RethinkBH incident

Reports of site slowness

Notice Resolved View vendor source →

RethinkBH experienced a notice incident on July 15, 2024, lasting 2d 21h. The incident has been resolved; the full update timeline is below.

Started
Jul 15, 2024, 05:13 PM UTC
Resolved
Jul 18, 2024, 02:49 PM UTC
Duration
2d 21h
Detected by Pingoru
Jul 15, 2024, 05:13 PM UTC

Update timeline

  1. investigating Jul 15, 2024, 05:13 PM UTC

    We are investigating reports of site slowness and are working to resolve them as quickly as possible. We will continue to provide updates as we have more information.

  2. identified Jul 15, 2024, 06:01 PM UTC

    The site slowness appears to be tied to updates made by Microsoft over the weekend. We are currently working with Microsoft to resolve this issue as quickly as possible.

  3. monitoring Jul 15, 2024, 06:47 PM UTC

    The issue has now been resolved. We are continuing to monitor site performance and will update this page with any updates.

  4. investigating Jul 17, 2024, 01:23 PM UTC

    We have begun receiving new reports of site slowness. We are investigating them and working on resolving them as quickly as possible. We will continue to provide updates as we have more information.

  5. identified Jul 17, 2024, 01:51 PM UTC

    The cause of this issue has been identified and a fix has been implemented. Site performance should be returning to normal.

  6. monitoring Jul 17, 2024, 03:26 PM UTC

    This morning, we experienced an issue with our scale-out rules with Microsoft, which typically allocate additional servers to the website before business hours. As a result, the website experienced slower performance. Multiple Microsoft customers reported similar issues, indicating a potential problem on Microsoft's end. The issue was addressed with Microsoft and we were able to scale out to more servers. This change has restored the website to its normal capacity. The site is currently operating as expected, and we are continuing to conduct tests to ensure stability.

  7. resolved Jul 18, 2024, 02:49 PM UTC

    This incident has been resolved.