Skip navigation

Our Cloud Operations Team is currently investigating an incident where clients on POD 3 may experience performance degradation while working in Eloqua Apps. We do not currently have an ETA for resolution, and the next update will be at 5pm UTC.

 

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

**Update** Friday, July 14th, 1:40 PM UTC

 

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

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

**Update** Friday, July 14th, 1:52 PM UTC

 

Our Cloud Operations Team has confirmed that the issue is still reoccurring. We do not currently have an ETA for resolution, and the next update will be at 5pm UTC.

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

**Update** Friday, July 14th, 2:27 PM UTC

 

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

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

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

**Update** Saturday, July 22nd, 2017, 3:29 AM UTC

 

The maintenance for POD 1 has concluded.

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

**Update** Saturday, July 22nd, 2017, 2:43 AM UTC

 

The maintenance for POD 3 has concluded.

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

**Update** Saturday, July 22nd, 2017, 1:22 AM UTC

 

The maintenance for POD 4 has concluded.

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

**Update** Saturday, July 22nd, 2017, 1:18 AM UTC

 

The maintenance for POD 2 has concluded.

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

**Update** Friday, July 21st, 2017, 9:54 PM UTC

 

The maintenance for POD 6 has concluded.

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

**Update** Friday, July 21st, 2017, 11:54 AM UTC

 

The maintenance for POD 7 has concluded.

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

 

Oracle Eloqua Apps Release: Version 236

 

 

The Eloqua Apps 'Version 236' Release is on its way. Your Eloqua instance will be seeing the new enhancements on Friday, July 21st, 2017.

 

The Version 236 rollout starting Friday, July 21st, 2017.

 

The per pod schedule is as follows:

 

  • POD 1, 2, 3, 4: Saturday, July 22nd from 12am to 5am UTC
  • POD 6: Friday, July 21st at 8pm to Saturday, July 22nd at 1am UTC
  • POD 7: Friday, July 21st from 10am to 3pm UTC

 

Profiler and applications hosted at 'apps.p01.eloqua.com' (for Pod 1) ,'apps.p02.eloqua.com' (for Pod 2), etc will not be configurable during the maintenance window.

 

Please review the supporting resources available in the Topliners Release Resource Center and in the Recent Versions: What's New doc.

 

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

 

To determine your POD:

Log into Eloqua as you normally would.

Look at the browser URL once you are logged in.

Your POD URL has the following format: secure.p01.eloqua for POD 1, secure.p02.eloqua.com for POD 2, etc.

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

**Update** Tuesday, July 11th, 7:50 PM UTC

POD 2, 3, 6, 7 emergency maintenance period is completed and production use of your instance has been restored.

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

**Update** Tuesday, July 11th, 5:50 PM UTC

POD 3, 6, 7 Emergency maintenance has begun, updates will be made here as they progress.

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

**Update** Tuesday, July 11th, 5:21 PM UTC

POD 2 Emergency maintenance has begun, updates will be made as we progress through the various PODs

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

Emergency Maintenance Advisory: Tuesday, July 11th, 2017

 

 

Eloqua will be performing emergency maintenance on Tuesday, July 11th, 2017 between 4 pm to 8 pm UTC.

 

During your POD's maintenance, the following will be unavailable: Application access, API, landing pages and forms.

Our System Status page on Topliners will be updated with progress during the window.

Our Cloud Operations Team have identified an issue where some POD 3 clients will not be able to log into the Eloqua application. We do not currently have an ETA for resolution. The next update will be at approximately 2 pm UTC.

 

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

**Update** Tuesday, July 4th, 2:00 PM UTC

 

Our Cloud Operations Team has identified the root cause of this incident. They are currently working towards resolving the issue. No ETA is available, the next update will be at approximately 3 pm UTC.

 

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

**Update** Tuesday, July 4th, 3:00 PM UTC

 

Our Cloud Operations Team continues to work on resolving this incident. No ETA is available, the next update will be at approximately 4 pm UTC.

 

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

**Update** Tuesday, July 4th, 4:00 PM UTC

 

Our Cloud Operations Team continues to work on resolving this incident. No ETA is available, the next update will be at approximately 5 pm UTC.

 

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

**Update** Tuesday, July 4th, 4:25 PM UTC

 

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

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

Filter Blog

By date: By tag: