Snapshot 296559
Raw (normalized text)
Scripts and page chrome removed; this is what change detection compares.
{
"components": [
{
"created_at": "2021-03-01T16:20:14.489Z",
"description": null,
"group_id": null,
"id": "7hc2dnlph2ns",
"name": "Scheduler",
"page_id": "6m5v2lqb4txt",
"position": 1,
"showcase": true,
"start_date": "2021-03-01T00:00:00.000Z",
"status": "operational",
"updated_at": "2026-06-14T09:54:31.655Z"
},
{
"created_at": "2015-08-05T15:44:28.870Z",
"description": null,
"group_id": null,
"id": "7wxdr24f6zns",
"name": "API",
"page_id": "6m5v2lqb4txt",
"position": 2,
"showcase": true,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-07T10:20:54.634Z"
},
{
"components": [
"z1l9hwl3qzwh",
"yw553xq25fjq",
"c22spg7hz9tt"
],
"created_at": "2026-06-03T14:57:24.511Z",
"description": null,
"group_id": null,
"id": "lwk6jxjgl456",
"name": "Meeting Agents",
"page_id": "6m5v2lqb4txt",
"position": 3,
"showcase": false,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-08T19:57:24.270Z"
},
{
"created_at": "2015-08-05T15:43:44.897Z",
"description": null,
"group_id": null,
"id": "v5h8cvtfpsw6",
"name": "Background Processing",
"page_id": "6m5v2lqb4txt",
"position": 4,
"showcase": true,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-08T19:57:24.277Z"
},
{
"created_at": "2015-08-05T15:43:44.913Z",
"description": null,
"group_id": null,
"id": "gk9tm2621bkp",
"name": "Developer Dashboard",
"page_id": "6m5v2lqb4txt",
"position": 5,
"showcase": true,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-08T19:57:24.283Z"
},
{
"components": [
"6p0wfjlkw690",
"lbym3z60fm1f",
"7mrbsj5bp9xl",
"c3j5m257pwxn"
],
"created_at": "2015-08-06T09:24:46.655Z",
"description": null,
"group_id": null,
"id": "g2vfx6bv0m2n",
"name": "Major Calendar Providers",
"page_id": "6m5v2lqb4txt",
"position": 6,
"showcase": false,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-08T19:57:09.764Z"
},
{
"components": [
"97gkb147vdv9",
"44wsw7593z31"
],
"created_at": "2022-06-21T14:32:42.344Z",
"description": null,
"group_id": null,
"id": "w4xzbd6nxv5k",
"name": "Conferencing Services",
"page_id": "6m5v2lqb4txt",
"position": 7,
"showcase": false,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-08T19:57:09.778Z"
}
],
"incidents": [
{
"components": [
{
"created_at": "2015-08-06T09:23:29.841Z",
"description": null,
"group_id": "g2vfx6bv0m2n",
"id": "6p0wfjlkw690",
"name": "Apple",
"page_id": "6m5v2lqb4txt",
"position": 1,
"showcase": false,
"start_date": null,
"status": "operational",
"updated_at": "2026-11-17T21:05:48.032Z"
}
],
"created_at": "2026-11-17T17:33:52.491Z",
"id": "fvy69x5b28rv",
"impact": "minor",
"impact_override": null,
"incident_updates": [
{
"affected_components": [
{
"code": "6p0wfjlkw690",
"name": "Major Calendar Providers - Apple",
"new_status": "operational",
"old_status": "degraded_performance"
}
],
"body": "Apple sync has recovered back to normal levels and changes to events have been reconciled.\n\nAt 16:50 UTC, we began to see a high rate of failures when communicating with Apple. This recovered about 20:15 UTC and has remained stable since.",
"created_at": "2026-11-17T21:05:48.079Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-17T21:05:48.079Z",
"id": "fk948wp60wym",
"incident_id": "fvy69x5b28rv",
"status": "resolved",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-17T21:05:48.079Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "6p0wfjlkw690",
"name": "Major Calendar Providers - Apple",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "We are seeing some improvement to the number of syncs completing normally, but we are not quite back to normal levels yet. We are continuing to monitor the situation.",
"created_at": "2026-11-17T19:33:40.099Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-17T19:33:40.099Z",
"id": "wh4dw3rkbpwy",
"incident_id": "fvy69x5b28rv",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-17T19:33:40.099Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "6p0wfjlkw690",
"name": "Major Calendar Providers - Apple",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "We are continuing to see large numbers of failing syncs with Apple iCloud calendars. Apple are reporting iCloud issues as of 16:45 UTC which are the root cause.\n\nYou will see a delay in changes to Apple calendars until the incident is resolved. Cronofy will reconcile changes as soon as possible so no action is needed on your part.\n\nYou can follow Apple's status on their page: https://www.apple.com/support/systemstatus/",
"created_at": "2026-11-17T18:00:21.698Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-17T18:00:21.698Z",
"id": "l2nb9bgq3t73",
"incident_id": "fvy69x5b28rv",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-17T18:00:21.698Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "6p0wfjlkw690",
"name": "Major Calendar Providers - Apple",
"new_status": "degraded_performance",
"old_status": "operational"
}
],
"body": "Since 16:50 UTC we have observed an increased error rate for Apple calendar sync operations. We are still seeing more successes than failures but consider there to be enough failures to mark Apple as degraded.",
"created_at": "2026-11-17T17:33:52.688Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-17T17:33:52.688Z",
"id": "2sswr29n3w78",
"incident_id": "fvy69x5b28rv",
"status": "investigating",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-17T17:33:52.688Z",
"wants_twitter_update": false
}
],
"metadata": {},
"monitoring_at": "2026-11-17T18:00:21.698Z",
"name": "Degraded Apple Calendar Sync",
"page_id": "6m5v2lqb4txt",
"postmortem_body": null,
"postmortem_body_last_updated_at": null,
"postmortem_ignored": false,
"postmortem_notified_subscribers": false,
"postmortem_notified_twitter": false,
"postmortem_published_at": null,
"reminder_intervals": "[]",
"resolved_at": "2026-11-17T21:05:48.079Z",
"scheduled_auto_completed": false,
"scheduled_auto_in_progress": false,
"scheduled_for": null,
"scheduled_remind_prior": false,
"scheduled_reminded_at": null,
"scheduled_until": null,
"shortlink": "https://stspg.io/92myplw718cq",
"started_at": "2026-11-17T17:33:52.480Z",
"status": "resolved",
"updated_at": "2026-11-17T21:05:48.105Z"
},
{
"components": [
{
"created_at": "2026-06-03T14:58:03.425Z",
"description": "Meeting Agent infrastructure for joining Google Meet calls",
"group_id": "lwk6jxjgl456",
"id": "yw553xq25fjq",
"name": "Google Meet",
"page_id": "6m5v2lqb4txt",
"position": 2,
"showcase": true,
"start_date": "2026-01-01T00:00:00.000Z",
"status": "operational",
"updated_at": "2026-11-16T12:41:23.087Z"
}
],
"created_at": "2026-11-12T14:57:54.986Z",
"id": "hlb4z1x5tg9j",
"impact": "minor",
"impact_override": null,
"incident_updates": [
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "operational",
"old_status": "degraded_performance"
}
],
"body": "Google Meet join success is back to normal since our most recent updates and we consider this incident resolved.\n\nOn 12th November we saw a large uptick in Google Meet failures at the meeting join stage which we reported as access_denied.\n\nWe believe Google rolled out a change in behavior over time, as looking back over our telemetry we see that this would have been visible earlier throughout November at a lower level. As part of the fixes deployed, we have increased our monitoring coverage and sensitivity in this area to better handle future similar cases should they occur.",
"created_at": "2026-11-13T15:56:54.446Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-13T15:56:54.446Z",
"id": "tnp666x6nw24",
"incident_id": "hlb4z1x5tg9j",
"status": "resolved",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-13T15:56:54.446Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "Our improvements today have had positive results so far. We're continuing to monitor Google Meet success rates closely.",
"created_at": "2026-11-13T12:44:45.692Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-13T12:44:45.692Z",
"id": "cvqwp8vykrw0",
"incident_id": "hlb4z1x5tg9j",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-13T12:44:45.692Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "A further improvement to Google Meet Meeting Agents released this morning and we are monitoring its impact on overall success rates in our environments",
"created_at": "2026-11-13T09:47:00.347Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-13T09:47:00.347Z",
"id": "xbv4yr01hxbx",
"incident_id": "hlb4z1x5tg9j",
"status": "identified",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-13T09:47:00.347Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "We've implemented an improvement to our meeting join logic which has improved our success rate, but not entirely eliminated the issue. We're continuing to make further improvements and will post updates as they release.",
"created_at": "2026-11-12T18:00:13.581Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-12T18:00:13.581Z",
"id": "99hk0mz909n7",
"incident_id": "hlb4z1x5tg9j",
"status": "identified",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-12T18:00:13.581Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "degraded_performance",
"old_status": "operational"
}
],
"body": "We are investigating an increased failure rate in Meeting Agents joining Google Meet calls, resulting in us reporting an access_denied status for impacted cases.\n\nOther meeting providers are unaffected.",
"created_at": "2026-11-12T14:57:55.099Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-12T14:57:55.099Z",
"id": "n6n93pf1h16l",
"incident_id": "hlb4z1x5tg9j",
"status": "investigating",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-12T14:57:55.099Z",
"wants_twitter_update": false
}
],
"metadata": {},
"monitoring_at": "2026-11-13T12:44:45.692Z",
"name": "Increase in failures to join Google Meet calls",
"page_id": "6m5v2lqb4txt",
"postmortem_body": null,
"postmortem_body_last_updated_at": null,
"postmortem_ignored": false,
"postmortem_notified_subscribers": false,
"postmortem_notified_twitter": false,
"postmortem_published_at": null,
"reminder_intervals": null,
"resolved_at": "2026-11-13T15:56:54.446Z",
"scheduled_auto_completed": false,
"scheduled_auto_in_progress": false,
"scheduled_for": null,
"scheduled_remind_prior": false,
"scheduled_reminded_at": null,
"scheduled_until": null,
"shortlink": "https://stspg.io/3kyh11k4dr61",
"started_at": "2026-11-12T14:57:54.975Z",
"status": "resolved",
"updated_at": "2026-11-13T15:56:54.476Z"
},
{
"components": [
{
"created_at": "2015-08-06T09:23:56.457Z",
"description": null,
"group_id": "g2vfx6bv0m2n",
"id": "7mrbsj5bp9xl",
"name": "Microsoft 365",
"page_id": "6m5v2lqb4txt",
"position": 3,
"showcase": false,
"start_date": null,
"status": "operational",
"updated_at": "2026-11-13T15:32:49.653Z"
},
{
"created_at": "2015-08-06T09:23:43.622Z",
"description": null,
"group_id": "g2vfx6bv0m2n",
"id": "c3j5m257pwxn",
"name": "Outlook.com",
"page_id": "6m5v2lqb4txt",
"position": 4,
"showcase": false,
"start_date": null,
"status": "operational",
"updated_at": "2026-11-13T15:32:49.678Z"
}
],
"created_at": "2026-11-12T18:07:40.493Z",
"id": "kc0969gx9bxd",
"impact": "major",
"impact_override": null,
"incident_updates": [
{
"affected_components": [
{
"code": "7mrbsj5bp9xl",
"name": "Major Calendar Providers - Microsoft 365",
"new_status": "operational",
"old_status": "partial_outage"
},
{
"code": "c3j5m257pwxn",
"name": "Major Calendar Providers - Outlook.com",
"new_status": "operational",
"old_status": "partial_outage"
}
],
"body": "Microsoft 365 was degraded from approximately 17:30 UTC, Thursday 12th November until 13:30 UTC, Friday 13th November. A large number of sync operations between Cronofy and Microsoft were failing, leading to delays in changes being reflected.\n\nCommunication with Microsoft 365 services has recovered, and all real-time Cronofy operations are working normally.\n\nWe have processed every change made to an event via Cronofy during the incident. Event creates, updates and deletes now appear in Microsoft 365 calendars as normal.\n\nWe are syncing changes made in the calendar into Cronofy again too. \n\nBecause the outage was long, we are also running extra syncs to confirm that every calendar is fully up to date. This work runs as fast as Microsoft's rate limits allow. \n\nWhile we are doing extra work to validate the integrity of calendar data, until it is finished, a small number of results could be based on stale calendar data. As most people couldn’t interact with their calendars during the outage, we believe this is unlikely but want to be certain.\n\nNo data has been lost, and no action is needed from you.\n\nAt this point, we believe normal function is restored, and we are marking this incident as resolved; if you have any queries, please contact us at support@cronofy.com",
"created_at": "2026-11-13T15:32:49.717Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-13T15:32:49.717Z",
"id": "n5hpdddh5yyj",
"incident_id": "kc0969gx9bxd",
"status": "resolved",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-13T15:32:49.717Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7mrbsj5bp9xl",
"name": "Major Calendar Providers - Microsoft 365",
"new_status": "partial_outage",
"old_status": "partial_outage"
},
{
"code": "c3j5m257pwxn",
"name": "Major Calendar Providers - Outlook.com",
"new_status": "partial_outage",
"old_status": "partial_outage"
}
],
"body": "We're seeing improvement: syncs with Microsoft are succeeding in much greater numbers.\n\nWe are processing the backlog of changes to bring calendars fully back in sync.",
"created_at": "2026-11-13T14:10:22.138Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-13T14:10:22.138Z",
"id": "lzygvf1wh7zf",
"incident_id": "kc0969gx9bxd",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-13T14:10:22.138Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7mrbsj5bp9xl",
"name": "Major Calendar Providers - Microsoft 365",
"new_status": "partial_outage",
"old_status": "degraded_performance"
},
{
"code": "c3j5m257pwxn",
"name": "Major Calendar Providers - Outlook.com",
"new_status": "partial_outage",
"old_status": "operational"
}
],
"body": "We are continuing to monitor for any further issues.",
"created_at": "2026-11-13T12:05:13.294Z",
"custom_tweet": null,
"deliver_notifications": false,
"display_at": "2026-11-13T12:05:13.294Z",
"id": "sb7ktd7h0vjj",
"incident_id": "kc0969gx9bxd",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-13T12:05:13.294Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7mrbsj5bp9xl",
"name": "Major Calendar Providers - Microsoft 365",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "While we wait for the Microsoft outage to be resolved, here is what you can expect from your Cronofy operations:\n\n- We are retrying all creation and updates to events. As Microsoft restores service, these will begin to sync into calendars as usual.\n- Availability Queries still work, and are based on our best knowledge of each calendar. Calendar data from Microsoft can not be guaranteed to be up to date at the moment. However, as no one can edit their calendars at the moment, this is a low risk.\n- Push Notifications for calendar changes are being sent as normal. You will be seeing lower levels now because of the lack of changes being received from Microsoft. There will be higher levels later when sync operations resume.\n- Once connection is restored, Cronofy will automatically reconcile changes to events to bring the calendar back up to date. This is the same operation as when a calendar has been disconnected for a period and then reconnected.\n\nYou do not need to take any action, and no data will be lost; all changes will eventually sync as soon as we are able.\n\nWe are continuing to monitor https://status.cloud.microsoft/ and our own telemetry, and will update again once we see normal operations resuming.",
"created_at": "2026-11-13T11:56:44.441Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-13T11:56:44.441Z",
"id": "pk4mx9yd0zg0",
"incident_id": "kc0969gx9bxd",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-13T11:56:44.441Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7mrbsj5bp9xl",
"name": "Major Calendar Providers - Microsoft 365",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "We are still monitoring, waiting for Microsoft to restore service fully.\n\nWe are going to stop posting updates for now, until we see the incident resolved. Our service will continue to sync as much as possible, and retry any changes that failed.\n\nPlease watch https://status.cloud.microsoft/ for updates from Microsoft on the resolution of the incident.",
"created_at": "2026-11-13T00:16:26.302Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-13T00:16:26.302Z",
"id": "w1jmv8swh35x",
"incident_id": "kc0969gx9bxd",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-13T00:16:26.302Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7mrbsj5bp9xl",
"name": "Major Calendar Providers - Microsoft 365",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "We have still seen no improvement yet.\n\nSync of Microsoft calendars remains degraded - about 40% of our communications to Microsoft are working, and any failed calls are being retried until they succeed.\n\nMicrosoft are reporting under issue reference EX1550543, which you can follow at https://status.cloud.microsoft\n\nWe will update this status when we see some improvement or in another 2 hours.",
"created_at": "2026-11-12T22:03:40.327Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-12T22:03:40.327Z",
"id": "g7qg1z25rdlq",
"incident_id": "kc0969gx9bxd",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-12T22:03:40.327Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7mrbsj5bp9xl",
"name": "Major Calendar Providers - Microsoft 365",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "We are continuing to monitor the situation but have seen no improvement yet.\n\nMicrosoft are reporting under issue reference EX1550543, which you can follow at https://status.cloud.microsoft\n\nWe will update this status when we see some improvement or in 2 hours.",
"created_at": "2026-11-12T19:56:35.648Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-12T19:56:35.648Z",
"id": "9vm2slm3qk3w",
"incident_id": "kc0969gx9bxd",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-12T19:56:35.648Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7mrbsj5bp9xl",
"name": "Major Calendar Providers - Microsoft 365",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "We are continuing to monitor the situation. \n\nSync to Microsoft 365 calendars is degraded, so there is some delay between events appearing in calendars. Other providers are not impacted.\n\nWe will update this status when we see some improvement, or in an hour.",
"created_at": "2026-11-12T18:51:59.140Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-12T18:51:59.140Z",
"id": "htp9h7gqtmz0",
"incident_id": "kc0969gx9bxd",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-12T18:51:59.140Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7mrbsj5bp9xl",
"name": "Major Calendar Providers - Microsoft 365",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "This looks to be as a result of a wider outage with Microsoft's services that has been given issue reference EX1550543.\nWe'll continue to monitor.",
"created_at": "2026-11-12T18:27:58.651Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-12T18:27:58.651Z",
"id": "s84wsg3gb8t6",
"incident_id": "kc0969gx9bxd",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-12T18:27:58.651Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7mrbsj5bp9xl",
"name": "Major Calendar Providers - Microsoft 365",
"new_status": "degraded_performance",
"old_status": "operational"
}
],
"body": "We are observing Microsoft 365 calendar APIs returning higher error rates and investigating the impact. This may affect how quickly changes to calendars are observed and our ability to push events.",
"created_at": "2026-11-12T18:07:40.607Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-11-12T18:07:40.607Z",
"id": "q6456sxncxjc",
"incident_id": "kc0969gx9bxd",
"status": "investigating",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-11-12T18:07:40.607Z",
"wants_twitter_update": false
}
],
"metadata": {},
"monitoring_at": "2026-11-12T18:27:58.651Z",
"name": "Microsoft 365 elevated error rates",
"page_id": "6m5v2lqb4txt",
"postmortem_body": null,
"postmortem_body_last_updated_at": null,
"postmortem_ignored": false,
"postmortem_notified_subscribers": false,
"postmortem_notified_twitter": false,
"postmortem_published_at": null,
"reminder_intervals": null,
"resolved_at": "2026-11-13T15:32:49.717Z",
"scheduled_auto_completed": false,
"scheduled_auto_in_progress": false,
"scheduled_for": null,
"scheduled_remind_prior": false,
"scheduled_reminded_at": null,
"scheduled_until": null,
"shortlink": "https://stspg.io/fmyhml785wjn",
"started_at": "2026-11-12T18:07:40.481Z",
"status": "resolved",
"updated_at": "2026-11-13T15:32:49.738Z"
},
{
"components": [
{
"created_at": "2021-03-01T16:20:14.489Z",
"description": null,
"group_id": null,
"id": "7hc2dnlph2ns",
"name": "Scheduler",
"page_id": "6m5v2lqb4txt",
"position": 1,
"showcase": true,
"start_date": "2021-03-01T00:00:00.000Z",
"status": "operational",
"updated_at": "2026-06-14T09:54:31.655Z"
},
{
"created_at": "2015-08-05T15:44:28.870Z",
"description": null,
"group_id": null,
"id": "7wxdr24f6zns",
"name": "API",
"page_id": "6m5v2lqb4txt",
"position": 2,
"showcase": true,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-07T10:20:54.634Z"
}
],
"created_at": "2026-10-22T12:01:35.997Z",
"id": "20vznwyhkz7f",
"impact": "none",
"impact_override": null,
"incident_updates": [
{
"affected_components": [
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "operational",
"old_status": "operational"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "operational",
"old_status": "operational"
}
],
"body": "Cronofy are aware of two recently published PHP vulnerabilities, CVE-2026-109618 \u0026 CVE-2026-109619. \n\nWe can confirm that we do not make use of PHP and are therefore unaffected by these vulnerabilities.\n\nRegarding usage of our PHP SDK, we strongly recommend that you upgrade to a version of PHP that includes patches for the two identified vulnerabilities. \n\nFor further reading please refer to PHP’s documentation: https://www.php.net/archive/2026.php#2026-10-21-5\n\nPlease contact support@cronofy.com with any questions.",
"created_at": "2026-10-22T12:01:36.057Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-10-22T12:01:36.057Z",
"id": "hlkjfz8f7dbx",
"incident_id": "20vznwyhkz7f",
"status": "resolved",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-10-22T12:01:36.057Z",
"wants_twitter_update": false
}
],
"metadata": {},
"monitoring_at": null,
"name": "PHP Remote Code Execution Vulnerabilities",
"page_id": "6m5v2lqb4txt",
"postmortem_body": null,
"postmortem_body_last_updated_at": null,
"postmortem_ignored": false,
"postmortem_notified_subscribers": false,
"postmortem_notified_twitter": false,
"postmortem_published_at": null,
"reminder_intervals": "[]",
"resolved_at": "2026-10-22T12:01:36.057Z",
"scheduled_auto_completed": false,
"scheduled_auto_in_progress": false,
"scheduled_for": null,
"scheduled_remind_prior": false,
"scheduled_reminded_at": null,
"scheduled_until": null,
"shortlink": "https://stspg.io/6b7przqrvnj7",
"started_at": "2026-10-22T12:01:35.992Z",
"status": "resolved",
"updated_at": "2026-10-22T12:01:36.067Z"
},
{
"components": [
{
"created_at": "2015-08-05T15:44:28.870Z",
"description": null,
"group_id": null,
"id": "7wxdr24f6zns",
"name": "API",
"page_id": "6m5v2lqb4txt",
"position": 2,
"showcase": true,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-07T10:20:54.634Z"
}
],
"created_at": "2026-07-07T10:12:51.633Z",
"id": "mrnbftn2pyzk",
"impact": "major",
"impact_override": "major",
"incident_updates": [
{
"affected_components": [
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "operational",
"old_status": "operational"
}
],
"body": "All pending notifications have now been flushed.\n\nNotifications scheduled since approximately 02:00 UTC on July 1st were failing to be sent. This affected customers in the US data center making use of the following API features:\n- Event Triggers; approximately 9000 notifications for calendar events starting/ending will have been delivered late\n- Scheduler Workflows; a small number of Scheduling Request lifecycle notifications will have been delivered late\n- Meeting Agents; a small number of scheduled Meeting Agents will not have arrived to their scheduled meetings\n\nA postmortem of the incident will take place and be attached to this incident in the next 48 hours.",
"created_at": "2026-07-07T11:12:21.242Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-07-07T11:12:21.242Z",
"id": "2vjn7svvcv6g",
"incident_id": "mrnbftn2pyzk",
"status": "resolved",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-07-07T11:12:21.242Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "operational",
"old_status": "degraded_performance"
}
],
"body": "A failing component in our US data center led to scheduled notifications for Event Triggers backing up and not sending. We've resolved the immediate cause, which will lead to notifications being delivered behind schedule.\n\nWe are monitoring this and investigating any wider impact from the issue.",
"created_at": "2026-07-07T10:20:54.664Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-07-07T10:20:54.664Z",
"id": "18g4z4k1mzmx",
"incident_id": "mrnbftn2pyzk",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-07-07T10:20:54.664Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "degraded_performance",
"old_status": "operational"
}
],
"body": "We are investigating an issue where Event Trigger notifications are failing to send in our US data center",
"created_at": "2026-07-07T10:12:51.721Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-07-07T10:12:51.721Z",
"id": "wg4x844kzf6b",
"incident_id": "mrnbftn2pyzk",
"status": "investigating",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-07-07T10:12:51.721Z",
"wants_twitter_update": false
}
],
"metadata": {},
"monitoring_at": "2026-07-07T10:20:54.664Z",
"name": "Event Triggers not sending in US data center",
"page_id": "6m5v2lqb4txt",
"postmortem_body": "Between approximately 02:25 UTC on July 1st and 10:11 UTC on July 7th 2026, scheduled notifications in our US data center failed to send. The affected notifications were queued but never picked up, and were flushed once the underlying cause was cleared.\n\nThe impact was limited to customers in the US data center using notification-driven API features. Approximately 9,000 Event Trigger notifications for calendar events starting and ending were delivered late. A small number of Scheduler Workflows lifecycle notifications were also delivered late, and a small number of scheduled Meeting Agents did not arrive to their meetings.\n\nThe root cause was a regression introduced on April 22nd, in an internal service responsible for sending scheduled notifications. The service uses leader election so that a single process handles distributing the imminent notifications at any one time, coordinated through a lock. The regression made that configuration fragile. If a leader did not release the lock cleanly, no other process would override it. When the leader stopped in the early hours of July 1st, it left the lock held, and with no process able to take over, notifications quietly backed up from that point.\n\nNothing alerted us to this. The failure mode was an absence of activity rather than an error, and we had no alerting on notification throughput that would have caught the drop-off.\n\nDuring the incident, we manually cleared the stuck lock, which allowed the service to resume and flush the backlog within four minutes.\n\n## Timeline\n\nAll times are in UTC.\n\n* **April 22nd, 10:27** A change is merged that makes the leader election's lock-holding fragile. The fault is latent and has no immediate effect.\n* **July 1st, 02:25** The leader process in the US stops in a way that invokes the regression, leaving the lock held. No notifications are picked up from this point.\n* **July 2nd, 06:42** A support ticket reports an issue with Event Triggers.\n* **July 6th, 14:53** A second support ticket reports an issue with Event Triggers.\n* **July 7th, 09:38** The pattern across the two tickets is identified internally and raised.\n* **July 7th, 09:50** Telemetry is reviewed, showing a clear drop-off in notification sends.\n* **July 7th, 09:57** An internal incident channel is opened.\n* **July 7th, 10:05** The held lock is raised as the probable cause.\n* **July 7th, 10:07** The lock is manually cleared.\n* **July 7th, 10:07-10:11** The backlog of late notifications is flushed by the now-working service.\n* **July 7th, 10:12** The public incident is opened.\n* **July 7th, 10:40** Impact is reviewed and confirmed, including the other affected paths \\(Scheduler Workflows, Meeting Agents\\).\n* **July 7th, 11:12** The public incident is resolved.\n\n## Retrospective\n\nWe always ask the same three questions.\n\n### Could the issue have been resolved sooner?\n\nOnce we were looking at the right thing, resolution was fast. The probable cause was raised within eight minutes of opening the channel, and the backlog was flushed four minutes after that. We are satisfied with how the resolution itself went.\n\n### Could the issue have been identified sooner?\n\nThis is where we fell short, and badly. The failure was live for almost six days. Two things let it run that long. First, we had no alerting on notification throughput, so a complete stop in sending produced no signal. It is harder to alert on things _not_ happening, but that is exactly the case this warranted. Second, the first support ticket arrived on July 2nd and did not surface the pattern. It took a second ticket, four days later, for the connection to be made. Six days is too long for a customer-facing feature to be silently failing.\n\n### Could the issue have been prevented?\n\nThe regression was introduced in April and sat latent until a leader failed to shut down cleanly for the first time. The fragility was in the lock's release path, the case where a leader stops without releasing cleanly, which is precisely the kind of edge that is easy to miss in review and under-covered by tests. We did not catch it at either stage.\n\n## Actions\n\nWe have added alerting on notification throughput, so that a drop-off in sends is positively and quickly identifiable rather than depending on customer reports.\n\nWe have fixed the code so that a lock held by a stopped leader is reliably released and picked up by another process, rather than leaving the work stuck.\n\nWe have added tests around the configuration to ensure we cannot fall foul of the misconfiguration by accident, and integration tests to show that an orphaned lock can be obtained by another process.\n\nWe are reviewing how we handle support tickets that describe an absence of expected behavior, so that a single ticket of this kind prompts a check of the relevant telemetry sooner.",
"postmortem_body_last_updated_at": "2026-07-08T19:53:21.838Z",
"postmortem_ignored": false,
"postmortem_notified_subscribers": true,
"postmortem_notified_twitter": false,
"postmortem_published_at": "2026-07-08T19:48:53.630Z",
"reminder_intervals": null,
"resolved_at": "2026-07-07T11:12:21.242Z",
"scheduled_auto_completed": false,
"scheduled_auto_in_progress": false,
"scheduled_for": null,
"scheduled_remind_prior": false,
"scheduled_reminded_at": null,
"scheduled_until": null,
"shortlink": "https://stspg.io/txvbdqqjykn6",
"started_at": "2026-07-07T10:12:51.626Z",
"status": "resolved",
"updated_at": "2026-07-08T19:53:21.841Z"
},
{
"components": [
{
"created_at": "2015-08-05T15:44:28.870Z",
"description": null,
"group_id": null,
"id": "7wxdr24f6zns",
"name": "API",
"page_id": "6m5v2lqb4txt",
"position": 2,
"showcase": true,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-07T10:20:54.634Z"
}
],
"created_at": "2026-06-16T09:25:46.755Z",
"id": "xfndlfkqzyh2",
"impact": "minor",
"impact_override": null,
"incident_updates": [
{
"affected_components": [
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "operational",
"old_status": "degraded_performance"
}
],
"body": "The mitigation has been completed. Increased API errors were observed from 09:30:30 to 09:31:30 UTC.",
"created_at": "2026-06-16T09:56:04.575Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-16T09:56:04.575Z",
"id": "04ksby7mqk98",
"incident_id": "xfndlfkqzyh2",
"status": "resolved",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-16T09:56:04.575Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "degraded_performance",
"old_status": "operational"
}
],
"body": "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.",
"created_at": "2026-06-16T09:25:46.840Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-16T09:25:46.840Z",
"id": "458xk2s3nl00",
"incident_id": "xfndlfkqzyh2",
"status": "identified",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-16T09:25:46.840Z",
"wants_twitter_update": false
}
],
"metadata": {},
"monitoring_at": null,
"name": "Increased API errors in our US data center",
"page_id": "6m5v2lqb4txt",
"postmortem_body": null,
"postmortem_body_last_updated_at": null,
"postmortem_ignored": false,
"postmortem_notified_subscribers": false,
"postmortem_notified_twitter": false,
"postmortem_published_at": null,
"reminder_intervals": null,
"resolved_at": "2026-06-16T09:56:04.575Z",
"scheduled_auto_completed": false,
"scheduled_auto_in_progress": false,
"scheduled_for": null,
"scheduled_remind_prior": false,
"scheduled_reminded_at": null,
"scheduled_until": null,
"shortlink": "https://stspg.io/b1fdlnwl9mb3",
"started_at": "2026-06-16T09:25:46.746Z",
"status": "resolved",
"updated_at": "2026-06-16T09:56:04.590Z"
},
{
"components": [
{
"created_at": "2021-03-01T16:20:14.489Z",
"description": null,
"group_id": null,
"id": "7hc2dnlph2ns",
"name": "Scheduler",
"page_id": "6m5v2lqb4txt",
"position": 1,
"showcase": true,
"start_date": "2021-03-01T00:00:00.000Z",
"status": "operational",
"updated_at": "2026-06-14T09:54:31.655Z"
},
{
"created_at": "2015-08-05T15:44:28.870Z",
"description": null,
"group_id": null,
"id": "7wxdr24f6zns",
"name": "API",
"page_id": "6m5v2lqb4txt",
"position": 2,
"showcase": true,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-07T10:20:54.634Z"
},
{
"created_at": "2015-08-05T15:43:44.897Z",
"description": null,
"group_id": null,
"id": "v5h8cvtfpsw6",
"name": "Background Processing",
"page_id": "6m5v2lqb4txt",
"position": 4,
"showcase": true,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-08T19:57:24.277Z"
},
{
"created_at": "2015-08-05T15:43:44.913Z",
"description": null,
"group_id": null,
"id": "gk9tm2621bkp",
"name": "Developer Dashboard",
"page_id": "6m5v2lqb4txt",
"position": 5,
"showcase": true,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-08T19:57:24.283Z"
}
],
"created_at": "2026-06-08T16:00:03.019Z",
"id": "x4gq3y04qgmm",
"impact": "maintenance",
"impact_override": null,
"incident_updates": [
{
"affected_components": [
{
"code": "v5h8cvtfpsw6",
"name": "Background Processing",
"new_status": "operational",
"old_status": "under_maintenance"
},
{
"code": "gk9tm2621bkp",
"name": "Developer Dashboard",
"new_status": "operational",
"old_status": "under_maintenance"
},
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "operational",
"old_status": "under_maintenance"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "operational",
"old_status": "under_maintenance"
}
],
"body": "The scheduled maintenance has been completed successfully. We observed disruption at the following times (UTC):\n\nSingapore: No disruption observed\nAustralia: 07:30:15 - 07:30:30\nUK: No disruption observed\nCanada: 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\nGermany: 08:47:30 - 08:49:00\nUS: 09:16:30 - 09:16:45\n\nIf you have any questions, please email support@cronofy.com.",
"created_at": "2026-06-14T09:54:31.760Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-14T09:54:31.760Z",
"id": "bch9wl50g50d",
"incident_id": "x4gq3y04qgmm",
"status": "completed",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-14T09:54:31.760Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "v5h8cvtfpsw6",
"name": "Background Processing",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "gk9tm2621bkp",
"name": "Developer Dashboard",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
}
],
"body": "The update is complete in our US data center. We observed disruption from 09:16:30 to 09:16:45 UTC.\n\nWe 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.",
"created_at": "2026-06-14T09:41:22.224Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-14T09:41:22.224Z",
"id": "8cshc9g7v0x3",
"incident_id": "x4gq3y04qgmm",
"status": "verifying",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-14T09:41:22.224Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "v5h8cvtfpsw6",
"name": "Background Processing",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "gk9tm2621bkp",
"name": "Developer Dashboard",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
}
],
"body": "The update is complete in our Germany data center. We observed disruption from 08:47:30 to 08:49:00 UTC.\n\nWe are beginning the update in our US data center.",
"created_at": "2026-06-14T09:00:12.736Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-14T09:00:12.736Z",
"id": "w3rj8tn66y0v",
"incident_id": "x4gq3y04qgmm",
"status": "in_progress",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-14T09:00:12.736Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "v5h8cvtfpsw6",
"name": "Background Processing",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "gk9tm2621bkp",
"name": "Developer Dashboard",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
}
],
"body": "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.\n\nWe are beginning the update in our Germany data center.",
"created_at": "2026-06-14T08:37:06.255Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-14T08:37:06.255Z",
"id": "bxz1jp0dqbdr",
"incident_id": "x4gq3y04qgmm",
"status": "in_progress",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-14T08:37:06.255Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "v5h8cvtfpsw6",
"name": "Background Processing",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "gk9tm2621bkp",
"name": "Developer Dashboard",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
}
],
"body": "The update is complete in our UK data center. There was no observed disruption.\n\nWe are beginning the update in our Canada data center.",
"created_at": "2026-06-14T08:07:36.115Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-14T08:07:36.115Z",
"id": "dkk02ng35lzv",
"incident_id": "x4gq3y04qgmm",
"status": "in_progress",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-14T08:07:36.115Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "v5h8cvtfpsw6",
"name": "Background Processing",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "gk9tm2621bkp",
"name": "Developer Dashboard",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
}
],
"body": "The update is complete in our Australia data center. We observed disruption from 07:30:15 to 07:30:30 UTC.\n\nWe are beginning the update in our UK data center.",
"created_at": "2026-06-14T07:43:35.899Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-14T07:43:35.899Z",
"id": "0r9ysv7gd4jq",
"incident_id": "x4gq3y04qgmm",
"status": "in_progress",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-14T07:43:35.899Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "v5h8cvtfpsw6",
"name": "Background Processing",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "gk9tm2621bkp",
"name": "Developer Dashboard",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "under_maintenance",
"old_status": "under_maintenance"
}
],
"body": "The update is complete in our Singapore data center. There was no observed disruption.\n\nWe are beginning the update in our Australia data center.",
"created_at": "2026-06-14T07:19:14.874Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-14T07:19:14.874Z",
"id": "1ymfm52dvk6m",
"incident_id": "x4gq3y04qgmm",
"status": "in_progress",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-14T07:19:14.874Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "v5h8cvtfpsw6",
"name": "Background Processing",
"new_status": "under_maintenance",
"old_status": "operational"
},
{
"code": "gk9tm2621bkp",
"name": "Developer Dashboard",
"new_status": "under_maintenance",
"old_status": "operational"
},
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "under_maintenance",
"old_status": "operational"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "under_maintenance",
"old_status": "operational"
}
],
"body": "The scheduled maintenance is in progress. We are beginning the update in our Singapore data center.",
"created_at": "2026-06-14T07:00:01.450Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-14T07:00:01.450Z",
"id": "tpm9fz4zm0yf",
"incident_id": "x4gq3y04qgmm",
"status": "in_progress",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-14T07:00:01.450Z",
"wants_twitter_update": false
},
{
"affected_components": null,
"body": "Maintenance will begin as scheduled in 60 minutes.",
"created_at": "2026-06-14T06:00:29.008Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-14T06:00:29.008Z",
"id": "y47h2wj61g72",
"incident_id": "x4gq3y04qgmm",
"status": "scheduled",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-14T06:00:29.008Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "v5h8cvtfpsw6",
"name": "Background Processing",
"new_status": "operational",
"old_status": "operational"
},
{
"code": "gk9tm2621bkp",
"name": "Developer Dashboard",
"new_status": "operational",
"old_status": "operational"
},
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "operational",
"old_status": "operational"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "operational",
"old_status": "operational"
}
],
"body": "We will be upgrading the instance types used within our cache and database clusters in all data centers.\n\nThese 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.\n\nWe will provide notifications as this maintenance progresses via our status page.\n\nIf you have any questions, please email support@cronofy.com.",
"created_at": "2026-06-08T16:00:03.090Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-08T16:00:03.090Z",
"id": "jthgtzbh57qd",
"incident_id": "x4gq3y04qgmm",
"status": "scheduled",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-08T16:00:03.090Z",
"wants_twitter_update": false
}
],
"metadata": {},
"monitoring_at": "2026-06-14T09:41:22.224Z",
"name": "Cache and database cluster instance type upgrades in all data centers",
"page_id": "6m5v2lqb4txt",
"postmortem_body": null,
"postmortem_body_last_updated_at": null,
"postmortem_ignored": false,
"postmortem_notified_subscribers": false,
"postmortem_notified_twitter": false,
"postmortem_published_at": null,
"reminder_intervals": null,
"resolved_at": "2026-06-14T09:54:31.760Z",
"scheduled_auto_completed": false,
"scheduled_auto_in_progress": false,
"scheduled_for": "2026-06-14T07:00:00.000Z",
"scheduled_remind_prior": true,
"scheduled_reminded_at": "2026-06-14T06:00:29.223Z",
"scheduled_until": "2026-06-14T10:00:00.000Z",
"shortlink": "https://stspg.io/2s6cc0k0q14t",
"started_at": "2026-06-08T16:00:03.008Z",
"status": "completed",
"updated_at": "2026-06-14T09:54:31.788Z"
},
{
"components": [
{
"created_at": "2026-06-03T14:58:03.425Z",
"description": "Meeting Agent infrastructure for joining Google Meet calls",
"group_id": "lwk6jxjgl456",
"id": "yw553xq25fjq",
"name": "Google Meet",
"page_id": "6m5v2lqb4txt",
"position": 2,
"showcase": true,
"start_date": "2026-01-01T00:00:00.000Z",
"status": "operational",
"updated_at": "2026-11-16T12:41:23.087Z"
}
],
"created_at": "2026-06-03T15:12:41.281Z",
"id": "rjphtm5zz2sm",
"impact": "minor",
"impact_override": "minor",
"incident_updates": [
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "operational",
"old_status": "degraded_performance"
}
],
"body": "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.",
"created_at": "2026-06-04T13:05:10.692Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-04T13:05:10.692Z",
"id": "blr17lf352qh",
"incident_id": "rjphtm5zz2sm",
"status": "resolved",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-04T13:05:10.692Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "We are now rolling out a further fix which has tested well internally, and will continue to monitor its performance.",
"created_at": "2026-06-04T11:00:43.824Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-04T11:00:43.824Z",
"id": "pfwcpj3rrhwj",
"incident_id": "rjphtm5zz2sm",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-04T11:00:43.824Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "degraded_performance",
"old_status": "operational"
}
],
"body": "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.",
"created_at": "2026-06-04T09:39:22.162Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-04T09:39:22.162Z",
"id": "nv7dk8bhdlmk",
"incident_id": "rjphtm5zz2sm",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-04T09:39:22.162Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "operational",
"old_status": "operational"
}
],
"body": "Google Meet Meeting Agents are making join attempts successfully since the fix release earlier. We will continue to monitor their performance.",
"created_at": "2026-06-03T18:34:03.669Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-03T18:34:03.669Z",
"id": "508jcvz1h9p8",
"incident_id": "rjphtm5zz2sm",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-03T18:34:03.669Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "operational",
"old_status": "major_outage"
}
],
"body": "We are continuing to monitor for any further issues.",
"created_at": "2026-06-03T18:30:06.199Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-03T18:30:06.199Z",
"id": "lj15jdmv13v9",
"incident_id": "rjphtm5zz2sm",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-03T18:30:06.199Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "major_outage",
"old_status": "major_outage"
}
],
"body": "We are rolling out a fix which has tested positively internally, and will be monitoring success rates",
"created_at": "2026-06-03T16:31:39.527Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-03T16:31:39.527Z",
"id": "jkkphggf10xv",
"incident_id": "rjphtm5zz2sm",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-03T16:31:39.527Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "yw553xq25fjq",
"name": "Meeting Agents - Google Meet",
"new_status": "major_outage",
"old_status": "operational"
}
],
"body": "We have seen that Google Meet Meeting Agents are being rejected from the meetings before being able to join and are investigating the issue.\n\nThese meetings will fail to be recorded and transcribed.",
"created_at": "2026-06-03T15:12:41.356Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-03T15:12:41.356Z",
"id": "59kz6w1601gh",
"incident_id": "rjphtm5zz2sm",
"status": "investigating",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-03T15:12:41.356Z",
"wants_twitter_update": false
}
],
"metadata": {},
"monitoring_at": "2026-06-03T16:31:39.527Z",
"name": "Google Meet Meeting Agents failing to join",
"page_id": "6m5v2lqb4txt",
"postmortem_body": null,
"postmortem_body_last_updated_at": null,
"postmortem_ignored": false,
"postmortem_notified_subscribers": false,
"postmortem_notified_twitter": false,
"postmortem_published_at": null,
"reminder_intervals": null,
"resolved_at": "2026-06-04T13:05:10.692Z",
"scheduled_auto_completed": false,
"scheduled_auto_in_progress": false,
"scheduled_for": null,
"scheduled_remind_prior": false,
"scheduled_reminded_at": null,
"scheduled_until": null,
"shortlink": "https://stspg.io/npkk4779jn0f",
"started_at": "2026-06-03T15:12:41.270Z",
"status": "resolved",
"updated_at": "2026-06-04T13:05:10.713Z"
},
{
"components": [
{
"created_at": "2015-08-06T09:23:14.152Z",
"description": null,
"group_id": "g2vfx6bv0m2n",
"id": "lbym3z60fm1f",
"name": "Google",
"page_id": "6m5v2lqb4txt",
"position": 2,
"showcase": false,
"start_date": null,
"status": "operational",
"updated_at": "2026-06-02T20:29:58.616Z"
}
],
"created_at": "2026-06-02T13:40:23.072Z",
"id": "0zffp08ws9k2",
"impact": "minor",
"impact_override": null,
"incident_updates": [
{
"affected_components": [
{
"code": "lbym3z60fm1f",
"name": "Major Calendar Providers - Google",
"new_status": "operational",
"old_status": "degraded_performance"
}
],
"body": "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. \n\nThe 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.\n\nWe will continue to monitor the situation and will raise a new incident if performance declines to a noticeable level.",
"created_at": "2026-06-02T20:29:58.652Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-02T20:29:58.652Z",
"id": "w1209tf69nz9",
"incident_id": "0zffp08ws9k2",
"status": "resolved",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-02T20:29:58.652Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "lbym3z60fm1f",
"name": "Major Calendar Providers - Google",
"new_status": "degraded_performance",
"old_status": "degraded_performance"
}
],
"body": "We are continuing to see elevated errors when communicating with Google Calendar.\nCronofy 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.\n\nWe are continuing to monitor the situation, but will only update this incident if there is a significant change in either direction.",
"created_at": "2026-06-02T16:55:14.253Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-02T16:55:14.253Z",
"id": "xrgn0br3ts3q",
"incident_id": "0zffp08ws9k2",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-02T16:55:14.253Z",
"wants_twitter_update": false
},
{
"affected_components": [
{
"code": "lbym3z60fm1f",
"name": "Major Calendar Providers - Google",
"new_status": "degraded_performance",
"old_status": "operational"
}
],
"body": "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.",
"created_at": "2026-06-02T13:40:23.166Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-06-02T13:40:23.166Z",
"id": "8k6r6jvt0s36",
"incident_id": "0zffp08ws9k2",
"status": "monitoring",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-06-02T13:40:23.166Z",
"wants_twitter_update": false
}
],
"metadata": {},
"monitoring_at": "2026-06-02T13:40:23.166Z",
"name": "Increased error rates for some Google calendar sync operations",
"page_id": "6m5v2lqb4txt",
"postmortem_body": null,
"postmortem_body_last_updated_at": null,
"postmortem_ignored": false,
"postmortem_notified_subscribers": false,
"postmortem_notified_twitter": false,
"postmortem_published_at": null,
"reminder_intervals": null,
"resolved_at": "2026-06-02T20:29:58.652Z",
"scheduled_auto_completed": false,
"scheduled_auto_in_progress": false,
"scheduled_for": null,
"scheduled_remind_prior": false,
"scheduled_reminded_at": null,
"scheduled_until": null,
"shortlink": "https://stspg.io/5hf38h8fhz8f",
"started_at": "2026-06-02T13:40:23.060Z",
"status": "resolved",
"updated_at": "2026-06-02T20:29:58.671Z"
},
{
"components": [
{
"created_at": "2021-03-01T16:20:14.489Z",
"description": null,
"group_id": null,
"id": "7hc2dnlph2ns",
"name": "Scheduler",
"page_id": "6m5v2lqb4txt",
"position": 1,
"showcase": true,
"start_date": "2021-03-01T00:00:00.000Z",
"status": "operational",
"updated_at": "2026-06-14T09:54:31.655Z"
},
{
"created_at": "2015-08-05T15:44:28.870Z",
"description": null,
"group_id": null,
"id": "7wxdr24f6zns",
"name": "API",
"page_id": "6m5v2lqb4txt",
"position": 2,
"showcase": true,
"start_date": null,
"status": "operational",
"updated_at": "2026-07-07T10:20:54.634Z"
}
],
"created_at": "2026-05-14T10:37:32.966Z",
"id": "mt55ykv7ynhf",
"impact": "none",
"impact_override": null,
"incident_updates": [
{
"affected_components": [
{
"code": "7wxdr24f6zns",
"name": "API",
"new_status": "operational",
"old_status": "operational"
},
{
"code": "7hc2dnlph2ns",
"name": "Scheduler",
"new_status": "operational",
"old_status": "operational"
}
],
"body": "Between 03:08 UTC and 03:10 UTC we observed increased API error rates in our US data center. During this time, customers may have received 500 Internal Server Error responses. Since that time, error rates have returned to normal levels.\n\nThese errors were caused by a read-only database server going through an automated recovery process.",
"created_at": "2026-05-14T10:37:33.014Z",
"custom_tweet": null,
"deliver_notifications": true,
"display_at": "2026-05-14T10:37:33.014Z",
"id": "0xljc9603skv",
"incident_id": "mt55ykv7ynhf",
"status": "resolved",
"tweet_id": null,
"twitter_updated_at": null,
"updated_at": "2026-05-14T10:37:33.014Z",
"wants_twitter_update": false
}
],
"metadata": {},
"monitoring_at": null,
"name": "Increased API errors in our US data center",
"page_id": "6m5v2lqb4txt",
"postmortem_body": null,
"postmortem_body_last_updated_at": null,
"postmortem_ignored": false,
"postmortem_notified_subscribers": false,
"postmortem_notified_twitter": false,
"postmortem_published_at": null,
"reminder_intervals": null,
"resolved_at": "2026-05-14T10:37:33.014Z",
"scheduled_auto_completed": false,
"scheduled_auto_in_progress": false,
"scheduled_for": null,
"scheduled_remind_prior": false,
"scheduled_reminded_at": null,
"scheduled_until": null,
"shortlink": "https://stspg.io/kxx85rr40qrv",
"started_at": "2026-05-14T10:37:32.961Z",
"status": "resolved",
"updated_at": "2026-05-14T10:37:33.024Z"
}
],
"page": {
"id": "6m5v2lqb4txt",
"name": "Cronofy",
"url": "https://status.cronofy.com"
},
"status": {
"description": "All Systems Operational",
"indicator": "none"
}
}