Discussions

GREEN / Login Impacted / Some POD 1 Clients / RESOLVED

Jonathan.Turiano-Oracle
edited Oct 30, 2014 5:06PM in Eloqua System Status

Our Cloud Operations team is currently investigating an incident where clients are receiving an error message when logging into the Eloqua Application on POD1. We do not currently have an ETA for resolution. The next update will be at approximately 6:30 am EDT (UTC -4)

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

**Update**

Thursday, October 30th, 6:30 am EDT (UTC -4)


Our Cloud Operations Team continues to investigate this incident. The next update will be around 7:30 am EDT (UTC-4)


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

**Update**

Thursday, October 30th, 7:30 am EDT (UTC -4)


Upon further investigation, only some clients on POD 1 are impacted. Our Cloud Operations Team continues to investigate this incident. The next update will be around 8:30 am EDT (UTC-4)


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

**Update**

Thursday, October 30th, 8:23 am EDT (UTC -4)


Our Cloud Operations Team continues to aggressively troubleshoot this incident. The next scheduled update will be around 9:30 am EDT (UTC-4)


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

**Update**

Thursday, October 30th, 9:23 am EDT (UTC -4)


Our Cloud Operations Team continues to troubleshoot this incident. The next scheduled update will be around 10:30 am EDT (UTC-4)


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

**Update**

Thursday, October 30th, 10:13 am EDT (UTC -4)


Our Cloud Operations Team continues to troubleshoot this incident. The next scheduled update will be around 11:30 am EDT (UTC-4)


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

**Update**

Thursday, October 30th, 11:20 am EDT (UTC -4)


Upon further investigation, it has been confirmed that the incident still exists. Our Cloud Operations Team continues to troubleshoot this incident. The next scheduled update will be around 12:30 pm EDT (UTC-4)


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

**Update**

Thursday, October 30th, 12:28 pm EDT (UTC -4)


Our Cloud Operations Team have identified the incident and working towards a resolution. The next scheduled update will be around 1:30 pm EDT (UTC-4)


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

**Update**

Thursday, October 30th, 1:25 pm EDT (UTC -4)


Our Cloud Operations Team have identified the incident and still working towards a resolution. The next scheduled update will be around 2:30 pm EDT (UTC-4)


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

**Update**

Thursday, October 30th, 2:25 pm EDT (UTC -4)


Our Cloud Operations and Development Team are currently investigating the incident and still working towards a resolution. The next scheduled update will be around 3:30 pm EDT (UTC-4)


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

**Update**

Thursday, October 30th, 3:30 pm EDT (UTC -4)


Our Cloud Operations and Development Team are currently investigating the incident and still working towards a resolution. The next scheduled update will be around 5:30 pm EDT (UTC-4)


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

**Update**

Thursday, October 30th, 5:00 pm EDT (UTC -4)


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

Upon further investigation, the root cause of the incident was found to be the result of an event within the Customer's control authority. We recommend that the Customer work with Oracle Support to remediate the situation and put a long term corrective action in place.

Post edited by Unknown User on
Tagged: