Skip navigation
1 2 3 Previous Next

Eloqua System Status

38 Posts authored by: Micheal Brown-Oracle

Our cloud operations team is investigating an incident that is causing configuration of Eloqua Cloud Applications to be unavailable. Existing cloud applications will continue to function as expected. We do not currently have an ETA for resolution, however, the next update will be at 5:30 am EDT (UTC -4).

 

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

**Update**

Thursday, July 31st 4:59 am EDT (UTC -4).

 

This incident has now been fully resolved.

Our development team is currently investigating an incident that is leading to intermittent performance impact in the integration area of the Eloqua application.  The next update will be at approximately 10:00 am Thursday, July 23rd (UTC -4)

 

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

**Update**

Thursday, July 23rd 10:31 am EDT (UTC -4).

 

Our development team is currently evaluating options to rectify this incident. No ETA is available, however the next update will be at approximately 4 pm EDT (UTC -4)

 

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

**Update**

Thursday, July 23rd 4:25 pm EDT (UTC -4).

 

Our development team has confirmed that this incident is now resolved.

Our development team is aggressively working to resolve a defect that is intermittently causing distribution list compilation to fail for E9 batch sends. While this incident is ongoing, use of program builder for sending is not impacted, and can be utilized as a workaround. We do not have an ETA for resolution, however daily updates will be provided via this thread. The next update will be Thursday, July 2nd at 10 am EDT (utc -4)

 

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

**Update**

Thursday, July 2nd 10:00 am EDT (UTC -4).

 

Our development team is currently still investigating this defect, no ETA is yet available. The next update will be at approximately 12:00 pm EDT (UTC -4) on Friday, July 3rd.

 

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

**Update**

Friday, July 3rd 11:57 am EDT (UTC -4).

 

Our development team is currently working to push through a fix for this incident. We do not currently have an ETA for the deployment of this fix, however we will provide an update on Monday, July 6th at 12:00 pm EDT (UTC -4)

 

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

**Update**

Monday, July 6th 12:10 pm EDT (UTC -4).

 

Our development team is currently evaluating timing for the deployment of the fix for this defect. We do not currently have an ETA, however the next update will be at approximately 12:00 pm (EDT UTC-4) on July 7th.

 

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

**Update**

Tuesday, July 7th 12:10 pm EDT (UTC -4).

 

We are currently still evaluating a timeline for the deployment of this fix. We do not currently have an ETA. The next update will be at approximately 12:00 pm EDT (UTC-4) on  July 8th.

 

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

**Update**

Wednesday, July 8th 12:35 pm EDT (UTC -4).

 

Our development team is still working out a timeline for the deployment of the fix for this defect. We do not currently have an ETA, however the next update will be at approximately 12:00 pm (EDT UTC-4) on July 9th.

 

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

**Update**

Thursday, July 9th 12:35 pm EDT (UTC -4).

Our development team is currently finalizing deployment plans for this fix. The next update will be at approximately 12:00 pm EDT (UTC-4) on July 13th.

 

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

**Update**

Monday, July 13th 12:07 pm EDT (UTC -4).

The fix for this defect is tentatively scheduled to be deployed Sunday July 19th. Any further updates or changes to this schedule will be provided via this thread, otherwise, the next update will be at approximately 12 PM EDT (UTC-4) on Sunday July 19th.

Our Cloud Operations and Development teams are currently investigating an incident that is causing slowness in processing of imports/exports as well as cloud applications. We do not currently have an ETA for resolution. the next update will be at approximately 11:30 am EDT (UTC -4).

 

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

**Update**

Tuesday, June 30th 11:15 am EDT (UTC -4).

 

Our Cloud Operations and Development teams have identified the root cause of this incident. Corrective actions have been taken, and the backlog created during this incident is being processed. The next update will be at approximately 2 PM EDT (UTC -4).

 

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

**Update**

Tuesday, June 30th 1:37 pm EDT (UTC -4).

 

The backlog continues to process at this time. We have put in place further changes to help speed the process, however no ETA is currently available. The next update will be at approximately 4 pm EDT (UTC -4).

 

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

**Update**

Tuesday, June 30th 4:15 pm EDT (UTC -4).

 

This incident has been resolved.

Our Cloud Operations Team is investigating an incident where Eloqua Insight is intermittently unavailable. No ETA is available, the next update will be at approximately 11 am EDT (UTC -4).

 

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

**Update: Wednesday, June 24th 9:50 am EDT (UTC -4)**

 

This incident has 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 is currently investigating an incident that is impacting the performance of the BULK API on PODs 1 and 2. We do not currently have an ETA for resolution. The next update will be at approximately 5:30 am EDT (UTC -4)

 

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

**Update: Wednesday, April 22nd 5:30 am EDT (UTC-4)**

 

Our Cloud Operations Team continues to work to resolve this incident, however at this time, no ETA for resolution is available. The next update will be at approximately 6:30 am EDT (UTC-4)

 

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

**Update: Wednesday, April 22nd 6:30 am EDT (UTC-4)**

 

Our Cloud Operations Team is continuing to work to resolve this incident. No ETA is currently available. The next update will be at approximately 7:30 am EDT (UTC-4)


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

**Update: Wednesday, April 22nd 6:45 am EDT (UTC-4)**

 

Our Cloud Operations Team has resolved this incident.

 

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 and Development Teams are currently investigating an incident impacting the performance of email bounceback processing queue for POD1 and POD 2 clients. We do not currently have an ETA for resolution, the next update is scheduled for 7:00 pm EDT (UTC -4)


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

**Update: Thursday, April 9th 7:05 pm EDT (UTC -4)**

 

Our Cloud Operations team has been able to resolve this issue for POD 1 clients, so this is now only affecting those on POD 2. The next update will be at approximately 10:00 am EDT (UTC -4) on Friday, April 10th.


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

**Update: Friday, April 10th 9:52 am EDT (UTC -4)**

 

Our Cloud Operations team is actively working with our Development teams to resolve this incident. The next update will be at approximately 12:00 pm EDT (UTC -4).

 

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

**Update: Friday, April 10th 10:00 am EDT (UTC -4)**

 

Our Cloud Operations and Development teams have resolved this incident.

 

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.

Our Cloud Operations Team is currently investigating an incident that is impacting the availability of BULK API Exports on POD1.  We do not currently have an ETA for resolution, however, the next update will be at approximately 6 PM EDT (UTC-4).

 

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

**Update**

Friday, April 3rd, 5:40 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 storage issue. The storage 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.

Emergency Hot Fix Advisory: Sunday, February 1st, 2015


Eloqua will be performing an emergency hot-fix on Sunday, February 1st, starting at 8 am EST. This will take approximately 3 hours.

 

All application processing will be suspended during this window and resumed after downtime ends.

 

Downtime effect as follows. During portions of this maintenance period, the following platform features will be unavailable:

 

  • Email Sending (all types)
  • Inbound/Outbound CRM Integrations
  • Bulk API
  • Lead Scoring
  • Data Import/Exports
  • Campaign Processing

 

We recommend that customers not attempt to use the application at this time as rolling outages are anticipated. Inbound web tracking and form data will be captured, however, agent use of the platform can potentially result in work being lost. Once the maintenance is complete, all processing will resume and any work items scheduled to execute during the maintenance window will begin processing.

 

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

Our Cloud Operations Team is currently investigating an incident that is impacting BULK API and Data Import/Export on POD 3.  We do not currently have an ETA for resolution, The next update will be at approximately 12:00 am EST (UTC -5)

 

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

**Update**

Wednesday, January 28th 12:00 am EST (UTC -5)

Our Cloud Operations Team is currently working to address this issue, however no ETA for full resolution is currently available. The next update will be at approximately 1:00 am EST (UTC -5)


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

**Update**

Wednesday, January 28th 12:17 am EST (UTC -5)

After analysis by our support teams, it was determined that the incident resulted from a storage issue. The storage 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 that is impacting the performance of BULK API on POD1.  We do not currently have an ETA for resolution. The next update will be at approximately 12 PM EST (UTC -5)


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

**Update**

Sunday, January 25th, 11:10 am EST (UTC -5)

Our Cloud Operations team has uncovered and resolved the root cause of this incident. Some delays can be expected while a small backlog that has formed is processed. The next update will be at approximately 2 pm EST (UTC -5)

 

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

**Update**

Sunday, January 25th, 1:20 pm EST (UTC -5)

After analysis by our support teams, it was determined that the incident was the result of a software bug of an Oracle Program. Information related to the incident has been passed on to our Product Engineering team. Once Product Engineering confirms they have a resolution to the issue, it will be deployed to the applicable Oracle Programs for your Eloqua service. No ETA for resolution is available at this time. 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, including deployment of the appropriate patch or release when available.


Our Cloud Operations team is currently investigating an incident that is impacting overall performance of the application for some POD1 clients. We do not currently have an ETA for resolution. The next update will be at approximately 3:00 pm EST (UTC-5)

 

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

**Update**

Wednesday, January 21st, 3:00 pm EST (UTC -5)

Our Cloud Operations Team continues to investigate this incident. The next update will be at approximately 4:00 pm EST (UTC-5)


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

**Update**

Wednesday, January 21st, 3:05 pm EST (UTC -5)


Our Cloud Operations Team has confirmed that this issue is now resolved.

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

Sunday, January 18th, 11:07 am EST (UTC -5).

 

Because of Application Unavailable / POD1 Clients, the Cloud Operations Team has delayed the Emergency Hot Fix for POD3 until further notice.

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

**Update**

Sunday, January 18th, 1:00 pm EST (UTC-5).

 

Our Cloud Operations Team are currently rolling out the hotfixes for POD3. We can confirm that your Eloqua Services will not be suspended and will update this post upon completion.

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

**Update**

Sunday, January 18th, 1:30 pm EST (UTC-5).

 

Our Cloud Operations Team have completed the hot-fixes.

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

Emergency Hot Fix Advisory: Sunday, January 18th, 2015


Eloqua will be performing an emergency hot-fix on Sunday, January 18th, between 5 and 11 am EST (UTC -5).

 

All application processing will be suspended during this window and resumed after downtime ends.

 

Downtime effect as follows. During portions of this maintenance period, the following platform features will be unavailable:

 

  • Email Sending (all types)
  • Inbound/Outbound CRM Integrations
  • Bulk API
  • Lead Scoring
  • Data Import/Exports
  • Campaign Processing

 

We recommend that customers not attempt to use the application at this time as rolling outages are anticipated. Inbound web tracking and form data will be captured, however, agent use of the platform can potentially result in work being lost. Once the maintenance is complete, all processing will resume and any work items scheduled to execute during the maintenance window will begin processing.

 

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

Our development team is currently investigating an incident that is impacting the ability for some users to access Prospect Profiler. We do not currently have an ETA for resolution, however the next update will be January 16 at approximately 10:00 AM EST (UTC -5)

 

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

**Update**

Friday, January 16th, 10:00 AM EST (UTC -5)

 

Our development team is still currently investigating the incident and still working towards a resolution. The next update will be at approximately 4:00 pm EST (UTC-5)

 

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

**Update**

Friday, January 16th, 4:00 PM EST (UTC -5)

 

Our Development team is working to fully test a fix for this incident. We cannot at this time provide an ETA. The next update will be on Monday Jan 19th, 2015 at approximately 10:00 am EST (UTC -5)

 

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

**Update**

Friday, January 16th, 6:05 PM EST (UTC -5)

 

Our Cloud Operations Team will be pushing a hot-fix for customers on POD 1 and 3 for this incident on Sunday, January 18th, 2015. While we continue to plan for POD 2, the next scheduled update will be on Monday, January 19th, 2015 around 10:00 am EST (UTC-5).

 

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

**Update**

Monday, January 26th, 10:05 AM EST (UTC -5)

This issue is now fully resolved, the hotfix was pushed on January 18th.

Our Cloud Operations Team is currently investigating an incident impacting the availability of the Eloqua Application for some POD1 clients. The next update will be at approximately 8:15 pm EST (UTC-5)


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

**Update**

Monday, January 5th, 8:20 pm EST (UTC-5)

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