Skip navigation

Our Bulk API Service was temporarily unavailable between 16:32 EDT (GMT -4) and 17:09 EDT. This issue has now been resolved.

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

**Update**

Thursday, August 22nd, 3:16 am EDT (UTC -4)

 

Our Cloud Operations Team had identified the BULK API Services had additional downtime which was resolved at 2:45 am EDT (GMT -4) today. 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.

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

**Update**

Thursday, August 22nd, 3:24 am EDT (UTC -4)

 

This issue affected users on Pod1 and Pod2.

 

To determine if you are on Pod1:

Log into Eloqua as you normally do

Look at the browser URL once you are logged in

Pod1 URL has the following format - www.secure.eloqua.com/...  (note:  no number included in URL)

 

To determine if you are on Pod2:

Log into Eloqua as you normally do

Look at the browser URL once you are logged in

Pod2 URL has the following format - www02.secure.eloqua.com/... (note:  02 included in URL)

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

There is an issue accessing the application. Oracle|Eloqua is investigating and we will provide another update around 5:00 pm EDT (UTC -4).


This issue affects users on Pod1 and Pod2.

 

To determine if you are on Pod1:

Log into Eloqua as you normally do

Look at the browser URL once you are logged in

Pod1 URL has the following format - www.secure.eloqua.com/...  (note:  no number included in URL)

 

To determine if you are on Pod2:

Log into Eloqua as you normally do

Look at the browser URL once you are logged in

Pod2 URL has the following format - www02.secure.eloqua.com/... (note:  02 included in URL)

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

**Update**

Friday, August 16th, 4:36 pm EDT (UTC -4)

 

We have also identified users on Pod3 were also impacted.


To determine if you are on Pod3:

Log into Eloqua as you normally do

Look at the browser URL once you are logged in

Pod3 URL has the following format - secure.p03.eloqua.com...... (note:  03 included in URL)

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

**Update**

Friday, August 16th, 4:37 pm EDT (UTC -4)

 

The application should now be accessible. We are continuing to investigate the root cause of this issue and will provide an update once we have more information.

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

**Update**

Friday, August 16th, 5:50 pm EDT (UTC -4)

 

This issue has now been fully resolved. Our production team is still reviewing the root cause. We will provide an update with more information about the root cause by Monday, August 19th, 1:00 pm EDT (UTC -4).

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

**Update**

Saturday, August 17th, 4:50 pm EDT (UTC -4)

 

After analysis by our support teams, it was determined that the incident resulted from a network issue. The network 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.

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


We have received reports of some customers not receiving Email Sends or Email Notifications deployed through the Eloqua application. We are currently investigating to determine the possible cause. We will provide a further update once we have any additional information, or by 2 p.m. EDT at the latest.

 

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

**Update**

Tuesday, August 13th, 1:46 p.m. EDT (UTC -4)

 

This issue has now been resolved.

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

Filter Blog

By date: By tag: