All Systems Operational

Uptime over the past 90 days. View historical uptime.
Scheduler Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Background Processing Operational
90 days ago
100.0 % uptime
Today
Developer Dashboard Operational
90 days ago
100.0 % uptime
Today
Major Calendar Providers Operational
Apple Operational
Google Operational
Microsoft 365 Operational
Outlook.com Operational
Conferencing Services Operational
GoTo Operational
Zoom Operational
Meeting Agents Operational
90 days ago
99.94 % uptime
Today
Zoom Operational
90 days ago
100.0 % uptime
Today
Google Meet Operational
90 days ago
99.84 % uptime
Today
Microsoft Teams Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jun 14, 2026
Cache and database cluster instance type upgrades in all data centers
Completed - The scheduled maintenance has been completed successfully. We observed disruption at the following times (UTC):

Singapore: No disruption observed
Australia: 07:30:15 - 07:30:30
UK: No disruption observed
Canada: 08:12:15 - 08:13:30 UTC, 08:24:15 - 08:25:30, 09:30:30 - 09:30:45 and 09:33:30 - 09:33:45
Germany: 08:47:30 - 08:49:00
US: 09:16:30 - 09:16:45

If you have any questions, please email support@cronofy.com.
Jun 14, 09:54 UTC
Verifying - The update is complete in our US data center. We observed disruption from 09:16:30 to 09:16:45 UTC.

We also observed some additional disruption in our Canadian data center. This was from 09:30:30 to 09:30:45, and from 09:33:30 to 09:33:45. This extra disruption happened when old database reader nodes were removed from the cluster. This was the only data center where changes to the database cluster were made.
Jun 14, 09:41 UTC
Update - The update is complete in our Germany data center. We observed disruption from 08:47:30 to 08:49:00 UTC.

We are beginning the update in our US data center.
Jun 14, 09:00 UTC
Update - The update is complete in our Canada data center. We observed disruption from 08:12:15 to 08:13:30 UTC, and then again from 08:24:15 to 08:25:30.

We are beginning the update in our Germany data center.
Jun 14, 08:37 UTC
Update - The update is complete in our UK data center. There was no observed disruption.

We are beginning the update in our Canada data center.
Jun 14, 08:07 UTC
Update - The update is complete in our Australia data center. We observed disruption from 07:30:15 to 07:30:30 UTC.

We are beginning the update in our UK data center.
Jun 14, 07:43 UTC
Update - The update is complete in our Singapore data center. There was no observed disruption.

We are beginning the update in our Australia data center.
Jun 14, 07:19 UTC
In progress - The scheduled maintenance is in progress. We are beginning the update in our Singapore data center.
Jun 14, 07:00 UTC
Scheduled - We will be upgrading the instance types used within our cache and database clusters in all data centers.

These upgrades require a failover to the new instance types, therefore there will be up to five minutes of disruption when this happens. We will upgrade the instances one data center at a time and will begin the first upgrade shortly after 07:00 UTC. We expect the upgrades to be completed by 10:00 UTC on Sunday, 14th June 2026.

We will provide notifications as this maintenance progresses via our status page.

If you have any questions, please email support@cronofy.com.
Jun 8, 16:00 UTC
Jun 13, 2026

No incidents reported.

Jun 12, 2026

No incidents reported.

Jun 11, 2026

No incidents reported.

Jun 10, 2026

No incidents reported.

Jun 9, 2026

No incidents reported.

Jun 8, 2026

No incidents reported.

Jun 7, 2026

No incidents reported.

Jun 6, 2026

No incidents reported.

Jun 5, 2026

No incidents reported.

Jun 4, 2026
Google Meet Meeting Agents failing to join
Resolved - 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.
Jun 4, 13:05 UTC
Update - We are now rolling out a further fix which has tested well internally, and will continue to monitor its performance.
Jun 4, 11:00 UTC
Update - 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.
Jun 4, 09:39 UTC
Update - Google Meet Meeting Agents are making join attempts successfully since the fix release earlier. We will continue to monitor their performance.
Jun 3, 18:34 UTC
Update - We are continuing to monitor for any further issues.
Jun 3, 18:30 UTC
Monitoring - We are rolling out a fix which has tested positively internally, and will be monitoring success rates
Jun 3, 16:31 UTC
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.
Jun 3, 15:12 UTC
Jun 3, 2026
Jun 2, 2026
Increased error rates for some Google calendar sync operations
Resolved - 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.
Jun 2, 20:29 UTC
Update - 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.
Jun 2, 16:55 UTC
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.
Jun 2, 13:40 UTC
Jun 1, 2026

No incidents reported.

May 31, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage