The Cloud Operations Team requires additional time for our POD1 468 Release, as such the application remains unavailable. They estimate an additional hour is required and we will provide another scheduled update at approximately 11:45 am EST (UTC-5) today.

 

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

**Update**

Sunday, January 18th, 11:45 am EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. They have had to revise their earlier estimation and we are unable to provide an ETA at the moment. The next scheduled update will be at approximately 12:30 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 12:27 pm EST (UTC-5).

 

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 1:00 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 1:00 pm EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 1:30 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 1:27 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 1:57 pm EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 2:30 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 2:25 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 2:56 pm EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 3:30 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 3:27 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 3:56 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 4:28 pm EST (UTC-5).

 

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

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

**Update**

Sunday, January 18th, 4:40 pm EST (UTC-5).

 

The application is now accessible.

The unplanned outage was a result of planned maintenance requiring additional time beyond the initially anticipated duration. The maintenance has been completed and your Eloqua service is available. Oracle is reviewing the events and issues that caused this extended maintenance. After these reviews are completed, additional appropriate corrective actions identified during the reviews will be taken.