Our Cloud Operations Team has been aggressively troubleshooting an incident where some clients are receiving a "Secure Connection Failed" error. As of 2:50pm EDT (UTC-4), a configuration change was made and they are monitoring the situation. We currently do not have an ETA for resolution, however, the next scheduled update will be around 3:30pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 3:30 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 4:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 4:00 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 5:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 5:00 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 6:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 5:50 pm EDT (UTC -4)

 

Cloud Operations will be performing additional configurations changes at 9:00pm EDT (UTC-4) and will be monitoring the incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 10:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 10:02 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 11:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 10:42 pm EDT (UTC -4)

 

As the Cloud Operations Team troubleshoot this incident, we are still unable to provide anything tangible at this time. While we are still unable to provide an ETA, we will provide another update on Wednesday, August 12th at approximately 10:00 am EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 10:00 am EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 11:00 am EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 11:09 am EDT (UTC -4)

 

Our Cloud Operations has reverted the configurations changes that did not have any affect. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 12:00 pm EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 12:25 pm EDT (UTC -4)

 

Our Cloud Operations Team has confirmed that this issue is now resolved.

 

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

**Update** Thursday, August 13th, 1:11 pm EDT (UTC -4)

 

After analysis by our support teams, the root cause of the incident was not determined.  At this time, production use of your Eloqua service has been restored.  Oracle is 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.