Discussions

GREEN / Insight Loading Slowly / All / RESOLVED

Micheal Brown-Oracle
edited Nov 25, 2014 9:14AM in Eloqua System Status

We are currently experiencing intermittent timeouts and connection errors with Eloqua Insight. Our Cloud Operations Team is currently working alongside a vendor to resolve the underlying cause of the long load time on first connection.

Our teams have put in place additional monitoring and have taken measures to limit the length of these occurrences while we work towards a definitive resolution.

We are committed to providing daily updates until a resolution is found.

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

**Update**

Thursday, October 23rd, 12:45 pm EDT (UTC -4)

Our Cloud Operations Team continues to work alongside our vendor to come to a resolution. We will update this post again tomorrow with further information.

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

**Update**

Monday, October 27th, 2:10 pm EDT (UTC -4)

Our Cloud Operations Team has worked with the vendor to put in place measures to alleviate the root cause. Users should no longer be experiencing slow load on initial opening of Eloqua Insight.

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

**Update**

Tuesday, October 28th, 1:55 pm EDT (UTC -4)

Our Cloud Operations Team continues to work with a vendor to diagnose and correct the cause of these occurrences on POD 3. To clarify yesterday's update, on POD 1 changes have been put in place that do not resolve the root cause but do greatly reduce the occurrence and duration of incident.

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

**Update**

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

Our Cloud Operations Team has made further changes to help alleviate the delays felt on POD 3. They continue to work alongside a vendor to find a resolution to the root cause of these issues.

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

**Update**

Thursday, October 30th, 3:00 pm EDT (UTC -4)

Our Cloud Operations Team continues to work with a vendor to diagnose and find a resolution to the root cause of these issues.

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

**Update**

Friday, October 31st, 2:45 pm EDT (UTC -4)

Our Cloud Operations Team continues to work alongside a vendor to find a resolution to the root cause of these issues.

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

**Update**

Tuesday, November 4th, 9:15 am EST (UTC -5)

Our Cloud Operations Team continues to monitor the workarounds put in place to ensure better stability on PODs 1 and 3, and continue to work alongside our vendors to find a resolution to the root cause.

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

**Update**

Wednesday, November 5th, 1:29 pm EST (UTC -5)

Our Cloud Operations Team continues to work with our vendor to come to a resolution of the root cause of these incidents.

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

**Update**

Thursday, November 6th, 2:40 pm EST (UTC -5)

Our Cloud Operations and Development Teams continue to collaborate with our vendor to identify and fix the root cause of these incidents, however at this time we cannot provide an ETA for resolution.

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

**Update**

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

Our Cloud Operations Team continues to work alongside our vendor to diagnose and rectify the cause of these incidents. We do not currently have an ETA for resolution.

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

**Update**

Monday, November 10th, 5:20 pm EST (UTC -5)

Our Cloud Operations Team continues to collaborate with development and our vendor to determine the root cause of these incidents. We do not currently have an ETA for resolution to provide.

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

**Update**

Tuesday, November 11th, 5:10 pm EST (UTC -5)

Our Cloud Operations Team continues to monitor the measures already implemented, and continue to work alongside our vendors to find a resolution to the root cause.


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

**Update**

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

Our Cloud Operations Team continues to work with our vendor to come to a resolution of the root cause of these incidents.


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

**Update**

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

Our Cloud Operations and Development Teams continue to collaborate with our vendor to identify and fix the root cause of these incidents, however at this time we cannot provide an ETA for resolution.

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

**Update**

Friday, November 14th, 4:55 pm EST (UTC -5)

Our Cloud Operations Team continues to work alongside our vendor to diagnose and rectify the cause of these incidents. We do not currently have an ETA for resolution.


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

**Update**

Monday, November 17th, 6:47 pm EST (UTC -5)

Our Cloud Operations Team continues to collaborate with development and our vendor to determine the root cause of these incidents. We do not currently have an ETA for resolution to provide.


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

**Update**

Tuesday, November 18th, 3:05 pm EST (UTC -5)

Our Cloud Operations Team continues to work with our vendor to come to a resolution of the root cause of these incidents.


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

**Update**

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

Our Cloud Operations Team continues to work alongside our vendor to diagnose and rectify the cause of these incidents. We do not currently have an ETA for resolution.


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

**Update**

Thursday, November 20th, 3:12 pm EST (UTC -5)

Our Cloud Operations Team continues to monitor the measures already implemented, and continue to work alongside our vendors to find a resolution to the root cause.


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

**Update**

Tuesday, November 25th, 9:08 am EST (UTC -5)

The measures put in place by our Cloud Operations Team have put in place have resolved the incidents of Eloqua Insight long load times. We will continue to monitor the situation, however at this time long load times with Insight are no longer being experienced.


Post edited by Unknown User on
Tagged: