Google's API returned increased 503 errors, causing delayed calendar syncs for a small percentage of Cronofy users over 1.8 hours. Google identified and resolved an infrastructure issue on their end, with Cronofy confirming error rates returned to normal levels and marking the incident resolved.
Google has closed their incident and we've seen error rates remain low so are likewise marking this as resolved now.
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.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with