Both our Development Team and Cloud Operations Team are currently investigating an incident where contacts are not being scored for POD 1 clients. At this time, we are not able to provide an ETA, but the next schedule update will be around 5.15 pm EDT (UTC-4).

 

====================================

**Update**

Sunday, July 27th, 5:08 pm EDT (UTC -4)

 

The Cloud Operations Team continue to the investigate the incident. Through their efforts, we have now confirmed this is a performance degradation incident as contacts are being scored. We are still unable to provide an ETA, but the next schedule update will be around 6:15 pm EDT (UTC-4).

 

====================================

**Update**

Sunday, July 27th, 6:22 pm EDT (UTC -4)

 

The Cloud Operations Team continues to the investigate the incident. We are still unable to provide an ETA, but the next schedule update will be around 7:15 pm EDT (UTC-4).

 

====================================

**Update**

Sunday, July 27th, 7:12 pm EDT (UTC -4)

 

Both our Development Team and Cloud Operations Team continues to the investigate the incident. We are still unable to provide an ETA, but the next schedule update will be around 8:15 pm EDT (UTC-4).

 

====================================

**Update**

Sunday, July 27th, 8:15 pm EDT (UTC -4)

 

Both our Development Team and Cloud Operations Team continues to the investigate the incident. We are still unable to provide an ETA, but the next schedule update will be around 9:15 pm EDT (UTC-4).

 

====================================

**Update**

Sunday, July 27th, 9:17 pm EDT (UTC -4)

 

Both our Development Team and Cloud Operations Team continues to the investigate the incident. We are still unable to provide an ETA, but the next schedule update will be on Monday, July 28th, 2014 around 10:00 am EDT (UTC-4).

 

====================================

**Update**

Monday, July 28th, 8:02 am EDT (UTC -4)

 

The incident was resolved today around 2:45 am EDT (UTC-4). After analysis by our support teams, it was determined that the incident resulted from a configuration issue.  The configuration issue has been resolved and production use of your Eloqua service has been restored.  Oracle is also reviewing the monitoring, alerting and standard operating procedures related to the incident.  After these reviews are completed, additional appropriate corrective actions identified during the reviews will be taken.