Looking for an update now? Check the current status, or follow Cronofy for future changes.
100%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
4 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Event Triggers not sending in US data center
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A failing component in our US data center led to scheduled notifications for Event Triggers backing up and not sending. We've resolved the immediate cause, which will lead to notifications being delivered behind schedule.
We are monitoring this and investigating any wider impact from the issue.
investigating
We are investigating an issue where Event Trigger notifications are failing to send in our US data center
June 2026
Increased API errors in our US data center
minorSource not attested
Last archived state: resolved
View archived record details
identified
We've been monitoring an issue on a cache cluster node since shortly after the maintenance at the weekend. As part of mitigation, customers may see increased errors from the API for a short time period. We will begin the mitigation momentarily.
Google Meet Meeting Agents failing to join
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are now rolling out a further fix which has tested well internally, and will continue to monitor its performance.
monitoring
After monitoring we've seen that the fix has improved performance but we're still seeing elevated cases of failures to join Google Meet Meetings, so are still working improving things further.
monitoring
Google Meet Meeting Agents are making join attempts successfully since the fix release earlier. We will continue to monitor their performance.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are rolling out a fix which has tested positively internally, and will be monitoring success rates
investigating
We have seen that Google Meet Meeting Agents are being rejected from the meetings before being able to join and are investigating the issue.
These meetings will fail to be recorded and transcribed.
Increased error rates for some Google calendar sync operations
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
monitoring
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.
