Bridge incident

Bridge Analytics: Increased failure rates with scheduled reports

Minor Resolved View vendor source →

Bridge experienced a minor incident on May 1, 2023 affecting Analytics, lasting 2d 2h. The incident has been resolved; the full update timeline is below.

Started
May 01, 2023, 05:07 PM UTC
Resolved
May 03, 2023, 07:41 PM UTC
Duration
2d 2h
Detected by Pingoru
May 01, 2023, 05:07 PM UTC

Affected components

Analytics

Update timeline

  1. investigating May 01, 2023, 05:07 PM UTC

    We are currently seeing an increase in scheduled reports failing within Bridge analytics and we are investigating this issue with our partners. We will provide an update as soon as we can. Thank you for your patience!

  2. identified May 02, 2023, 02:35 PM UTC

    We are working closely with our analytics partners to provide a long term stable solution across the Bridge Analytics platform. We expect a resolution to be in place by the end of the week and we will provide additional updates as progress continues. We appreciate your patience while we actively work to resolve this issue!

  3. identified May 02, 2023, 09:01 PM UTC

    We are continuing to work with our partners for a resolution to the issues impacting scheduled reports. We will be performing maintenance on the Analytics feature within Bridge tomorrow morning: Wednesday, May 3, 2023, between 1:00 AM EDT and 5:00 AM EDT (between 5:00 AM UTC and 9:00 AM UTC). Once this maintenance event is complete, our expectation is that scheduled reporting will resume. We'll provide an additional update after that time.

  4. monitoring May 03, 2023, 03:50 PM UTC

    Our team has been able to work with our partners to implement a fix to resolve the issues being seen with Bridge Analytics and scheduled reports. There will be an additional maintenance window required as we implement a long term solution to avoid these types of issues, We will communicate the date and time of that window as soon as we can. In the meantime, we are continuing to monitor the updates made to resolve the issue. Thanks again for your patience!

  5. resolved May 03, 2023, 07:41 PM UTC

    This incident has been resolved.