Cronofy incident

Degraded sync performance for Microsoft 365

Minor Resolved View vendor source →

Cronofy experienced a minor incident on January 22, 2026 affecting Microsoft 365, lasting 2h 1m. The incident has been resolved; the full update timeline is below.

Started
Jan 22, 2026, 11:18 PM UTC
Resolved
Jan 23, 2026, 01:19 AM UTC
Duration
2h 1m
Detected by Pingoru
Jan 22, 2026, 11:18 PM UTC

Affected components

Microsoft 365

Update timeline

  1. investigating Jan 22, 2026, 11:18 PM UTC

    We are currently investigating degraded sync performance for Microsoft 365 as we are experiencing a much higher error rate than normal.

  2. monitoring Jan 22, 2026, 11:28 PM UTC

    We believe this is related to a Microsoft incident (ID: MO1221364). We are keeping a close eye on how this progresses

  3. monitoring Jan 23, 2026, 12:01 AM UTC

    We are continuing to monitor the situation, but have not seen any improvement so far

  4. resolved Jan 23, 2026, 01:19 AM UTC

    Between 22:00 and 01:15 UTC we saw elevated error rates when performing sync operations with Microsoft 365. Microsoft continues to work on a full resolution to the incident with ID MO1221364. However, the error rates we are now observing are back to normal levels.