Event Triggers not sending in US data center
Affected: API
Cronofy Outage History
Cronofy is up right nowCronofy had 13 outages in the last 2 years totaling 73h 49m of downtime — averaging 0.5 incidents per month.
There were 13 Cronofy outages since October 20, 2025 totaling 73h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.
Increased API errors in our US data center
Affected: API
Timeline · 2 updates
- identified Jun 16, 2026, 09:25 AM UTC
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.
- resolved Jun 16, 2026, 09:56 AM UTC
The mitigation has been completed. Increased API errors were observed from 09:30:30 to 09:31:30 UTC.
Google Meet Meeting Agents failing to join
Affected: Google Meet
Timeline · 7 updates
- investigating Jun 03, 2026, 03:12 PM UTC
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.
- monitoring Jun 03, 2026, 04:31 PM UTC
We are rolling out a fix which has tested positively internally, and will be monitoring success rates
- monitoring Jun 03, 2026, 06:30 PM UTC
We are continuing to monitor for any further issues.
- monitoring Jun 03, 2026, 06:34 PM UTC
Google Meet Meeting Agents are making join attempts successfully since the fix release earlier. We will continue to monitor their performance.
- monitoring Jun 04, 2026, 09:39 AM UTC
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 Jun 04, 2026, 11:00 AM UTC
We are now rolling out a further fix which has tested well internally, and will continue to monitor its performance.
- resolved Jun 04, 2026, 01:05 PM UTC
Google Meet Meeting Agents are attempting meeting joins successfully again after our further fix earlier today. We shall continue to monitor but consider this incident to be closed.
Increased error rates for some Google calendar sync operations
Affected: Google
Timeline · 3 updates
- 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.
- 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.
- 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.
Events failing to sync to user calendars
Affected: Background Processing
Timeline · 5 updates
Issues scheduling with Google Chrome Extension in Gmail
Affected: Scheduler
Timeline · 5 updates
- investigating Feb 17, 2026, 11:22 AM UTC
We are aware of issues affecting our Google Chrome Extension preventing users from creating scheduling requests in Gmail. We are currently investigating and will provide an update as soon as possible.
- investigating Feb 17, 2026, 12:01 PM UTC
We are still working to identify the exact root cause of the issue. We will provide further updates as soon as possible.
- identified Feb 17, 2026, 12:39 PM UTC
A recent Google Chrome update has changed a mechanism that our Gmail extension relies on. We are developing a fix that is compatible with this new mechanism. We will provide an update in a few hours or when we have an updated version of the extension ready.
- identified Feb 17, 2026, 01:34 PM UTC
We have submitted an updated version of the Chrome Extension to Google which contains a fix for this issue. The updated version will be available as soon as it has been checked and published by Google. We will provide an update once we confirmation of this from Google.
- resolved Feb 17, 2026, 02:10 PM UTC
We have released version 0.22.25 of the Cronofy Chrome extension, fixing the issue. If you have any problems, please first check that both Google Chrome and the Cronofy Chrome extension are up to date. If you have any additional issues then please contact [email protected].
Elevated API 500 errors in our AU data center
Timeline · 1 update
- resolved Feb 13, 2026, 01:44 PM UTC
Between 12:52 and 12:55 we saw that calls to our API encountered a higher level of 500 Server Error responses than usual We have investigated this and it appears to relate to a period where we saw a large spike in traffic, a rapid drop and another spike in quick succession resulting in some temporary 500 errors. This is now resolved but we will continue monitoring for any further issues.
MS Teams Conferencing Failures
Affected: Microsoft 365
Timeline · 6 updates
- investigating Feb 11, 2026, 11:29 AM UTC
We are investigating an elevated level of failures for provisioning MS Teams Conferencing.
- investigating Feb 11, 2026, 12:07 PM UTC
We are continuing to investigate - the issue is not impacting all customers but we are not yet seeing a pattern to the domains or events impacted.
- investigating Feb 11, 2026, 12:54 PM UTC
We are still investigating; we are capturing additional logs to help us narrow down the failing population. Some conferences are being provisioned after automatically retrying, but still not as many as we'd expect.
- investigating Feb 11, 2026, 01:31 PM UTC
We've found some evidence that other users of the Microsoft Graph API are experiencing the same issue; we're looking for anything that may let us mitigate the impact and we're reaching out to Microsoft for support.
- investigating Feb 11, 2026, 02:59 PM UTC
We believe the root cause is a lack of generated URLs for a meeting when we call Microsoft Graph APIs. We are waiting for a response from Microsoft on the issue. Unfortunately the timing of this is out of our hands. We are also working on alternative ways to provision Teams meetings, but this will not provide a short term fix. We are continuing to work on finding a way to resolve, mitigate or provide an more reliable path to Teams provisioning. We will update this incident over the coming days as we make meaningful progress.
- resolved Feb 12, 2026, 10:59 AM UTC
We have seen that our error rate provisioning MS Teams Conferencing has returned to normal, low levels since 16:10 UTC yesterday. Normal levels of service have resumed, and we're working to improve our monitoring so that similar issues are detected sooner in the future.
Degraded sync performance for Microsoft 365
Affected: Microsoft 365
Timeline · 4 updates
- 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.
- 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
- monitoring Jan 23, 2026, 12:01 AM UTC
We are continuing to monitor the situation, but have not seen any improvement so far
- 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.
Increased API error rates in our US data center
Timeline · 4 updates
Google calendar sync degraded
Affected: Google
Timeline · 3 updates
- investigating Nov 12, 2025, 06:31 PM UTC
We are currently investigating the cause of Google calendar sync degradation
- monitoring Nov 12, 2025, 06:40 PM UTC
Google's API error rate has dropped again and has been at normal levels for the past 10 minutes. We'll continue to monitor and confirm this holds out.
- resolved Nov 12, 2025, 06:56 PM UTC
Between 18:15 UTC and 18:28 UTC, we observed elevated error rates, and Google Calendar users may have experienced delays with calendar reads and writes. Since 18:28 UTC, all Google Calendar operations have been functioning as normal.
CA data center - Interruption of service
Affected: SchedulerAPI
Timeline · 3 updates
Major outage in US data center
Affected: SchedulerAPIBackground ProcessingDeveloper Dashboard