Cronofy Outage History

Cronofy is up right now

There were 5 Cronofy outages since February 11, 2026 totaling 29h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cronofy.com

Minor March 13, 2026

Increased error rates for some Google calendar sync operations

Detected by Pingoru
Mar 13, 2026, 01:29 PM UTC
Resolved
Mar 13, 2026, 03:18 PM UTC
Duration
1h 48m
Affected: Google
Timeline · 4 updates
  1. investigating Mar 13, 2026, 01:29 PM UTC

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

  2. investigating Mar 13, 2026, 01:54 PM UTC

    We are seeing signs of improvement from Google's side -- error rates have improved a great deal but are not yet quite back to normal levels. We continue to monitor the situation.

  3. monitoring Mar 13, 2026, 02:55 PM UTC

    Google have identified an issue within their infrastructure which they're tracking at https://www.google.com/appsstatus/dashboard/incidents/KamjizntSiNtRETcBL2Q From our side, we're now seeing very low enough error rates that we don't think that users will experience any noticeable negative impact. We'll keep watching Google's incident until it's fully resolved.

  4. resolved Mar 13, 2026, 03:18 PM UTC

    Google has closed their incident and we've seen error rates remain low so are likewise marking this as resolved now.

Read the full incident report →

Major February 27, 2026

Events failing to sync to user calendars

Detected by Pingoru
Feb 27, 2026, 04:06 PM UTC
Resolved
Feb 27, 2026, 05:35 PM UTC
Duration
1h 28m
Affected: Background Processing
Timeline · 5 updates
  1. identified Feb 27, 2026, 04:06 PM UTC

    Since approximately 12:30 UTC a subset of calendar events failed to be synced to users' calendars. We've identified the source of the issue and released a fix, we are now assessing the impact and actions necessary to resolve the issue for previously impacted calendar events.

  2. identified Feb 27, 2026, 04:28 PM UTC

    We have identified that affected events were those being written to Microsoft calendars and using the `integrated` conferencing option. The system is already retrying these failures and successfully writing them. We are looking to accelerate this process.

  3. identified Feb 27, 2026, 05:00 PM UTC

    At approximately 12:30 UTC a change was released that prevented events being created in Microsoft calendars if integrated conferencing was being used. A fix was released and the last error observed at approximately 16:05 UTC. Since that time over 90% of the impacted events have been successfully synced due to standard retry mechanisms with the platform. We are working to enqueue additional attempts for all affected calendars to speed up this process and to be certain nothing has been missed.

  4. resolved Feb 27, 2026, 05:35 PM UTC

    At approximately 12:30 UTC a change was released that prevented events being created in Microsoft calendars if integrated conferencing was being used. A fix was released and the last error observed at approximately 16:05 UTC. Over 90% of the impacted events were successfully synced due to standard retry mechanisms with the platform by 17:00 UTC, we also ran a sweep to proactively retry all remaining events which completed by 17:30 UTC. This incident is now resolved and operations are back to normal. We will be conducting a postmortem and will publish the findings of that next week.

  5. postmortem Mar 03, 2026, 03:12 PM UTC

    On Friday February 27th 2026 at 12:28 UTC, a change was released to our production environment that caused a bug preventing events using Microsoft Integrated conferencing from being synced to calendars. At 16:05 UTC, a change was released to fix the issue and full functionality was restored. By 17:35 UTC, all previously impacted events had been successfully retried and synced and the incident was closed. In total, we identified 2,254 events that had been affected by this bug, all of which have now been successfully synced. We always ask the questions: * Could the issue have been identified sooner? * Could the issue have been resolved sooner? * Could the issue have been prevented? In this instance, the issue could and should have been identified by us earlier. The change that introduced this bug was released at 12:28 UTC, but we only became aware of the issue when a customer reported issues to us at 15:27 UTC. We never want to rely on customers having to tell us about issues in our platform before we are aware, so this is an instance where gaps in our system monitoring meant the issue went undetected for too long. We deployed a fix for this issue at 16:05 UTC, which was 37 minutes after the bug report email was sent, and 13 minutes after we identified the extent of the issue and opened an incident at 15:52 UTC. Therefore, we don’t believe the bug could’ve been resolved any sooner, as we acted quickly to release a fix once we were fully aware of the problem. Along with a gap in our alerting, the bug should have been prevented through automated testing, which would’ve flagged the issue before the initial change was deployed at 12:28 UTC. In this instance, our testing failed to check the logic down the path that Microsoft Teams integrated conferencing followed, because a check had been mocked instead of being integration tested, leading to a blind spot. We have addressed this and are reviewing where we have used test mocks which could hide integration issues. Actions: * Further guidelines around coding principles to be provided to our Engineering team regarding our approach to automated testing * Improve our system monitoring to provide specific alerting around this particular area

Read the full incident report →

Minor February 17, 2026

Issues scheduling with Google Chrome Extension in Gmail

Detected by Pingoru
Feb 17, 2026, 11:22 AM UTC
Resolved
Feb 17, 2026, 02:10 PM UTC
Duration
2h 47m
Affected: Scheduler
Timeline · 5 updates
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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].

Read the full incident report →

Minor February 13, 2026

Elevated API 500 errors in our AU data center

Detected by Pingoru
Feb 13, 2026, 01:44 PM UTC
Resolved
Feb 13, 2026, 01:44 PM UTC
Duration
—
Timeline · 1 update
  1. 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.

Read the full incident report →

Minor February 11, 2026

MS Teams Conferencing Failures

Detected by Pingoru
Feb 11, 2026, 11:29 AM UTC
Resolved
Feb 12, 2026, 10:59 AM UTC
Duration
23h 29m
Affected: Microsoft 365
Timeline · 6 updates
  1. investigating Feb 11, 2026, 11:29 AM UTC

    We are investigating an elevated level of failures for provisioning MS Teams Conferencing.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Read the full incident report →

Looking to track Cronofy downtime and outages?

Pingoru polls Cronofy's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Cronofy reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Cronofy alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Cronofy for free

5 free monitors · No credit card required