Skip navigation
1 2 3 4 Previous Next

Eloqua System Status

116 Posts authored by: Anirude-Oracle

Our Cloud Operations Team has identified between the hours of 11:00 am and 3:30 pm EDT (UTC-4) today, email sending was unavailable for our POD 3 clients and the incident has since been resolved. 

 

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 Cloud Operations Team has been investigating an incident where some clients were experiencing Email Deliverability Delays. There were additional configuration changes made to help resolve the incident. We are currently monitoring the situation and the next scheduled update will be around 11:30 am EDT (UTC-4).

 

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

**Update**

Friday, September 5th, 11:26 am EDT (UTC -4)

 

Our Cloud Operations Team continue to monitor the situation and the next scheduled update will be around 1:30 pm EDT (UTC-4).

 

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

**Update**

Friday, September 5th, 1:19 pm EDT (UTC -4)

 

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 Cloud Operations Team is currently investigating an incident where several services including Bulk API, Rest API, Data Import Export and Eloqua Insight are unresponsive. While we currently don't have an ETA, the next scheduled update will be around 11:30 am EDT (UTC-4).

 

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

**Update**

Thursday, September 4th, 11:26 am EDT (UTC -4)

 

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.

Between 12:55 am EDT and 1:30 am EDT (UTC-4) today, the Bulk API service was unresponsive. 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.

Our Cloud Operations Team is currently investigating an incident where the Bulk API service is unresponsive. While we currently don't have an ETA, the next scheduled update will be around 2:30 PM EDT (UTC -4)


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


****Update: August 28th 2014 2:30 PM EDT (UTC -4)****


All services are running normally, our NOC team is still investigating the cause. The Next update will be around 3:30 PM EDT (UTC -4)


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


****Update: August 28th 2014 2:49 PM EDT (UTC -4)****


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.

Continuing from the "GREEN / Bulk API, Rest API and Data Import Export Unresponsive / POD 1 and 2 / RESOLVED" advisory, our Cloud Operations Team have started work on restoring Eloqua Insight services for our POD 2 customers. We are unable to provide an ETA, but the next scheduled update will be around 10:00 am EDT (UTC-4).

 

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

**Update**

Thursday, August 28th, 9:33 am EDT (UTC -4)

 

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.

Our Cloud Operations Team is currently investigating an incident where the Bulk API service is unresponsive. While we currently don't have an ETA, the next scheduled update will be around 7:30 pm EDT (UTC-4).

 

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

**Update**

Wednesday, August 27th, 6:49 pm EDT (UTC -4)

 

Our Cloud Operations Team has identified a hardware failure and are working towards a resolution. Please note; RestAPI, Eloqua Insight and the Data Import/Export Services are also impacted. While we currently don't have an ETA, the next scheduled update will be around 7:30 pm EDT (UTC-4).

 

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

**Update**

Wednesday, August 27th, 7:14 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to work towards a resolution. They have been able to specifically restore functionality to the Bulk API services. The remaining services (RestAPI, Eloqua Insight and the Data Import/Export Services) are still impacted. Additionally - the scope of the incident has expanded to include our POD2 customers. While we currently don't have an ETA, the next scheduled update will be around 8:30 pm EDT (UTC-4).


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

**Update**

Wednesday, August 27th, 8:20 pm EDT (UTC -4)

 

Our Cloud Operations Team has made some progress with the incident. All services are restored for POD1 and they are currently working through the backlog of requests. POD2 has also been restored, but Eloqua Insight is experiencing performance degradation.  The next scheduled update will be around 9:00 pm EDT (UTC-4).

 

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

**Update**

Wednesday, August 27th, 9:11 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to work towards resolving the hardware failure. The next scheduled update will be around 10:00 pm EDT (UTC-4).

 

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

**Update**

Wednesday, August 27th, 10:15 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to work towards resolving the hardware failure. The next scheduled update will be around 11:00 pm EDT (UTC-4).

 

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

**Update**

Wednesday, August 27th, 10:22 pm EDT (UTC -4)

 

All the services have been fully restored to POD1. Eloqua Insight is final remaining service still impacted on POD2.  The next scheduled update will be around 11:00 pm EDT (UTC-4).

 

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

**Update**

Wednesday, August 27th, 11:10 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to investigate the Eloqua Insight incident on POD2.  The next scheduled update will be around 12:00 am EDT (UTC-4).

 

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

**Update**

Thursday, August 28th, 12:04 am EDT (UTC -4)

 

Our Cloud Operations Team continues to investigate the Eloqua Insight incident on POD2.  The next scheduled update will be around 1:00 am EDT (UTC-4).

 

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

**Update**

Thursday, August 28th, 12:53 am EDT (UTC -4)

 

Our Cloud Operations Team continues to investigate the Eloqua Insight incident on POD2.  The next scheduled update will be around 2:00 am EDT (UTC-4).

 

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

**Update**

Thursday, August 28th, 1:36 am EDT (UTC -4)

 

Will be resolving this incident as POD1 services were restored and we are opening a separate advisory for the ongoing Eloqua Insight Impacted on POD 2.

 

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

**Update**

Thursday, August 28th, 9:34 am EDT (UTC -4)

 

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.

Eloqua will be performing an emergency hot-fix this evening on Wednesday, August 27th, 2014 starting at 9:00 pm EDT (UTC-4)

 

The impact of the Eloqua Service will be moderate, the service that we need to redeploy is related to Data Imports. There will be an overall performance decrease using the Eloqua Application while we are deploying this hot-fix. Our System Status page on Topliners will be updated with our progress during the hot-fix.


We will be updating the advisory with the actual start time later today. The next scheduled update will be around 4:00pm EDT (UTC-4).


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

**Update**

Wednesday, August 27th, 10:42 am EDT (UTC -4)

 

Updated the advisory with our start time of 9:00 pm EDT (UTC-4).

 

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

**Update**

Wednesday, August 27th, 9:14 pm EDT (UTC -4)

 

Due to the ongoing incident on POD 1 and 2, we are delaying this emergency hot-fix. The next scheduled update will be around 10:30 pm EDT (UTC-4).

 

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

**Update**

Wednesday, August 27th, 10:24 pm EDT (UTC -4)

 

Due to the ongoing incident on POD 1 and 2, we are delaying this emergency hot-fix. The next scheduled update will be around 11:30 pm EDT (UTC-4).

 

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

**Update**

Wednesday, August 27th, 10:37 pm EDT (UTC -4)

 

Our Cloud Operations Team has started the hot-fix process. The next scheduled update will be around 11:30 pm EDT (UTC-4).

 

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

**Update**

Wednesday, August 27th, 11:24 pm EDT (UTC -4)

 

The hot-fix process is still in progress. The next scheduled update will be around 12:30 am EDT (UTC-4).

 

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

**Update**

Wednesday, August 28th, 12:24 am EDT (UTC -4)

 

The hot-fix process is still in progress. The next scheduled update will be around 1:30 am EDT (UTC-4).

 

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

**Update**

Wednesday, August 28th, 1:28 am EDT (UTC -4)

 

The hot-fix process is still in progress. The next scheduled update will be around 2:30 am EDT (UTC-4).

 

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

**Update**

Wednesday, August 28th, 1:49 am EDT (UTC -4)

 

The hot-fix process has completed successfully.

Our Development Team is currently investigating an incident impacting the compilation time of distribution lists, in the email batch send wizard area of Eloqua 9. We do not currently have an ETA for resolution. The next update is scheduled for 4:00 pm EDT (UTC -4).

 

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

****Update *****

Tuesday, August 26th 2014 3:55 PM EDT (UTC -4)

 

Our development team and NOC team continue to work together to investigate this incident. They have been able to rule out a few potential causes, but, as of yet they have been unable to uncover the root cause. The next update is scheduled for Wednesday August 27th 2014 at 10:00 AM EDT (UTC -4)

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

****Update *****

Wednesday, August 27th 2014 9:54 AM EDT (UTC -4)

Our Development and NOC Teams continue to work towards resolution, however at this time no ETA is available.  The next update is scheduled for Wednesday August 27th 2014 at 4:00 PM EDT (UTC -4)

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

****Update *****

Wednesday, August 27th 2014 11:15 AM EDT (UTC -4)

Our Development and NOC Teams have been able to resolve the incident and distribution list compilation is now behaving normally.

Our Development Team has been investigating an incident where clients are unable to add field merges to Engage Emails assets. They are currently working on a solution and at this time, we are unable to provide an ETA. Our next scheduled update will be Friday, August 22nd, 2014 around 11:00 am EDT.

 

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

**Update**

Friday, August 22nd, 12:05 pm EDT (UTC -4)

 

Our Development Team has identified a fix and we are currently targeting to hot-fix this incident on Sunday, August 24th, 2014. We will provide another update today around 5:00pm EDT.

 

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

**Update**

Friday, August 22nd, 3:38 pm EDT (UTC -4)

 

Our Cloud Operations Team has confirmed this hot-fix will be pushed to our production environments after our Eloqua Summer '14 Release - Service Pack 4 maintenance. Our next scheduled update will be Sunday, August 24th, 2014 around 5:00 pm EDT.

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

**Update**

Sunday, August 24th, 10:20 am EDT (UTC -4)

 

This hot-fix has been applied and this is now resolved.

Some clients are experiencing issues with hosted images being intermittently unavailable. Our cloud operations team is working toward a resolution, however at this time no ETA is available. The next update will be around 4 PM EDT (UTC-4).

 

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

**Update**

Thursday, August 14th, 12:40 pm EDT (UTC -4)


Our Cloud Operation Team working with our 3rd party vendor has identified the root case and corrective measure are being executed. As part of the restorative process, there is a possibility that some users might see a performance degradation for about 1 hour. While we are unable to provide an ETA, the next scheduled update will be around 4:00 pm EDT (UTC-4).

 

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

**Update**

Thursday, August 14th, 3:31 pm EDT (UTC -4)

 

This issue has been resolved as of 1:12 PM EDT.  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 Cloud Operations Team is currently investigating an incident where the Bulk API services for POD 1 and 2 clients are not working. At this time, we are unable to provide an ETA, but the next scheduled update will be around 6:00 pm EDT (UTC-4) today.


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

***Update: 5:59 PM EDT (UTC-4)***


This incident was resolved at 5:38 PM EDT (UTC-4). 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.


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

Eloqua Summer '14 Release - Service Pack 3



Service Pack 3 of the Summer '14 Release will roll out between 5AM, Sunday, August 10th, and 11 am, Sunday, August 10th, 2014 (all times EDT (UTC -4)).

 

 

Please review the supporting resources available in the Oracle Eloqua Release Center. This includes Release Notes for both Eloqua 9 Release Notes 2014 andEloqua 10 Release Notes 2014, with information on:


Release Overview

What's New in This Release

Known Issues

Fixed Issues

Technical Notes and Limitations

Supported Environments

Documentation

Troubleshooting and Technical Support

 

If you're not already an Eloqua Insiders, you'll need to request access to that group before you can access the Release Resource Center.

 

While the application may remain accessible during this time, some features such as file and image uploads, program builder and emails will be paused as they are upgraded. There will also be intermittent downtime during this window. You are advised to avoid using the application during this window.


******************************************************************************************************


****Update: 11:02 AM EDT (UTC-4)****

Maintenance is currently still underway on POD 1, the next update will be around 12:00 PM EDT (UTC-4). POD3 is operational.


*******************************************************************************************************

****Update: 11:58 AM EDT (UTC-4)****

POD 3 Rollout is complete. We are currently still in maintenance on POD1. The next update will be around 12:45 PM EDT (UTC-4).


*******************************************************************************************************

****Update: 12:45 PM EDT (UTC-4)****

POD 3 Rollout is complete. We are currently still in maintenance on POD1. The next update will be around 1:00 PM EDT (UTC-4).


*******************************************************************************************************

****Update: 1:02 PM EDT (UTC-4)****

Rollout of SP3 has been successfully concluded.


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.


*******************************************************************************************************

Our Cloud Operations Team is currently investigating an incident where External Calls are not processing. We are unable to provide an ETA, but next scheduled update will be around 7:00pm EDT.

 

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

**Update**

Thursday, August 7th, 5:25 pm EDT (UTC -4)

 

Our Cloud Operations Team has confirmed the External Calls are processing, but very slowly. They continue to investigate the incident. We are unable to provide an ETA, but next scheduled update will be around 7:00pm EDT.

 

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

**Update**

Thursday, August 7th, 6:15 pm EDT (UTC -4)

 

Our Cloud Operations Team has resolved the incident. 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 Cloud Operations Team identified and resolved an incident with our Bounceback Processing Services. Between July 15th, 2014 and July 31st, 2014, there was an intermittent incident where some contacts were being marked as hard bouncebacks when they should have been marked as a soft bounceback.

 

Since our Cloud Operations Team were able to scope the impact of this incident, they are executing corrective measures Tuesday, August 5th, 2014. They are, however, unable to correct Eloqua Insight metrics that may have been impacted.

 

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: