Looking for an update now? Check the current status, or follow Cronofy for future changes.
97.6%of 83 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
October 2026
100%
31
0
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)
Aug 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We're seeing improvement: syncs with Microsoft are succeeding in much greater numbers.
We are processing the backlog of changes to bring calendars fully back in sync.
monitoring
We are continuing to monitor for any further issues.
monitoring
While we wait for the Microsoft outage to be resolved, here is what you can expect from your Cronofy operations:
- We are retrying all creation and updates to events. As Microsoft restores service, these will begin to sync into calendars as usual.
- Availability Queries still work, and are based on our best knowledge of each calendar. Calendar data from Microsoft can not be guaranteed to be up to date at the moment. However, as no one can edit their calendars at the moment, this is a low risk.
- Push Notifications for calendar changes are being sent as normal. You will be seeing lower levels now because of the lack of changes being received from Microsoft. There will be higher levels later when sync operations resume.
- Once connection is restored, Cronofy will automatically reconcile changes to events to bring the calendar back up to date. This is the same operation as when a calendar has been disconnected for a period and then reconnected.
You do not need to take any action, and no data will be lost; all changes will eventually sync as soon as we are able.
We are continuing to monitor https://status.cloud.microsoft/ and our own telemetry, and will update again once we see normal operations resuming.
monitoring
We are still monitoring, waiting for Microsoft to restore service fully.
We are going to stop posting updates for now, until we see the incident resolved. Our service will continue to sync as much as possible, and retry any changes that failed.
Please watch https://status.cloud.microsoft/ for updates from Microsoft on the resolution of the incident.
monitoring
We have still seen no improvement yet.
Sync of Microsoft calendars remains degraded - about 40% of our communications to Microsoft are working, and any failed calls are being retried until they succeed.
Microsoft are reporting under issue reference EX1550543, which you can follow at https://status.cloud.microsoft
We will update this status when we see some improvement or in another 2 hours.
monitoring
We are continuing to monitor the situation but have seen no improvement yet.
Microsoft are reporting under issue reference EX1550543, which you can follow at https://status.cloud.microsoft
We will update this status when we see some improvement or in 2 hours.
monitoring
We are continuing to monitor the situation.
Sync to Microsoft 365 calendars is degraded, so there is some delay between events appearing in calendars. Other providers are not impacted.
We will update this status when we see some improvement, or in an hour.
monitoring
This looks to be as a result of a wider outage with Microsoft's services that has been given issue reference EX1550543.
We'll continue to monitor.
investigating
We are observing Microsoft 365 calendar APIs returning higher error rates and investigating the impact. This may affect how quickly changes to calendars are observed and our ability to push events.
Our improvements today have had positive results so far. We're continuing to monitor Google Meet success rates closely.
identified
A further improvement to Google Meet Meeting Agents released this morning and we are monitoring its impact on overall success rates in our environments
identified
We've implemented an improvement to our meeting join logic which has improved our success rate, but not entirely eliminated the issue. We're continuing to make further improvements and will post updates as they release.
investigating
We are investigating an increased failure rate in Meeting Agents joining Google Meet calls, resulting in us reporting an access_denied status for impacted cases.
Other meeting providers are unaffected.
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.
