Following yesterday's Eloqua Insight Incident, the Development team is continuing towards a path to resolution. While only users created prior to 28/10/2013 @ 5:30 pm EDT have access to Eloqua Insight, if users require access and created after the aforementioned date, or need to modify their Eloqua Insight access level (such as moving from Eloqua Reporting to Eloqua Analyzer) – please contact our Eloqua Support Team and they will be able to assist in the interim.

 

Our next schedule update on this incident will be Thursday, October 31st around 4:00 pm EDT (UTC -4)

 

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

Thursday, October 31st, 9:50 am EDT (UTC -4)


The Development Team has been working with both our QA Team and Production Team. We are targeting to hot-fix this incident today at 11:00 am EDT (UTC-4). After the hot-fix process is complete, we will provide another update around 11:45 am EDT (UTC-4)

 

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

**Update**

Thursday, October 31st, 12:30 pm EDT (UTC -4)


The Development Team is continuing to work with both our QA Team and Production Team. The hot-fix scheduled for 11:00 am EDT (UTC-4) was unsuccessful. We don't have an ETA to offer, but our next schedule update on this incident will be around 4:30 pm EDT (UTC -4)


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

**Update**

Thursday, October 31st, 3:17 pm EDT (UTC -4)


We were able to split the original hot-fix into three phases. We are currently working on hot-fixing phase 1; phase 2 and 3 have yet to be scheduled.  Our next schedule update on this incident will be Friday, November 1st around 11:00 am EDT (UTC -4)

 

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

**Update**

Friday, November 1st, 10:02 am EDT (UTC -4)


We are looking into hot-fixing phase 2 as part of our Service Pack release this weekend, Sunday, November 3rd, 2013.  Our next schedule update on this incident will be Monday, November 4th around 11:30 am EDT (UTC -5)

 

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

**Update**

Monday, November 4th, 10:02 am EDT (UTC -5)


We are targeting to complete phase 2 and 3 this week.  At this time, we cannot provide an ETA, but our next schedule update on this incident will be Tuesday, November 5th around 11:30 am EDT (UTC -5)


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

**Update**

Monday, November 6th, 2:03 pm EDT (UTC -5)


We are targeting to complete phase 2 in the next day.  Our next schedule update on this incident will be Thursday, November 7th around 1:30 pm EDT (UTC -5)


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

**Update**

Thursday, November 7th, 1:14 pm EST (UTC -5)


In lieu of the recent Eloqua Insight maintenance that went out last night, we are targeting to complete phase 2 on Friday, November 8th, 2013. Our next schedule update on this incident will be Friday, November 8th around 1:30 pm EST (UTC -5)


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

**Update**

Friday, November 8th, 10:20 am EST (UTC -5)


We are re-targeting to complete phase 2 on Monday, November 11th, 2013. Our next schedule update on this incident will be Monday, November 11th around 2:00 pm EST (UTC -5)


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

**Update**

Monday, November 11th, 12:09 pm EST (UTC -5)


We are currently patching phase 2 to all PODs, the next update will be around 4:00 pm EST (UTC -5)


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

**Update**

Monday, November 11th, 2:36 pm EST (UTC -5)


Phase 2 has been pushed to production. Our next schedule update on this incident will be Thursday, November 14th around 2:00 pm EST (UTC -5) with respects to Phase 3.


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

**Update**

Friday, November 15th, 12:48 pm EST (UTC -5)


We are looking to hot fix Phase 3. At this time, we cannot provide an ETA, but our next schedule update on this incident will be Monday, November 18th around 2:00 pm EST (UTC -5).


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

**Update**

Tuesday, November 26th, 12:48 pm EST (UTC -5)


Phase 3 was hot-fixed on November 18th around 5.30 pm EST (UTC-5). This issue is considered resolved.