Skip navigation

We are currently experiencing network issues which is affecting the availability of the Eloqua Application for POD 3 clients. We are currently working to resolve this issue and will provide an update at 10:30 am EST (UTC -5).


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

**Update**

Monday, January 27th, 10:17 am EST (UTC -5)

 

Our Production Team is still working through resolving this incident and will provide an update around 10:45 am EST (UTC -5).


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

**Update**

Monday, January 27th, 10:41 am EST (UTC -5)

 

Our Production Team attempted one solution that failed to resolve this incident and have engaged additional resources. We cannot provide an ETA for full resolution, but we will provide another update around 11:15 am EST (UTC -5).


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

**Update**

Monday, January 27th, 11:35 am EST (UTC -5)

 

Web requests have begun to process. We will continue to monitor the situation. At this time the application is available for all POD3 clients.

Due to a Certificate update, as of Sunday, January 26th, 2014, the address bar when logging into Pod 1 installs will no longer display "Eloqua Corporation [CA]", but will instead show "Oracle [US]".

 

Previous:

Eloqua Address Bar.jpg

 

Current:

Eloqua Address Bar - New.jpg

 

No other changes are associated to this update.

**Update**

Sunday, January 26, 2:30 pm EST (UTC -5)

 

Maintenance concluded successfully and on time. No issues have been identified.


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


Eloqua will be performing maintenance and hardware upgrades on Sunday, January 26th, between 5:00 am and 11:00 am EST (UTC -5).

 

During this maintenance period:

 

• Insight reporting will be unavailable for periods of the maintenance

• Forms and email responses will be lost during hardware reboots (5-10 minutes)

• Application processing will be paused, and resumed after maintenance completes

 

You are advised to avoid using the application or scheduling email batches during this window.

 

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

We are currently experiencing an issue with Email Sends. When attempting to send an email, you may receive the following error:

 

Error occurred while trying to connect to the smtp server. Please contact the technical support team.

 

We are currently working on a resolution to this issue. A further update will be provided at 1:30 pm EST (UTC -5) or as soon as we have any additional information.

 

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

**Update**

Wednesday, January 22, 1:21 pm EST (UTC -5)

 

We have now identified that this issue is not only affecting Test Sending. We are no longer actively seeing the error, but are continuing to investigate the cause. The next update will be at 2:00 pm EST (UTC -5) or as soon as we have any further information.

 

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

**Update**

Wednesday, January 22, 2:00 pm EST (UTC -5)

 

We are still currently investigating the cause of this issue. We have not seen a new occurrence of this error since approximately 1:20 pm EST (UTC -5). The next update will be at 3:00 pm EST (UTC -5) or as soon as we have any further information.

 

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

**Update**

Wednesday, January 22, 2:18 pm EST (UTC -5)

 

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.

Eloqua will be performing an emergency hot-fix on Sunday, January 19th starting at 7:00 am EST (UTC-5).


The impact of the Eloqua Service will be moderate, the service that we need to redeploy is related CRM Integration and Transaction Emails (Notifications). There will be an overall performance decrease using the Eloqua Application while we are deploying this hot-fix. 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.


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


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

**Update**

Sunday, January 19th, 7:27 am EST (UTC -5)

 

The Production Team started the hot-fix process around 7:00 am EST (UTC-5). The next update will be around 9:00 am EST (UTC-5).

 

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

**Update**

Sunday, January 19th, 8:03 am EST (UTC -5)

 

The hot-fix completed at 7.55 am EST (UTC-5)

We are currently experiencing network issues which is affecting the availability of the Eloqua Application for POD 1 and 3 clients. We are currently working to resolve this issue and will provide an update at 2:00 pm EST (UTC -5).


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)

 

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

**Update**

Wednesday, January 15th, 1:21 pm EST (UTC -5)

 

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.

We are currently experiencing network issues which are affecting the availability of the Eloqua Application for POD 1 and 2 clients. We are currently working to resolve this issue and will provide an update at 2:30 PM EST (UTC -5), or as soon as we have any additional information.

 

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

**Update**

Tuesday, January 14th, 2:30 pm EST (UTC -5)

 

We are still investigating the cause of this issue.

 

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

**Update**

Tuesday, January 14th, 3:00 pm EST (UTC -5)

 

We are still investigating the cause of this issue.

 

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

**Update**

Tuesday, January 14th, 3:30 pm EST (UTC -5)

 

We are still investigating the cause of this issue.

 

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

**Update**

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

 

We are still investigating the cause of this issue. The next update will be at approximately 4:30 pm EST (UTC -5) or as soon as we have any additional information.

 

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

**Update**

Tuesday, January 14th, 4:30 pm EST (UTC -5)

 

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

Tuesday, January 14th, 5:30 pm EST (UTC -5)

 

We are still experiencing intermittent network connectivity issues. We continue to work on resolving this issue, and will provide an update as soon as we have any additional information.

 

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

**Update**

Tuesday, January 14th, 6:15 pm EST (UTC -5)

 

We continue to investigate the cause of this issue, and will regularly update this post.


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

**Update**

Tuesday, January 14th, 7:10 pm EST (UTC -5)

 

Our Production Team continues to investigate this incident. At this time, we cannot offer an ETA, but the next scheduled update will be around 8:15 pm EST (UTC -5) or as soon as we have any additional information available.


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

**Update**

Tuesday, January 14th, 8:10 pm EST (UTC -5)

 

Our Production Team continues to investigate this incident as restoring the Eloqua Service is our top priority. At this time, we cannot offer an ETA, but the next scheduled update will be around 9:15 pm EST (UTC -5) or as soon as we have any additional information available.


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

**Update**

Tuesday, January 14th, 9:40 pm EST (UTC -5)

 

Our Production Team continues to investigate this incident. At this time we cannot offer an ETA. The next scheduled update will be at approximately 11:00 pm EST (UTC -5) or as soon as we have any additional information available.


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

**Update**

Tuesday, January 14th, 11:30 pm EST (UTC -5)

 

The issue was resolved as of 10:38 pm EST. 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.

Eloqua will be performing an emergency hot-fix later today on Wednesday, January 8th.


The impact of the Eloqua Service will be minimal, but there is potential for some customer impact. The service that we need to redeploy is the one that compiles recipients in the Eloqua 9 Email Batch Wizard.

 

During this hot-fix, there is a chance that a user who is in the middle of the Email Batch Wizard (generally on step 2), may see that step hang. The user would need to restart the batch wizard in this scenario.

 

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

 

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

**Update**

Wednesday , January 8th, 3:38 pm EST (UTC -5)

 

The hot-fix completed at 3.35 pm EST (UTC-5)

**UPDATE**

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

 

Maintenance concluded at 10:28 am without issues.


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


Emergency Maintenance Advisory for Sunday, January 5th, 2014

 

 

Eloqua will be performing emergency maintenance on Sunday, January 5th, between 6 and 10 AM EST (UTC -5).

 

During this maintenance, there will be a period of time when queuing of deployments will fail to execute - areas such as form submissions, quicksends, engage, etc. will not send out emails. These email notifications will be in a hard fail status and cannot be recovered.

 

You are advised to monitor previously scheduled batches, and to not create any new batches for this time period.

 

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

Filter Blog

By date: By tag: