Skip navigation

Our Production Team has identified the BULK API service is unavailable for POD 1 and 2 clients. We currently investigating this incident and don't have an ETA. We will provide another update around 12:15 pm EST (UTC-5).

 

To determine if you are on Pod1:

Log into Eloqua as you normally would.

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 would.

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

Thursday, December 19th, 12:27 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.

**UPDATE**

Thursday, December 19th, 9:40 pm EST (UTC -5)

 

Maintenance concluded within the scheduled timeframe and without issues.


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



Insight Maintenance Advisory for Thursday, December 19th, 2013

 

 

Eloqua will be performing Insight maintenance on Thursday, December 19th, between 9 and 9:30 PM EST (UTC -5).

 

During this maintenance period:

 

  • Non-Insight functionality will not be impacted
  • Insight will be intermittently unavailable during the maintenance window
  • Please avoid using Insight during the maintenance window to avoid losing work

 

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

 

 

To determine if you are on Pod 2:

 

Log into Eloqua as you normally would.

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).

Our Production Team is currently investigating performance issues with Eloqua Insight. The next scheduled update will be around 10:00 am EST (UTC -5).


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

**Update**

Friday, December 13th, 10:00 am EST (UTC -5)

 

We are still investigating this issue. Unfortunately we are still unable to provide an estimated resolution at this time. The next scheduled update will be around 11:00 am EST (UTC -5) or as soon as we have any additional information available.

 

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

**Update**

Friday, December 13th, 11:00 am EST (UTC -5)

 

We are still investigating this issue. Unfortunately we are still unable to provide an estimated resolution at this time. The next scheduled update will be around 1:00 pm EST (UTC -5) or as soon as we have any additional information available.

 

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

**Update**

Friday, December 13th, 1:00 pm EST (UTC -5)

 

We are still investigating this issue. Unfortunately we are still unable to provide an estimated resolution at this time. The next scheduled update will be around 3:00 pm EST (UTC -5) or as soon as we have any additional information available.

 

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

**Update**

Friday, December 13th, 1:20 pm EST (UTC -5)

 

Our production team believes they have identified the issue. The resolution will involve approximately 30 minutes of downtime for Insight on POD1. This downtime will only affect Insight, all other functionality of the Eloqua application will be unaffected. We are beginning the maintenance period now and will post an update as soon as the service has been restored.

 

To determine if your install is on POD1, when logged into the Eloqua application, the URL is:

 

https://secure.eloqua.com

 

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

**Update**

Friday, December 13th, 1:55 pm EST (UTC -5)

 

Our production team believes this issue has now been resolved. Insight is now available for all POD1 customers. We will provide an update with an analysis of the issue once we have completed our investigation.

 

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

**Update**

Friday, December 13th, 2:05 pm EST (UTC -5)

 

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

Between 9:50 am and 10:16 am EST (UTC-5), some clients' SSL Hypersites were unavailable. 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.

Our Development Team identified an intermittent issue where some email batches were not completing. It is recommended to review your batches to ensure proper deployment of campaigns. Navigation steps and tips can be found at Email Batch Troubleshooting.


Please contact our Support Team for additional viability into this incident. We currently don’t have an ETA to share, but our next schedule update on this incident will be Tuesday, December 10th around 2:00 pm EST (UTC -5).


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

**Update**

Tuesday, December 10th, 10:08 am EST (UTC -5)


The Development Team is working through a code fix for this incident. We are targeting to have this completed by Friday, December 13th. Our next schedule update on this incident will be Monday, December 16th around 2:00 pm EST (UTC -5).


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

**Update**

Monday, December 16th, 9:30 am EST (UTC -5)


The Development Team has completed their code fix for this incident. We are targeting to hot-fix this on Tuesday, December 17th. Our next schedule update on this incident will be Wednesday, December 18th around 11:00 am EST (UTC -5).


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

**Update**

Monday, December 18th, 10:58 am EST (UTC -5)

 

During the hot-fix process, our Development Team uncovered an area of the code that is at risk as a result of our current solution. They will require some more time to properly fix it before we can fully resolve this incident. We are now targeting to hot-fix this on January 3rd, 2014. Our next scheduled update on this incident will be Monday, January 6th, 2014 around 11:00 am EST (UTC -5).

 

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

**Update**

Monday, January 6th, 10:16 am EST (UTC -5)


The Development Team has completed their hot-fix for this incident and consider this resolved. Our team will continue to monitor this service.

Some clients are experiencing delays in email deployment. Our Production team is currently investigating the issue. At this time we are unable to provide an ETA, but the next scheduled update is at 9:30 am EST (UTC-5)

 

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

**Update**

Monday, December 2nd, 9:36 am EST (UTC -5)


The Eloqua Services has been restored as of 9:19 am 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.

Filter Blog

By date: By tag: