Skip navigation
1 2 3 Previous Next

Eloqua System Status

116 Posts authored by: Anirude-Oracle

Our Cloud Operations Team is currently woking on a incident where net new domain registrations are not working within the Eloqua platform. Domains registered through Eloqua that are coming up for renewal are also impacted. The teams are working through to get this resolved, and while we don't have an ETA, our next update will be Sunday, September 20th around 11:00 am EDT (UTC-4).

 

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

**Update: Sunday, September 20th 8:22 am EDT (UTC-4)**

 

The Cloud Operations Team were able to resolve the immediate incident. Customers are now able to register new domains within the Eloqua platform. We will continue to monitor the situation and provide another update on Monday, September 21st around 12:00 pm EDT (UTC-4).

 

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

**Update: Monday, September 21st 11:07 am EDT (UTC-4)**

 

After analysis by our support teams, it was determined that the incident resulted from a standard operating procedure error. The production use of your Eloqua service has been restored. The related standard operating procedure has been reviewed for improvement and for additional safeguards to avoid this issue in the future. Oracle is also reviewing the monitoring and alerting 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 for Sunday, September 20th, 2015



Eloqua is targeting to perform an emergency hot-fix between Sunday, September 20th at 5:00 am to Sunday, September 20th at 11:00 am EDT (UTC-4).

 

We anticipate the impact of the Eloqua Service will be moderate and the service that we need to redeploy is related to Eloqua Apps. We estimate the hot-fix will take around 2 hours to complete, however, our System Status page on Topliners will be updated with our progress during the hot-fix.

 

During portions of this maintenance period, customers may experience a temporary performance degradation.

 

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

 

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

**Update: Sunday, September 20th 8:02 am EDT (UTC-4)**

 

The hot-fix was successfully completed at 5:50 am EDT (UTC-4).

Our Cloud Operations Team has been aggressively troubleshooting an incident where some clients are receiving a "Secure Connection Failed" error. As of 2:50pm EDT (UTC-4), a configuration change was made and they are monitoring the situation. We currently do not have an ETA for resolution, however, the next scheduled update will be around 3:30pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 3:30 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 4:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 4:00 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 5:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 5:00 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 6:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 5:50 pm EDT (UTC -4)

 

Cloud Operations will be performing additional configurations changes at 9:00pm EDT (UTC-4) and will be monitoring the incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 10:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 10:02 pm EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 11:00 pm EDT (UTC-4).

 

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

**Update** Tuesday, August 11th, 10:42 pm EDT (UTC -4)

 

As the Cloud Operations Team troubleshoot this incident, we are still unable to provide anything tangible at this time. While we are still unable to provide an ETA, we will provide another update on Wednesday, August 12th at approximately 10:00 am EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 10:00 am EDT (UTC -4)

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 11:00 am EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 11:09 am EDT (UTC -4)

 

Our Cloud Operations has reverted the configurations changes that did not have any affect. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 12:00 pm EDT (UTC-4).

 

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

**Update** Wednesday, August 12th, 12:25 pm EDT (UTC -4)

 

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

 

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

**Update** Thursday, August 13th, 1:11 pm EDT (UTC -4)

 

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

Sunday, July 5th.

 

The 472 Release concluded on schedule and without incident.

 

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

As part of the upcoming 472 release, we made key improvements to the overall infrastructure. These improvements not only further Eloqua's platform scalability, they also enhance the management of historical data.

 

We have determined that the time required to apply these improvements is longer than what is typically required during a release.  As a result, for the POD1 472 Release, we are extending the maintenance window which will now start on Saturday, July 4th at 5:00pm EDT and end on Sunday, July 5th at 5:00pm EDT.  Please note this is a one-time extension and future releases will occur within our standard window.


Eloqua 472 Release


The Eloqua 472 Release will roll out between Saturday, July 4th, 2015 at 5 pm and Sunday, July 5th, 2015 at 5 pm [all times EDT (UTC -4)].

 

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both E9 and E10 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 period. You are advised to avoid using the application during this window.

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

**Update: Sunday, May 3rd 11:00 am EDT (UTC-4)**

 

The maintenance has concluded.

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

 

 


Emergency Maintenance Advisory for Wednesday, April 22nd, 2015

 

 

Eloqua will be performing a Emergency Maintenance on Wednesday, April 22nd, 2015, between 7:45 pm and 11 pm EDT (UTC -4) on Pods 1 and 2.

 

Bulk API Imports/Exports will be administratively disabled during part of this maintenance window, Insight reporting will be unavailable for up to 30 minutes.  All other application functionality will not be impacted.

 

Expected downtime as follow:

 

Maintenance Start Time: Wednesday, April 22nd, 2015 @ 19:45 EDT (UTC -4)

Maintenance End Time: Wednesday, April 22nd, 2015 @ 23:00 EDT

 

Insight Outage Start Time: Wednesday, April 22nd, 2015 @ 19:45 EDT

Insight Outage End Time: Wednesday, April 22nd, 2015 @ 20:15 EDT

 

Bulk API Outage Start Time: Wednesday, April 22nd, 2015 @ 20:00 EDT

Bulk API Outage End Time: Wednesday, April 22nd, 2015 @ 20:30 EDT

 

 

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

Sunday, April 19th.

 

The maintenance concluded on schedule and without incident.

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

Eloqua 470 Release


The Eloqua 470 Release will roll out on Sunday, April 19th, between 5 and 11 am EDT (UTC -4).

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both E9 and E10 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 period. 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).

 

  

  

  

  

  

  

 

  

 

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

**Update**

Sunday, April 12th.

 

The maintenance concluded on schedule and without incident.

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

Eloqua 470 Release


The Eloqua 470 Release will roll out on Sunday, April 12th, between 5 and 11 am EDT (UTC -4).

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both E9 and E10 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 period. You are advised to avoid using the application during this window.

 

 

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, April 1st, 2:30 am EDT (UTC -4).

 

The maintenance concluded on schedule and without incident.

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

Eloqua 470 Release


The Eloqua 470 Release will roll out between 11 pm, Tuesday, March 31st, and 5 am, Wednesday, April 1st, 2015 [all times EDT (UTC -4)].

 

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both E9 and E10 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 period. 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, March 1st, 11:18 am EST (UTC -5).

 

Our Cloud Operations Team has advised us that an estimated 1 more hour is required for them to complete the 469 Release. Another scheduled update will be provided around 12:00 pm EST (UTC-5) today.

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

**Update**

 

Sunday, March 1st, 12:08 pm EST (UTC-5).

 

The maintenance has now concluded.

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


Eloqua 469 Release


The Eloqua 469 Release will roll out on Sunday, March 1st, between 5 and 11 am EST (UTC -5).

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both E9 and E10 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 a member of 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 period. 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).

 

  

  

  

  

  

  

 

  

 

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

**Update**

Sunday, February 22nd.

 

The maintenance concluded on schedule and without incident.

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

Eloqua 469 Release


The Eloqua 469 Release will roll out on Sunday, February 22nd, between 5 and 11 am EST (UTC -5).

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both E9 and E10 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 period. You are advised to avoid using the application during this window.

 

 

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, February 18th, 3:00 am EST (UTC -5).

 

The maintenance concluded on schedule and without incident.

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

Eloqua 469 Release


The Eloqua 469 Release will roll out between 11 pm, Tuesday, February 17th, and 5 am, Wednesday, February 18h, 2015 [all times EST (UTC -5)].

 

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both E9 and E10 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 period. 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, January 18th, 10:15 am EST (UTC -5).

 

Our Cloud Operations Team has advised us that an estimated 2 more hours is required for them to complete the 468 Release. Another scheduled update will be provided around 11:00 am EST (UTC-5) today.

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

**Update**

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

 

We are now currently tracking the additional downtime via Application Unavailable / POD1 Clients. Please refer to the new system status post for updates.

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

**Update**

Sunday, January 18th, 4:45 pm EST (UTC -5).

 

The maintenance has now concluded.

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

 

Eloqua 468 Release


The Eloqua 468 Release will roll out on Sunday, January 18th, between 5 and 11 am EST (UTC -5).

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both Eloqua 9 Summer '14 Release Notes and Eloqua 10 Summer '14 Release Notes, 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.

 

During this maintenance, Eloqua will also be upgrading Insight for performance improvement and bug fixes.

NOTE: Due to this enhancement, there will be a freeze period in effect between 10 am (EST) on Friday, January 16th, and the completion of the 468 rollout, during which creation/modification of reports and new users created during the “freeze" period will not be reflected post-upgrade and will be lost.

 

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

 

  

  

  

 

  

  

  

 

  

 

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

**Update**

Sunday, January 11th, 12:00 pm EST (UTC -5).

 

The maintenance concluded on schedule and without incident.

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

Eloqua 468 Release


The Eloqua 468 Release will roll out on Sunday, January 11th, between 5 and 11 am EST (UTC -5).

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both Eloqua 9 Summer '14 Release Notes and Eloqua 10 Summer '14 Release Notes, 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.

 

During this maintenance, Eloqua will also be upgrading Insight for performance improvement and bug fixes.

NOTE: There is a freeze period now in effect, that will end with the completion of the maintenance, during which creation/modification of reports and new users created during the “freeze" period will not be reflected post-upgrade and will be lost.

 

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 period. You are advised to avoid using the application during this window.

 

 

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, January 7th, 3:35 am EST (UTC -5).

 

The maintenance concluded on schedule and without incident.

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


Eloqua 468 Release


The Eloqua 468 Release will roll out between 11 pm, Tuesday, January 6th, and 5 am, Wednesday, January 7th, 2015 [all times EST (UTC -5)].

 

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both Eloqua 9 Summer '14 Release Notes and Eloqua 10 Summer '14 Release Notes, 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 period. 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).

 

  

  

  

 

  

  

  

 

  Ken Carneiro-Oracle

Eloqua Support Holiday Schedule

Posted by Ken Carneiro-Oracle  Dec 22, 2014   

 

 

  

 

Happy Holidays from the Oracle Marketing Cloud Support Team

 


Due to the holidays, we have changed our hours of operations.

 

December 22 and 23 - normal 24 hour operations

December 24 - 12 midnight to 8pm EST (UTC -5)

December 25 - Closed

December 26 - 8 am to 8 pm EST

December 29 and 30 - normal 24 hour operations

December 31 - 12 midnight to 8 pm EST

January 1 2015 - Closed

January 2 - 8 am to 8 pm EST

January 5 - resume normal 24 hour operations 5 days a week

 

 

*Please note, for Emergency Severity 1 issues, we are available outside of the hours listed above. You can reach us at the following numbers:


USA & Canada: 1-866-327-8764
UK & EMEA: +44 20 3608 1304
France: +33-975181647
Germany: 0800 184 4542
Switzerland: 0800-559-851
Australia: 1-800-226-412
Singapore: 800 130 1655
Hong Kong & APAC: + 852 800 930 694

All Other Countries: 1-416-849-3247


Happy Holidays!

 

  

  

  

 

  

  

  

 

  

 

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

**Update**

Sunday, December 14th, 11:00 am EST (UTC -5).

 

The maintenance concluded on schedule and without incident.

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

 

Eloqua 467 Release - Sunday, December 14th, 2014

 

The Eloqua 467 Release will roll out between 5 and 11 am EST (UTC -5), on Sunday, December 14th, 2014.

 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both Eloqua 9 Summer '14 Release Notes and Eloqua 10 Summer '14 Release Notes, 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.

 

 

NOTE: Please check out our new product documentation site.

 

 

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

 

  

  

  

 

  

  

  

 

  

 

Eloqua 467 Release - Sunday, December 7th, 2014

 

The Eloqua 467 Release will roll out on Sunday, December 7th, between 5 and 11 am EST (UTC -5).


 

Please review the supporting resources available in the Release Resource Center. This includes Release Notes for both Eloqua 9 Summer '14 Release Notes and Eloqua 10 Summer '14 Release Notes, 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.

 

 

NOTE: Please check out our new product documentation site.

 

 

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

 

  

  

  

 

  

  

 

Actions

 

  

Filter Blog

 

  By date:




Scheduled Maintenance Advisory for Sunday, May 3rd, 2015

 

 

Eloqua will be performing a scheduled maintenance on Sunday, May 3rd, 2015, between 5 am and 11 am 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 and 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.

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

**Update**

Sunday, March 22nd, 11:00 am EDT (UTC -4).

 

Our Cloud Operations Team has advised us that an estimated 1 more hour is required for them to complete the maintenance. Another scheduled update will be provided around 12:00 pm EST (UTC-5) today.

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

 

**Update**

Sunday, March 22nd, 11:43 am EDT (UTC -4).

 

Our Cloud Operations Team has completed the hot-fixes.

 

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



Emergency Maintenance Advisory for Sunday, March 22nd, 2015

 

 

Eloqua will be performing an emergency maintenance on Sunday, March 22nd, 2015, between 5 and 11 am 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.

The Cloud Operations Team requires additional time for our POD1 468 Release, as such the application remains unavailable. They estimate an additional hour is required and we will provide another scheduled update at approximately 11:45 am EST (UTC-5) today.

 

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

**Update**

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

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. They have had to revise their earlier estimation and we are unable to provide an ETA at the moment. The next scheduled update will be at approximately 12:30 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 12:27 pm EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA at the moment. The next scheduled update will be at approximately 1:00 pm EST (UTC-5).

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

**Update**

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

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 1:30 pm EST (UTC-5).

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

**Update**

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

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 2:00 pm EST (UTC-5).

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

**Update**

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

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 2:30 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 2:25 pm EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 3:00 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 2:56 pm EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 3:30 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 3:27 pm EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 4:00 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 3:56 pm EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 4:30 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 4:28 pm EST (UTC-5).

 

Our Cloud Operations Team continues to aggressively work on resolving this incident. We are unable to provide an ETA but the next scheduled update will be at approximately 5:00 pm EST (UTC-5).

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

**Update**

Sunday, January 18th, 4:40 pm EST (UTC-5).

 

The application is now accessible.

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.

Please be advised, due to an unrecoverable hardware failure, an immediate migration of clients on a specific Database is currently underway by our Cloud Operations Team. We estimate the migration to take around 90 minutes and the next scheduled update will be around 7:00pm EST (UTC-5).

 

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

**Update**

Thursday, November 13th, 6:57 pm EST (UTC-5)


Our Cloud Operations Team continues to work on the migration. The original estimate was not sufficient and we are unable to provide an ETA at this time. For the clients affected by this incident, it should be noted that all application processing was paused during this window and inbound form data will be captured. Once the migration is complete, all processing will resume and any work items scheduled to execute during the migration window will begin processing. The next scheduled update will be around 7:45 pm EST (UTC-5).


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

**Update**

Thursday, November 13th, 7:11 pm EST (UTC-5)


Our Cloud Operations Team is targeting to have the migration completed by 8:00 pm EST (UTC-5). The next scheduled update will be around 8:10 pm EST (UTC-5).


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

**Update**

Thursday, November 13th, 8:06 pm EST (UTC-5)


Our Cloud Operations Team is completing the final phases of the migration. The next scheduled update will be around 8:30 pm EST (UTC-5).


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

**Update**

Thursday, November 13th, 8:25 pm EST (UTC-5)


Our Cloud Operations Team have completed the migration. 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.

With the pending change Salesforce.com is making to disable SSL 3.0 in favour of TLS 1.0 or higher (https://help.salesforce.com/apex/HTViewSolution?urlname=Salesforce-disabling-SSL-3-0-encryption&language=en_US), testing has shown this does not affect our client's Eloqua to Salesforce.com integration. The integration will continue to function normally.

We are currently tracking an incident where some users are receiving a permission error while saving a segment. Our Development Team is working on a path to resolution and are targeting to hot-fix this incident by end of day today. We will provide another update around 3:00 pm EST (UTC-5).

 

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

**Update**

Monday, November 3rd, 3:20 pm EST (UTC-5)


Our Development Team continues to work on this resolution and are still targeting to deploy this hot-fix by end of day. The next scheduled update will be around 6:00 pm EST (UTC-5).


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

**Update**

Monday, November 3rd, 6:20 pm EST (UTC-5)


Our Cloud Operations Team confirmed the hot-fix was applied to our Production Environment.

 

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

**Update**

Monday, November 3rd, 7:04 pm EST (UTC-5)


Our Cloud Operations Team has identified a false positive and a small percentage of clients failed deployment of the hot-fix. Our Development Team is closely working with them to resolve this in full. We are unable to provide an ETA, but the next scheduled update will be 10:00 am EST (UTC-5) on Tuesday, November 4th, 2014.

 

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

**Update**

Tuesday, November 4th, 10:00 am EST (UTC-5)


Our Cloud Operations and Development Team continue to work towards resolution, however no ETA is available. The next scheduled update will be around 1:00 pm EST (UTC-5).

 

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

**Update**

Tuesday, November 4th, 1:00 pm EST (UTC-5)


Our Development Team continue to work on a hot-fix that will address the small percentage of clients still experiencing the issue. There is no ETA available but the next scheduled update will be around 4:00 pm EST (UTC-5).

 

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

**Update**

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


Our Development Team continues to work on this resolution. We are unable to provide an ETA, but the next scheduled update will be around 10:00 am EST (UTC-5) on Wednesday, November 5th, 2014.

 

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

**Update**

Wednesday, November 5th, 10:10 am EST (UTC-5)

Our Development Team is currently reviewing a fix for this incident. We are currently unable to provide an ETA for when this fix will be applied. The next update will be at approximately 1:00 pm EST (UTC -5)


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

**Update**

Wednesday, November 5th, 12:55 pm EST (UTC-5)

Our Development Team is still reviewing a fix for this incident. We are currently unable to provide an ETA for when this fix will be applied. The next update will be at approximately 4:00 pm EST (UTC -5)


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

**Update**

Wednesday, November 5th, 4:00 pm EST (UTC-5)

Our Development Team continues to review the fix for this incident. We are currently unable to provide an ETA for when this fix will be applied. The next update will be around 10:00 am EST (UTC-5) on Thursday, November 6th, 2014.


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

**Update**

Thursday, November 6th, 10:00 am 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 at approximately 1:00 pm EST (UTC -5)


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

**Update**

Thursday, November 6th, 1:00 pm EST (UTC-5)

Our Development Team is still testing a fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 4:00 pm EST (UTC -5)


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

**Update**

Thursday, November 6th, 4:00 pm EST (UTC-5)

Our Development Team continues to test a fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 10:00 am EST (UTC-5) on Friday, November 7th, 2014.


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

**Update**

Friday, November 7th, 10:00 am EST (UTC-5)

Our Development Team is still working to fully test the fix for this incident. We cannot at this time provide an ETA. The next update will be at approximately 1:00 pm EST (UTC-5)


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

**Update**

Friday, November 7th, 1:00 pm EST (UTC-5)

Our Clouds Operations Team is targeting to hot-fix this incident by end of day today. We will provide another update at approximately 4:00 pm EST (UTC-5)


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

**Update**

Friday, November 7th, 3:00 pm EST (UTC-5)

Our Cloud Operations Team has confirmed that the fix has been applied to our Production Environment and the issue is now resolved.

Our Cloud Operations Team is currently investigating an incident where Eloqua Insight is unavailable on POD 1 and 3. While we do not currently have an ETA, the next update is scheduled for 9:30 am EDT (UTC -4).


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

**Update**

Friday, October 10th, 8:53 am EDT (UTC -4)


Our Cloud Operations Team was able to restore services for our POD 3 customers and they are still aggressively working on POD 1. While we do not currently have an ETA, the next update is scheduled for 10:00 am EDT (UTC -4).


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

**Update**

Friday, October 10th, 9:14 am EDT (UTC -4)


Our Cloud Operations Team was able to restore services for our POD 1 customers as well.


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 Development Team is actively investigating an incident where Segments containing the Form Submits criteria are incorrectly calculating. We recommend clients review any campaigns that may be configured with this. While we currently do not have an ETA, we will provide another update around 1:00 pm EDT (UTC-4).

 

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

**Update**

Wednesday, October 8th, 11:38 am EDT (UTC -4)


Our Development Team has crafted a hot-fix for this incident. While it is currently making it way through our hot-fix process, the team is targeting to get this pushed to production within the next few hours. We will provide another update around 1:00 pm EDT (UTC-4).


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

**Update**

Wednesday, October 8th, 12:51 pm EDT (UTC -4)


Our Development and Development Operations Team are still working though the hot-fix process. We will provide another update around 2:30 pm EDT (UTC-4).


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

**Update**

Wednesday, October 8th, 2:26 pm EDT (UTC -4)


Our Development and Development Operations Team continue to work through the hot-fix process. We are still targeting to get this completed before the end of the day. We will provide another update around 4:30 pm EDT (UTC-4).


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

**Update**

Wednesday, October 8th, 4:19 pm EDT (UTC -4)


Our Cloud Operations Team is currently working through the final steps of the hot-fix process. We will provide another update around 6:30 pm EDT (UTC-4).


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

**Update**

Wednesday, October 8th, 5:00 pm EDT (UTC -4)


This incident has been hot-fixed to Production and considered resolved.

As of 03-OCT-2014, Oracle Cloud Team has completed applying patches for vulnerability CVE-2014-7169 against those systems that were determined to be vulnerable in Oracle Eloqua. Customers should refer to the published Security Alert Advisory for more information about the technical content of these patches.  Oracle continues to monitor reports of additional CVEs related to Bash, and will address vulnerabilities in accordance with its vulnerability handling policies.

 

For More Information:

 

The advisory for Security Alert CVE-2014-7169 is located at http://www.oracle.com/technetwork/topics/security/alert-cve-2014-7169-2303276.html


More information has also been published at http://www.oracle.com/technetwork/topics/security/bashcve-2014-7169-2317675.html


The Oracle Software Security Assurance web site is located at http://www.oracle.com/us/support/assurance

Our Cloud Operations Team has identified a backlog with the Data Import Queues for POD1. We are estimating within 2 hours the queues should be cleared up.

 

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

**Update**

Thursday, October 2nd, 9:25 am EDT (UTC -4)

 

Our Cloud Operations Team has confirmed the Data Import Queues are now healthy.

Our Cloud Operations Team investigated and resolved an incident where Emails Sends from POD 1 were impacted. There is currently a backlog and the queues are processing. We estimate the queues should clear up within the next hour.

 

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

**Update**

Thursday, October 2nd, 2:17 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.


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

**Update**

Thursday, October 2nd, 9:26 am EDT (UTC -4)

 

Our Cloud Operations Team has confirmed our Email Queues are now healthy.

Filter Blog

By date: By tag: