Forum Stats

  • 3,678,542 Users
  • 7,135 Discussions
  • 12,060 Comments

Discussions

GREEN / Cloud Components Intermittently Unresponsive / POD 1 / RESOLVED

Jonathan.Turiano-Oracle
edited Oct 23, 2014 10:19AM in Eloqua System Status

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.

Post edited by Unknown User on
Tagged: