Skip navigation

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

**Update**

Wednesday, October 1st, 11:53 pm EDT (UTC -4)

 

Our Cloud Operations Team has completed their work on POD1 and POD2.

 

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.


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

**Update**

Wednesday, October 1st, 11:28 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to work aggressively to complete this. They have completed work on POD3 and services have been restored while POD1 and POD2 continue to be worked on. We are now targeting 12:15am EDT (UTC-4) and will provide another update around 12:00 am EDT (UTC-4).


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

**Update**

Wednesday, October 1st, 10:50 pm EDT (UTC -4)

 

Our Cloud Operations Team has identified the maintenance will need additional time. The teams are working aggressively to complete this and are currently targeting 11:45 pm EDT (UTC-4). We will provide another update around 11:30 pm EDT on their efforts.


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

**Update**

Wednesday, October 1st, 2:45 pm EDT (UTC -4)

 

This preventative maintenance has been confirmed for tonight, Wednesday, October 1st, between 9 and 11 pm EDT (UTC -4).


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

**Update**

Tuesday, September 30th, 6:35 pm EDT (UTC -4)

 

This preventative maintenance has been postponed. We are looking to schedule for the same time tomorrow (Wednesday, October 1st). This Post will be updated with the final timing once it has been confirmed.

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

 

Emergency Preventative Maintenance Advisory for Wednesday, October 1st, 2014

 

 

Eloqua will be performing emergency preventative maintenance on Tuesday, September 30th, 2014, between 9 and 11 pm EDT (UTC -4).

 

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 affecting the load time of cloud components on Eloqua landing pages. We will provide daily updates throughout this investigation.

 

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

**Update**

Wednesday, October 1st, 9:47 AM EDT (UTC-4)

 

Our development team is still currently investigating the incident. The next update is scheduled for Thursday, October 2nd.

 

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

**Update**

Thursday, October 2nd, 4:03 PM EDT (UTC-4)

 

Our development team has narrowed down the cause and is currently working towards a resolution. The next update is scheduled for Friday, October 3rd.

 

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

**Update**

Friday, October 3rd, 1:17 PM EDT (UTC-4)

 

Our development team is currently investigating the cause and still working towards a resolution. The next update is scheduled for Monday, October 6th.

 

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

**Update**

Monday, October 6th, 2:54 PM EDT (UTC-4)

 

Our development team is currently investigating the cause and still working towards a resolution. The next update is scheduled for Tuesday, October 7th.

 

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

**Update**

Tuesday, October 7th, 2:54 PM EDT (UTC-4)

 

Our development team is still investigating the cause and currently working towards a resolution. The next update is scheduled for Wednesday, October 8th.

 

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

**Update**

Wednesday, October 8th, 1:10 PM EDT (UTC-4)

 

Our development team continues to investigate the root cause for this incident. As of this time, we have no ETA for resolution. The next update is scheduled for Thursday, October 9th.

 

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

**Update**

Thursday, October 9th, 1:58 PM EDT (UTC-4)

 

Our development team continues to investigate the root cause for this incident. As of this time, we have no ETA for resolution. The next update is scheduled for Friday, October 10th.

 

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

**Update**

Friday, October 10th, 2:38 PM EDT (UTC-4)

 

Our development team continues to investigate the root cause for this incident. We currently have no ETA for resolution. The next update is scheduled for Tuesday, October 14th.

 

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

**Update**

Tuesday, October 14th, 1:43 PM EDT (UTC-4)

 

Our development team is still investigating the cause and currently working towards a resolution. The next update is scheduled for Wednesday, October 15th.

 

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

**Update**

Wednesday, October 15th, 4:14 PM EDT (UTC-4)

 

Our development team continues to investigate the incident. We currently have no ETA for resolution. The next update is scheduled for Thursday, October 16th.

 

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

**Update**

Thursday, October 16th, 2:15 PM EDT (UTC-4)

 

Our development team continues to investigate the incident. While we do not currently have an ETA, the next update is scheduled for Friday, October 17th.

 

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

**Update**

Friday, October 17th, 4:28 PM EDT (UTC-4)

 

Our development team continues to investigate the incident. While we do not currently have an ETA, the next update is scheduled for Monday, October 20th.

 

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

**Update**

Monday, October 20th, 4:10 PM EDT (UTC-4)

 

Our development team is continuing to investigate the incident and work towards a resolution. While we do not currently have an ETA, the next update is scheduled for Tuesday, October 21st.

 

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

**Update**

Tuesday, October 21st, 3:53 PM EDT (UTC-4)

 

Our development team is continuing to investigate the incident and work towards a resolution. While we do not currently have an ETA, the next update is scheduled for Wednesday, October 22nd.

 

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

**Update**

Wednesday, October 22nd, 4:22 PM EDT (UTC-4)

 

Our development team continues to investigate the incident and work towards a resolution. While we do not currently have an ETA, the next update is scheduled for Thursday, October 23rd.

 

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

**Update**

Thursday, October 23rd, 10:18 AM EDT (UTC-4)

 

Our development team has confirmed that the incident affecting the load time of cloud components is no longer reproducible.

Our Cloud Operations Team is currently investigating an incident that is impacting the availability of Eloqua Insight for some POD1 clients. We do not currently have an ETA for resolution. The next update will be around 8:00 am EDT (UTC -4).


This incident was fully resolved and insight made available as of 7:35 AM EDT.

 

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

**Update**

Friday, September 26th, 7:35 am EDT (UTC -4)

 

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 the responsiveness of BULK API and Data import on PODs 1 and 2. We currently do not have an ETA for resolution, the next update will be around 12:00 AM EDT (UTC -4) Sept 25 2014.

 

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

**Update**

Thursday, September 25th,  12:04 am EDT (UTC -4)

 

Our cloud operations team was able to resolve this issue as of 11:45 PM EDT (UTC -4) September 24th 2014.

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 identified at 4:00 AM EDT today (UTC -4), insight is unavailable for our POD 1 clients. We do not currently have an ETA for resolution, the next update is scheduled for 6:00 AM EDT (UTC -4).


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

**Update**

Monday, September 22nd 5:59 AM EDT (UTC-4)

 

Our cloud operations team is still currently investigating the incident. The next update will be around 7:00 AM EDT (UTC -4)

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

**Update**

Monday, September 22nd 6:57 AM EDT (UTC-4)


Our cloud operations team has restored the availability of insight on POD 1, and are working to determine the root cause of the incident. The next update will be around 9:00 AM EDT (UTC-4)

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

**Update**

Monday, September 22nd 9:04 AM EDT (UTC-4)


Insight is now fully available, we are awaiting for the root cause analysis to be completed, we will provide the root cause as soon as it becomes available. The next update will be around 11 AM EDT (UTC -4)


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

**Update**

Monday, September 22nd 10:22 AM EDT (UTC-4)


This issue was fully resolved as of 6:08 AM EDT ( UTC -4)

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

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

**Update**

Sunday, September 21st.

 

The maintenance concluded on schedule and without incident.

 

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

Scheduled Maintenance Advisory for Sunday, September 21st, 2014

 

 

Eloqua will be performing scheduled maintenance on Sunday, September 21st, 2014, between 5 and 11am EDT (UTC -4).

 

Downtime effect as follows. During portions of this maintenance period:

 

  • Client installs may be inaccessible
  • Application processing will be paused and resumed after downtime ends.

 

You are advised not to use the application during this period to avoid loss of work.

 

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

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

**Update**

Sunday, September 14th, 10 am EDT (UTC -4)

 

The maintenance concluded on schedule and without incident.

 

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

Scheduled Maintenance Advisory for Sunday, September 14th, 2014

 

 

Eloqua will be performing scheduled maintenance on Sunday, September 14th, 2014, between 5 and 11am EDT (UTC -4).

 

Downtime effect as follows. During portions of this maintenance period:

 

  • Client installs may be inaccessible
  • Some outbound activity will be unavailable (Bulk API, Lead Scoring)
  • Application processing will be paused and resumed after downtime ends.

 

You are advised not to use the application during this period to avoid loss of work.

 

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

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.

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

**Update**

Wednesday, September 10th, 04:10 am EDT (UTC -4)

 

The maintenance concluded on schedule and without incident.

 

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

Eloqua Summer '14 Release - Service Pack 5


Service Pack 5 of the Summer '14 Release will roll out between 11 pm, Tuesday, September 9th, and 5 am, Wednesday, September 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 and Eloqua 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.

 

 

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

Sunday, September 7th, 11:00 am EDT (UTC -4)

 

The maintenance concluded on schedule and without incident.

 

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

 

Eloqua Summer '14 Release - Service Pack 5


Service Pack 5 of the Summer '14 Release will roll out between 5 and 11 am EDT (UTC -4), on Sunday, September 7th, 2014.


 

 

Please review the supporting resources available in the Oracle Eloqua Release Center. This includes Release Notes for both Eloqua 9 Release Notes 2014 and Eloqua 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.

 

 

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

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 that is impacting the availability of Eloqua hosted images. We do not currently have an ETA for resolution. The next update will be around 11:00 AM EDT (UTC -4).

 

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


****Update: September 3rd 2014 10:18 AM EDT (UTC -4)****

Our Cloud Operations is working with a vendor to resolve this incident. We currently estimate that this should be resolved in one hour. The next update will be around 11:30 AM EDT (UTC -4)

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


****Update: September 3rd 2014 11:30 AM EDT (UTC -4)****

Our Cloud Operations is currently still working alongside a vendor to resolve this incident. The Next Update will be around 1:30 PM EDT (UTC -4).

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


****Update: September 3rd 2014 1:30 PM EDT (UTC -4)****

Our Cloud Operations is currently still working alongside a vendor to resolve this incident. The Next Update will be around 2:30 PM EDT (UTC -4).

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


****Update: September 3rd 2014 2:13 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.





Filter Blog

By date: By tag: