Cronofy incident

Increased error rates for some Google calendar sync operations

Minor Resolved View vendor source →

Cronofy experienced a minor incident on June 2, 2026 affecting Google, lasting 6h 49m. The incident has been resolved; the full update timeline is below.

Started
Jun 02, 2026, 01:40 PM UTC
Resolved
Jun 02, 2026, 08:29 PM UTC
Duration
6h 49m
Detected by Pingoru
Jun 02, 2026, 01:40 PM UTC

Affected components

Google

Update timeline

  1. monitoring Jun 02, 2026, 01:40 PM UTC

    Google's API is returning an increased number of 503 errors when we attempt to sync calendars. This affects a small percentage of calendars, and some users may see delayed calendar syncs as a result. We're continuing to monitor.

  2. monitoring Jun 02, 2026, 04:55 PM UTC

    We are continuing to see elevated errors when communicating with Google Calendar. Cronofy is operating normally - event changes are still syncing correctly. The only impact is that some changes may take slightly longer to be reflected in Google Calendars than usual. We are continuing to monitor the situation, but will only update this incident if there is a significant change in either direction.

  3. resolved Jun 02, 2026, 08:29 PM UTC

    Events continue to sync events into Google Calendars as normal. We are still seeing an elevated number of errors between Cronofy and Google Calendar, but are confident that our system are keeping events in sync correctly. The vast majority of events are still syncing almost immediately, while a minority of updates sync after a few seconds. This should have no impact on customers applications, so we are resolving the incident. We will continue to monitor the situation and will raise a new incident if performance declines to a noticeable level.