Cronofy incident

Degraded Sync performance for Microsoft 365

Minor Resolved View vendor source →

Cronofy experienced a minor incident on November 25, 2024 affecting Microsoft 365, lasting 5h 59m. The incident has been resolved; the full update timeline is below.

Started
Nov 25, 2024, 04:27 PM UTC
Resolved
Nov 25, 2024, 10:27 PM UTC
Duration
5h 59m
Detected by Pingoru
Nov 25, 2024, 04:27 PM UTC

Affected components

Microsoft 365

Update timeline

  1. identified Nov 25, 2024, 04:27 PM UTC

    We have been tracking a degradation in MS Graph connections since approximately 07:30 UTC today. While most operations have been succeeding in short order, this has worsened to the point where sync is starting to be noticeably degraded for some accounts. Microsoft are reporting on this as incident "MO941162". We are continuing to monitor and mitigate where we can, and will provide another update at 17:30 UTC.

  2. identified Nov 25, 2024, 05:31 PM UTC

    Many Graph API calls to Microsoft 365 are still timing out and we have yet to see any improvement. We are continuing to monitor the situation and mitigate any impact on operations. We will update again at 18:30 UTC.

  3. monitoring Nov 25, 2024, 06:27 PM UTC

    Many calls to Microsoft 365 are still failing. We have seen some improvement over the past hour but are still far from a full recovery. Synchronization of affected calendars will be degraded with failures retried automatically as required. Microsoft are reporting on this as incident MO941162, with fixes in progress but currently no timeline to resolution. We are continuing to monitor and mitigate where we can, and will provide another update by 19:30 UTC.

  4. monitoring Nov 25, 2024, 07:29 PM UTC

    We have seen little further improvement of reliability of calls to Microsoft 365. We are continuing to monitor our systems and Microsoft incident MO941162. Sync tasks continue to retry automatically. We will provide a further update by 20:30 UTC.

  5. monitoring Nov 25, 2024, 08:26 PM UTC

    We have seen little improvement of reliability of calls to Microsoft 365. However, we are now well past the busiest point of the day for Cronofy's services which means we're in a more stable position overall. We are continuing to monitor our systems and Microsoft incident MO941162. Microsoft are continuing to work on the underlying issue and sync tasks continue to retry automatically. We will provide a further update by 21:30 UTC.

  6. monitoring Nov 25, 2024, 09:27 PM UTC

    We have seen some improvement in the reliability of calls to Microsoft 365, but are far from normal service. We remain past the busiest point of the day for Cronofy's services which means we're in a more stable position overall. We are continuing to monitor our systems and Microsoft incident MO941162. Microsoft are continuing to work on the underlying issue and sync tasks continue to retry automatically. We will provide a further update by 22:30 UTC.

  7. resolved Nov 25, 2024, 10:27 PM UTC

    We have seen a significant improvement in the reliability of calls to Microsoft 365. This has now been close to, or within, the bounds of usual behavior for around an hour. This aligns with Microsoft's communication against incident MO941162. Microsoft are not saying it is fully resolved but that they have mitigations in place, and are continuing work to fully resolve the problem. As the impact of this has been minimal for a significant period, we are resolving this incident. We will keep a closer eye on this area until Microsoft call their incident resolved as well.