Skip navigation

Eloqua System Status

13 Posts authored by: Jeff Butwell

We have received reports that Insight on POD 3 is currently unavailable. We have also been informed that there may be performance issues when accessing the Eloqua application. We are investigating this issue and will provide an update at 5:30pm EDT (UTC -4) or as soon as we have any additional information.

 

To determine if you are on Pod3:

Log into Eloqua as you normally would.

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**

Wednesday, March 19th, 5:24 pm EDT (UTC -4)

 

This issue was resolved at 5:00 pm EDT

 

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.

 

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

We have received reports that Insight on POD 3 is currently unavailable. We are investigating this issue and will provide an update at 2:30pm EDT (UTC -4)

 

To determine if you are on Pod3:

Log into Eloqua as you normally would.

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**

Wednesday, March 19th, 2:40 pm EDT (UTC -4)

 

This issue was resolved at 2:09pm EDT

 

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.

 

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

We have received reports that some customers are experiencing slow loading of the application on POD 3. We are currently investigating this issue and will provide an update once we have more information.

 

To determine if you are on POD 3:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

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

 

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

 

**Update**

Tuesday, February 25th, 1:00 pm EST (UTC -5)

 

This issue has now been resolved.

 

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

We have received reports that clients on POD 3 may not be able to access the Bulk API at this time. We are currently investigating the cause of this issue and will update this post as soon as we have any further information.

 

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

**Update**

Monday,  February 17th, 8:59pm EST (UTC -5)

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

 

This issue has now been resolved. Bulk API service was restored at approximately 8:30pm EST (UTC -5).

**Update**

Sunday, January 26, 2:30 pm EST (UTC -5)

 

Maintenance concluded successfully and on time. No issues have been identified.


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


Eloqua will be performing maintenance and hardware upgrades on Sunday, January 26th, between 5:00 am and 11:00 am EST (UTC -5).

 

During this maintenance period:

 

• Insight reporting will be unavailable for periods of the maintenance

• Forms and email responses will be lost during hardware reboots (5-10 minutes)

• Application processing will be paused, and resumed after maintenance completes

 

You are advised to avoid using the application or scheduling email batches during this window.

 

Should you require more information or have any questions, please feel free to contact our support specialists.

We are currently experiencing an issue with Email Sends. When attempting to send an email, you may receive the following error:

 

Error occurred while trying to connect to the smtp server. Please contact the technical support team.

 

We are currently working on a resolution to this issue. A further update will be provided at 1:30 pm EST (UTC -5) or as soon as we have any additional information.

 

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

**Update**

Wednesday, January 22, 1:21 pm EST (UTC -5)

 

We have now identified that this issue is not only affecting Test Sending. We are no longer actively seeing the error, but are continuing to investigate the cause. The next update will be at 2:00 pm EST (UTC -5) or as soon as we have any further information.

 

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

**Update**

Wednesday, January 22, 2:00 pm EST (UTC -5)

 

We are still currently investigating the cause of this issue. We have not seen a new occurrence of this error since approximately 1:20 pm EST (UTC -5). The next update will be at 3:00 pm EST (UTC -5) or as soon as we have any further information.

 

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

**Update**

Wednesday, January 22, 2:18 pm EST (UTC -5)

 

After analysis by our support teams, it was determined that the incident resulted from a configuration issue. The configuration 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 are currently experiencing network issues which are affecting the availability of the Eloqua Application for POD 1 and 2 clients. We are currently working to resolve this issue and will provide an update at 2:30 PM EST (UTC -5), or as soon as we have any additional information.

 

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

**Update**

Tuesday, January 14th, 2:30 pm EST (UTC -5)

 

We are still investigating the cause of this issue.

 

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

**Update**

Tuesday, January 14th, 3:00 pm EST (UTC -5)

 

We are still investigating the cause of this issue.

 

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

**Update**

Tuesday, January 14th, 3:30 pm EST (UTC -5)

 

We are still investigating the cause of this issue.

 

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

**Update**

Tuesday, January 14th, 4:00 pm EST (UTC -5)

 

We are still investigating the cause of this issue. The next update will be at approximately 4:30 pm EST (UTC -5) or as soon as we have any additional information.

 

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

**Update**

Tuesday, January 14th, 4:30 pm EST (UTC -5)

 

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.

 

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

**Update**

Tuesday, January 14th, 5:30 pm EST (UTC -5)

 

We are still experiencing intermittent network connectivity issues. We continue to work on resolving this issue, and will provide an update as soon as we have any additional information.

 

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

**Update**

Tuesday, January 14th, 6:15 pm EST (UTC -5)

 

We continue to investigate the cause of this issue, and will regularly update this post.


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

**Update**

Tuesday, January 14th, 7:10 pm EST (UTC -5)

 

Our Production Team continues to investigate this incident. At this time, we cannot offer an ETA, but the next scheduled update will be around 8:15 pm EST (UTC -5) or as soon as we have any additional information available.


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

**Update**

Tuesday, January 14th, 8:10 pm EST (UTC -5)

 

Our Production Team continues to investigate this incident as restoring the Eloqua Service is our top priority. At this time, we cannot offer an ETA, but the next scheduled update will be around 9:15 pm EST (UTC -5) or as soon as we have any additional information available.


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

**Update**

Tuesday, January 14th, 9:40 pm EST (UTC -5)

 

Our Production Team continues to investigate this incident. At this time we cannot offer an ETA. The next scheduled update will be at approximately 11:00 pm EST (UTC -5) or as soon as we have any additional information available.


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

**Update**

Tuesday, January 14th, 11:30 pm EST (UTC -5)

 

The issue was resolved as of 10:38 pm EST. After analysis by our support teams, it was determined that the incident resulted from a configuration issue. The configuration 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.

On November 4th, between 12:33 PM EST and 1:16 PM EST, you may have experienced performance issues with Eloqua Insight.

 

After analysis by our support teams, it was determined that the incident resulted from an operating system issue. The operating system 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 are currently experiencing a delay with Test Sending emails. There may be a delay of approximately 15 minutes before emails which have been Test Sent are received. We are expecting this issue to be resolved at approximately 4:00 pm EDT (UTC -4). We will provide another update at that time.

 

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

**Update**

Thursday, October 24st, 2:44 pm EDT (UTC -4)

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

 

This issue has now been resolved. Test sends should now deploy without delay.

Currently, our login page at http://login.eloqua.com is unavailable. We are working to correct this issue and will provide more updates as they are available.


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

**Update**

Thursday, September 30th, 4:29 pm EDT (UTC -4)


The login page is now available. We are currently investigating to determine the cause and will provide an update when more details are available.


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

**Update**

Thursday, September 30th, 4:44 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.

 

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

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: