Cronofy experienced a minor incident on June 5, 2023 affecting Background Processing and Microsoft 365 and 1 more component, lasting 2h 24m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 05, 2023, 02:31 PM UTC
We are currently investigating degraded performance with background processing in both our DE and US data centers.
- identified Jun 05, 2023, 02:53 PM UTC
We have identified an issue with calendar sync operations when connecting to the Microsoft Graph API. We are working to mitigate this impact on the rest of our background processing jobs.
- identified Jun 05, 2023, 03:48 PM UTC
Our telemetry is showing that calender sync operations to Outlook.com and Microsoft 365 are also affected. We have mitigated the performance impact this issue was having on calendar sync operations with other providers. We are tracking open Microsoft incidents, with IDs MO571683 and EX571516, and continuing to monitor our platform closely.
- monitoring Jun 05, 2023, 04:13 PM UTC
Calendar sync operations to Microsoft services appear to have returned to normal around 16:00 UTC. We are continuing to monitor.
- resolved Jun 05, 2023, 04:56 PM UTC
From 14:13 to 15:47 UTC calendar sync operations to Microsoft platforms were degraded. During this time around 69% of operations between Cronofy and Microsoft resulted in failure and led to a backlog when processing requests. We took steps to mitigate the effects of this on other platforms and began monitoring the issue which has now been resolved. We believe this is related to Microsoft alert: MO571683 (https://portal.office.com/adminportal/home?#/servicehealth/:/alerts/MO571683)