The Cloud Operations confirmed some clients on POD 3 are experiencing performance related incidents. The team has identified the root cause and currently working towards resolving the incident. As part of the resolution, some instances will see around 15 minutes of downtime with the following effects:

 

1. Outbound activities will be paused and resumed after downtime ends.

2. Forms will be captured

3. Other inbound activities (email responses, web tracking) will not be captured.

 

Given the urgency, our Support Team is equipped with the list of impacted of clients - please contact our Product Support Team to validate if you are affected. Cloud Operations is currently set to start the path to resolution at 9:00 pm EST (UTC-5). We will provide another update around 9:20 pm EST (UTC-5).

 

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

**Update**

Monday, February 3rd, 8:11 pm EST (UTC -5)

 

The Cloud Operations Team has further clarified this incident and we stand corrected. The Eloqua Application is not being impacted right now. The Cloud Operations team identified critical hardware errors which is leading them to perform corrective measures tonight. The Support Team is still equipped with the list of impacted of clients - please contact our Product Support Team to validate if you are affected. Cloud Operations is currently set to start the path to resolution at 9:00 pm EST (UTC-5). We will provide another update around 9:20 pm EST (UTC-5).

 

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

**Update**

Monday, February 3rd, 9:21 pm EST (UTC -5)

 

The Cloud Operations Team has completed their work and the Eloqua Services is being restored to those affected. We will provide another update around 9:40 pm EST (UTC-5).


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

**Update**

Monday, February 3rd, 9:32 pm EST (UTC -5)

 

The Cloud Operations Team confirms the maintenance work completed successfully.

 

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

**Update**

Monday, February 3rd, 9:46 pm EST (UTC -5)

 

After analysis by our support teams, it was determined that the incident resulted from a hardware issue. The hardware identified as faulty has been replaced and production use of your Eloqua service 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.