Snapshot 11581
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"incidents": [
{
"created_at": "2026-08-20T14:42:56Z",
"id": "01M0FT01J8EJQNVVYTMG9DJE94",
"impact": "minor",
"incident_updates": [
{
"body": "Latency has now returned to normal.\n\nBetween 13:00 and 15:08 UTC there were periods of increased latency from some Microsoft APIs. Messages in Microsoft Teams were delivered with increased latency. Our dashboard and mobile app were not affected.",
"created_at": "2026-08-20T16:31:44Z",
"display_at": "2026-08-20T16:31:44Z",
"id": "01M0G0791K2NZCGX5RSRKS4VTV",
"incident_id": "01M0FT01J8EJQNVVYTMG9DJE94",
"status": "resolved",
"updated_at": "2026-08-20T16:31:44Z"
},
{
"body": "We are continuing to see periods of increased latency with our Microsoft Teams app. All other surfaces, including the dashboard and our mobile app, remain unaffected.",
"created_at": "2026-08-20T15:31:01Z",
"display_at": "2026-08-20T15:31:01Z",
"id": "01M0FWR2T02J9GKMNDP3SWTWC7",
"incident_id": "01M0FT01J8EJQNVVYTMG9DJE94",
"status": "identified",
"updated_at": "2026-08-20T15:31:01Z"
},
{
"body": "We have identified increased latency in our Microsoft Teams app. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.",
"created_at": "2026-08-20T14:42:56Z",
"display_at": "2026-08-20T14:42:56Z",
"id": "01M0FT01J82E7F607SY1YVJ425",
"incident_id": "01M0FT01J8EJQNVVYTMG9DJE94",
"status": "identified",
"updated_at": "2026-08-20T14:42:56Z"
}
],
"name": "Increased latency in Microsoft Teams",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-08-20T16:31:44Z",
"status": "resolved",
"updated_at": "2026-08-20T16:31:44Z"
},
{
"created_at": "2026-08-18T13:55:30Z",
"id": "01M0AJFRZS0BQHGKJGQCTW94DQ",
"impact": "minor",
"incident_updates": [
{
"body": "We've now rolled back and listing alerts is working normally again.",
"created_at": "2026-08-18T13:55:30Z",
"display_at": "2026-08-18T11:37:00Z",
"id": "01M0AJFRZSA2QVKRT117S1HCNG",
"incident_id": "01M0AJFRZS0BQHGKJGQCTW94DQ",
"status": "resolved",
"updated_at": "2026-08-18T13:55:30Z"
},
{
"body": "We've identified an issue listing alerts. Regular alerting and paging is unaffected.",
"created_at": "2026-08-18T13:55:30Z",
"display_at": "2026-08-18T11:24:00Z",
"id": "01M0AJFRZSR88YC0962G9Q2Y40",
"incident_id": "01M0AJFRZS0BQHGKJGQCTW94DQ",
"status": "identified",
"updated_at": "2026-08-18T13:55:30Z"
}
],
"name": "Issue with listing alerts in the public API and dashboard",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-08-18T11:37:00Z",
"status": "resolved",
"updated_at": "2026-08-27T14:05:31Z"
},
{
"created_at": "2026-08-03T15:56:51Z",
"id": "01KZ45F5YJP4CX02D7E59TEME0",
"impact": "minor",
"incident_updates": [
{
"body": "Opsgenie webhook delivery returned to normal at around 17:48 BST",
"created_at": "2026-08-03T17:04:37Z",
"display_at": "2026-08-03T17:04:37Z",
"id": "01KZ49B8FR6FEKJ4H6F4FV10FR",
"incident_id": "01KZ45F5YJP4CX02D7E59TEME0",
"status": "resolved",
"updated_at": "2026-08-03T17:04:37Z"
},
{
"body": "We have identified increased webhook latency with our Opsgenie integration. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.",
"created_at": "2026-08-03T15:56:51Z",
"display_at": "2026-08-03T15:56:51Z",
"id": "01KZ45F5YJVSP9DQ7NA9YEY2R7",
"incident_id": "01KZ45F5YJP4CX02D7E59TEME0",
"status": "identified",
"updated_at": "2026-08-03T15:56:51Z"
}
],
"name": "Delays in webhooks from Opsgenie",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-08-03T17:04:37Z",
"status": "resolved",
"updated_at": "2026-08-03T17:04:37Z"
},
{
"created_at": "2026-08-01T02:46:20Z",
"id": "01KYXKE8X9H96CXMSQNFV2MQ1R",
"impact": "major",
"incident_updates": [
{
"body": "Between around 00:00 and 02:44 UTC, some AI features returned increased error rates. We are now seeing full recovery.",
"created_at": "2026-08-01T02:46:20Z",
"display_at": "2026-08-01T02:45:00Z",
"id": "01KYXKE8X9WZQQ4140DH4TSZG9",
"incident_id": "01KYXKE8X9H96CXMSQNFV2MQ1R",
"status": "resolved",
"updated_at": "2026-08-01T02:46:20Z"
},
{
"body": "We detected increased error rates with some AI features.",
"created_at": "2026-08-01T02:46:20Z",
"display_at": "2026-08-01T00:08:00Z",
"id": "01KYXKE8X998RYD9Y1SYG5275G",
"incident_id": "01KYXKE8X9H96CXMSQNFV2MQ1R",
"status": "investigating",
"updated_at": "2026-08-01T02:46:20Z"
}
],
"name": "AI features degraded",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-08-01T02:45:00Z",
"status": "resolved",
"updated_at": "2026-08-01T02:46:20Z"
},
{
"created_at": "2026-07-16T08:32:01Z",
"id": "01KXN0VQK1R6K8V4EKT0P04G70",
"impact": "critical",
"incident_updates": [
{
"body": "SAML login has continued to perform as normal.",
"created_at": "2026-07-16T10:54:10Z",
"display_at": "2026-07-16T10:54:10Z",
"id": "01KXN900MA4558VV4SYGR75H5P",
"incident_id": "01KXN0VQK1R6K8V4EKT0P04G70",
"status": "resolved",
"updated_at": "2026-07-16T10:54:10Z"
},
{
"body": "SAML logins are now performing as normal. We'll continue to monitor for any further issues.",
"created_at": "2026-07-16T10:29:02Z",
"display_at": "2026-07-16T10:29:02Z",
"id": "01KXN7J0097BSA25NFQETEMXEK",
"incident_id": "01KXN0VQK1R6K8V4EKT0P04G70",
"status": "monitoring",
"updated_at": "2026-07-16T10:29:02Z"
},
{
"body": "We're continuing to see elevated errors and latency with SAML logins.\n\nAll other functionality remains unaffected.",
"created_at": "2026-07-16T10:16:01Z",
"display_at": "2026-07-16T10:16:01Z",
"id": "01KXN6T5DXFCR46414H5JV6W0G",
"incident_id": "01KXN0VQK1R6K8V4EKT0P04G70",
"status": "monitoring",
"updated_at": "2026-07-16T10:16:01Z"
},
{
"body": "SAML logins are now working with increased latency. We'll continue to monitor until fully recovered.\n\nAll other functionality remains unaffected.",
"created_at": "2026-07-16T09:27:44Z",
"display_at": "2026-07-16T09:27:44Z",
"id": "01KXN41R5P81NZQ3NQA2V64RYX",
"incident_id": "01KXN0VQK1R6K8V4EKT0P04G70",
"status": "monitoring",
"updated_at": "2026-07-16T09:27:44Z"
},
{
"body": "This issue remains ongoing and we're working on a resolution.\n\nAll other functionality is unaffected. Existing sessions on the mobile app and dashboard are unaffected and continue to have access as normal. We'll post our next update in the next 30 minutes.",
"created_at": "2026-07-16T09:12:14Z",
"display_at": "2026-07-16T09:12:14Z",
"id": "01KXN35BNHVMRJZGFDKWMZ5CYC",
"incident_id": "01KXN0VQK1R6K8V4EKT0P04G70",
"status": "identified",
"updated_at": "2026-07-16T09:12:14Z"
},
{
"body": "We're aware of issues affecting some customers logging in using SAML - we're investigating and will provide an update shortly.",
"created_at": "2026-07-16T08:32:01Z",
"display_at": "2026-07-16T08:32:01Z",
"id": "01KXN0VQK1MBTE7EC1KR2HP1E5",
"incident_id": "01KXN0VQK1R6K8V4EKT0P04G70",
"status": "investigating",
"updated_at": "2026-07-16T08:32:01Z"
}
],
"name": "Issues affecting login with SAML",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-07-16T10:54:10Z",
"status": "resolved",
"updated_at": "2026-07-16T10:54:10Z"
},
{
"created_at": "2026-06-23T19:45:27Z",
"id": "01KVV089C0YSE3QK9CBMA8J449",
"impact": "minor",
"incident_updates": [
{
"body": "We observed a limited increase in latency as well as a small number of dashboard errors between 19:31:30 and 19:34:30 UTC. This affected 0\\.03% of calls to our dashboard. This was detected by our internal synthetic monitoring. \n\nThe cause of these elevated errors was due to networking issues within GCP at the time. This is confirmed by our logs showing our GCP load balancer not forwarding success responses, as well as network timeouts when trying to reach external services. \n\nThe impact was limited to a small number of users and was solved by refreshing the dashboard.",
"created_at": "2026-06-25T11:51:53Z",
"display_at": "2026-06-25T11:51:53Z",
"id": "01KVZ9YKG3GNAP9G6KXFPWYVR5",
"incident_id": "01KVV089C0YSE3QK9CBMA8J449",
"status": "resolved",
"updated_at": "2026-06-25T11:51:53Z"
},
{
"body": "Between 19:31:30 and 19:34:30 UTC, some requests to our dashboard hit increased latency and connectivity errors. The cause was an upstream networking incident on Google Cloud Platform. Errors were transient and refreshing usually cleared them.\n\nLatency and error rates are back to normal and we're keeping an eye on things. We'll post a post-mortem covering the full impact.",
"created_at": "2026-06-23T20:25:28Z",
"display_at": "2026-06-23T20:25:28Z",
"id": "01KVV2HHYXF0B2CBX73KBVQ6HZ",
"incident_id": "01KVV089C0YSE3QK9CBMA8J449",
"status": "resolved",
"updated_at": "2026-06-23T20:25:28Z"
},
{
"body": "Latency and error rates have returned to normal. We're continuing to monitor for any further issues.",
"created_at": "2026-06-23T19:55:28Z",
"display_at": "2026-06-23T19:55:28Z",
"id": "01KVV0TM5XR26TAD4W9SP3GGMX",
"incident_id": "01KVV089C0YSE3QK9CBMA8J449",
"status": "monitoring",
"updated_at": "2026-06-23T19:55:28Z"
},
{
"body": "We have identified increased latency and timeouts affecting some requests to our dashboard. Issues seem to be transient, and we recommend refreshing.\n\nWe are continuing to investigate.",
"created_at": "2026-06-23T19:45:27Z",
"display_at": "2026-06-23T19:45:27Z",
"id": "01KVV089C028HE1QH64NRKVDEZ",
"incident_id": "01KVV089C0YSE3QK9CBMA8J449",
"status": "investigating",
"updated_at": "2026-06-23T19:45:27Z"
}
],
"name": "Intermittent dashboard errors",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-06-23T20:25:28Z",
"status": "resolved",
"updated_at": "2026-06-25T11:51:53Z"
},
{
"created_at": "2026-05-27T22:42:26Z",
"id": "01KSNSMYPEFW5W7941HRA7C5E6",
"impact": "minor",
"incident_updates": [
{
"body": "Slack have confirmed their services have largely returned to operational levels. We've not seen any direct impact on our Slack app since ~23:20 UTC yesterday. We're resolving this on our side, and you can follow any further updates on Slack’s status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f).",
"created_at": "2026-05-28T06:29:48Z",
"display_at": "2026-05-28T06:29:48Z",
"id": "01KSPMCQ7P9NX2VKWG2WM0W84W",
"incident_id": "01KSNSMYPEFW5W7941HRA7C5E6",
"status": "resolved",
"updated_at": "2026-05-28T06:29:48Z"
},
{
"body": "We are continuing to monitor Slack as it recovers. We are not seeing any direct impact on our Slack app.\n\nYou can follow updates on Slack’s status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f \"here\").",
"created_at": "2026-05-28T02:31:04Z",
"display_at": "2026-05-28T02:31:04Z",
"id": "01KSP6QKFJXJX99V43X4KFEN3V",
"incident_id": "01KSNSMYPEFW5W7941HRA7C5E6",
"status": "monitoring",
"updated_at": "2026-05-28T02:31:04Z"
},
{
"body": "We are continuing to monitor Slack as it continues to recover, and are no longer seeing any direct impact on our Slack app\n\nYou can follow updates on Slack's status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f \"here\").",
"created_at": "2026-05-28T00:19:17Z",
"display_at": "2026-05-28T00:19:17Z",
"id": "01KSNZ69PJTDK9YBCP0D8HGYBD",
"incident_id": "01KSNSMYPEFW5W7941HRA7C5E6",
"status": "monitoring",
"updated_at": "2026-05-28T00:19:17Z"
},
{
"body": "Error rates and latency on Slack operations have returned to normal, and the integration has recovered.\n\nYou can follow updates on Slack's status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f).",
"created_at": "2026-05-27T23:21:02Z",
"display_at": "2026-05-27T23:21:02Z",
"id": "01KSNVVM7YS8SQBGKJ3KD7G81P",
"incident_id": "01KSNSMYPEFW5W7941HRA7C5E6",
"status": "monitoring",
"updated_at": "2026-05-27T23:21:02Z"
},
{
"body": "Slack have acknowledged the incident on their side. You can follow their status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f).",
"created_at": "2026-05-27T23:02:32Z",
"display_at": "2026-05-27T23:02:32Z",
"id": "01KSNTSQVD7C4EJ72BSZSHPASB",
"incident_id": "01KSNSMYPEFW5W7941HRA7C5E6",
"status": "identified",
"updated_at": "2026-05-27T23:02:32Z"
},
{
"body": "We have identified increased error rates with our Slack integration. We are currently investigating how this is impacting our platform - this seems to be an issue on the Slack side, particularly around channel creation and message delivery.",
"created_at": "2026-05-27T22:42:26Z",
"display_at": "2026-05-27T22:42:26Z",
"id": "01KSNSMYPE45HZG3Q30KF0J3AW",
"incident_id": "01KSNSMYPEFW5W7941HRA7C5E6",
"status": "identified",
"updated_at": "2026-05-27T22:42:26Z"
}
],
"name": "Issue with Slack integration",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-05-28T06:29:48Z",
"status": "resolved",
"updated_at": "2026-05-28T06:29:48Z"
},
{
"created_at": "2026-05-14T14:08:13Z",
"id": "01KRKD2198XMDEEHN103BF81XQ",
"impact": "major",
"incident_updates": [
{
"body": "The issue has been resolved on Slack's side and we've confirmed that things look normal on our side too.",
"created_at": "2026-05-14T15:45:15Z",
"display_at": "2026-05-14T15:45:15Z",
"id": "01KRKJKQCYZPNNGBWPSVPHWZTD",
"incident_id": "01KRKD2198XMDEEHN103BF81XQ",
"status": "resolved",
"updated_at": "2026-05-14T15:45:15Z"
},
{
"body": "We're continuing to monitor the situation - Slack have posted an update on their status page to confirm that they're working on it. ",
"created_at": "2026-05-14T15:15:55Z",
"display_at": "2026-05-14T15:15:55Z",
"id": "01KRKGY0SVVKXK48MR52D4QV6Q",
"incident_id": "01KRKD2198XMDEEHN103BF81XQ",
"status": "monitoring",
"updated_at": "2026-05-14T15:15:55Z"
},
{
"body": "Slack have acknowledged the incident on their side. You can follow their status page [here](https://slack-status.com/2026-05/fe557ca05fdb64fa).",
"created_at": "2026-05-14T14:41:05Z",
"display_at": "2026-05-14T14:41:05Z",
"id": "01KRKEY758TZTABSFDTWEANW98",
"incident_id": "01KRKD2198XMDEEHN103BF81XQ",
"status": "monitoring",
"updated_at": "2026-05-14T14:41:05Z"
},
{
"body": "We've confirmed the issue is relating to errors being returned by Slack. This is affecting a number of features of our integration, including:\n\n• Creating incident channels\n\n• Sending messages\n\n• Syncing Slack user groups\n\nOur web dashboard continues to be available and Scribe is unaffected.",
"created_at": "2026-05-14T14:12:59Z",
"display_at": "2026-05-14T14:12:59Z",
"id": "01KRKDASA08G09ZRA2YA5KYH1R",
"incident_id": "01KRKD2198XMDEEHN103BF81XQ",
"status": "identified",
"updated_at": "2026-05-14T14:12:59Z"
},
{
"body": "We have identified increased error rates with our Slack integration. We are currently investigating how this is impacting our platform - this seems to be an issue on the Slack side, particularly around channel creation.",
"created_at": "2026-05-14T14:08:13Z",
"display_at": "2026-05-14T14:08:13Z",
"id": "01KRKD21980BX3JXH1T61GPNSP",
"incident_id": "01KRKD2198XMDEEHN103BF81XQ",
"status": "identified",
"updated_at": "2026-05-14T14:08:13Z"
}
],
"name": "Issue with Slack integration",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-05-14T15:45:15Z",
"status": "resolved",
"updated_at": "2026-05-14T15:45:15Z"
},
{
"created_at": "2026-05-07T07:37:11Z",
"id": "01KR0NX0CBM6WZQRQ5EYFGRGW4",
"impact": "critical",
"incident_updates": [
{
"body": "The website is now up and working as normal.",
"created_at": "2026-05-07T07:37:11Z",
"display_at": "2026-05-07T07:25:00Z",
"id": "01KR0NX0CBV40YH2X7FX1N88Y3",
"incident_id": "01KR0NX0CBM6WZQRQ5EYFGRGW4",
"status": "resolved",
"updated_at": "2026-05-07T07:37:11Z"
},
{
"body": "The web dashboard is unavailable due to a JavaScript deployment issue.",
"created_at": "2026-05-07T07:37:11Z",
"display_at": "2026-05-07T07:12:00Z",
"id": "01KR0NX0CBCX6RQ6GDC0DX295W",
"incident_id": "01KR0NX0CBM6WZQRQ5EYFGRGW4",
"status": "identified",
"updated_at": "2026-05-07T07:37:11Z"
}
],
"name": "Web dashboard unavailable",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-05-07T07:25:00Z",
"status": "resolved",
"updated_at": "2026-05-15T09:14:59Z"
},
{
"created_at": "2026-04-27T23:58:49Z",
"id": "01KQ8P386JA1R9FQ3FKNAXZ4RT",
"impact": "minor",
"incident_updates": [
{
"body": "Webhooks appear to arriving as normal again, so you should no longer see any delays.",
"created_at": "2026-04-28T00:14:06Z",
"display_at": "2026-04-28T00:14:06Z",
"id": "01KQ8PZ7BF4EGT8F99JSXXCEKY",
"incident_id": "01KQ8P386JA1R9FQ3FKNAXZ4RT",
"status": "resolved",
"updated_at": "2026-04-28T00:14:06Z"
},
{
"body": "We’re seeing delays of up to 30 minutes in receiving webhooks from Opsgenie, which may delay alert delivery. Our systems are operating normally and process alerts as soon as they arrive; the issue appears to be on Opsgenie’s side. We’re monitoring closely and will share updates as we learn more.",
"created_at": "2026-04-27T23:58:49Z",
"display_at": "2026-04-27T23:58:49Z",
"id": "01KQ8P386JA27C6MC7P8MEV0TE",
"incident_id": "01KQ8P386JA1R9FQ3FKNAXZ4RT",
"status": "monitoring",
"updated_at": "2026-04-27T23:58:49Z"
}
],
"name": "Delays in webhooks from Opsgenie",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-04-28T00:14:06Z",
"status": "resolved",
"updated_at": "2026-04-28T00:14:06Z"
},
{
"created_at": "2026-04-09T07:33:46Z",
"id": "01KNRJJMQPP8V5V2JRH0X7APZS",
"impact": "minor",
"incident_updates": [
{
"body": "Error rates have returned to normal levels.",
"created_at": "2026-04-09T07:55:20Z",
"display_at": "2026-04-09T07:55:20Z",
"id": "01KNRKT3NH8NCGHZF89B2TAFKD",
"incident_id": "01KNRJJMQPP8V5V2JRH0X7APZS",
"status": "resolved",
"updated_at": "2026-04-09T07:55:20Z"
},
{
"body": "We have identified increased error rates with our Atlassian Statuspage integration.\n\nAtlassian have published this to their status page [here](https://metastatuspage.com/incidents/94fwk40f4z15).",
"created_at": "2026-04-09T07:33:46Z",
"display_at": "2026-04-09T07:33:46Z",
"id": "01KNRJJMQP7ZGSNT4N5108RRZH",
"incident_id": "01KNRJJMQPP8V5V2JRH0X7APZS",
"status": "identified",
"updated_at": "2026-04-09T07:33:46Z"
}
],
"name": "Intermittent errors posting to Atlassian Statuspages",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-04-09T07:55:20Z",
"status": "resolved",
"updated_at": "2026-04-09T07:55:20Z"
},
{
"created_at": "2026-03-24T16:30:33Z",
"id": "01KMGAY02MN5W4Y1H2W83107Z3",
"impact": "minor",
"incident_updates": [
{
"body": "We are no longer seeing elevated latency and error rates from Microsoft Teams.",
"created_at": "2026-03-24T20:52:56Z",
"display_at": "2026-03-24T20:52:56Z",
"id": "01KMGSYEEBM0YFMQVPHBE0V4C4",
"incident_id": "01KMGAY02MN5W4Y1H2W83107Z3",
"status": "resolved",
"updated_at": "2026-03-24T20:52:56Z"
},
{
"body": "We have seen an improvement in error rates and latency for requests to Microsoft Teams, and we expect the performance of sending messages to Teams channels and DMs to have returned to normal.\n\nWe are continuing to monitor to ensure performance remains as expected, and we will provide a further update by 2100 UTC.",
"created_at": "2026-03-24T19:30:51Z",
"display_at": "2026-03-24T19:30:51Z",
"id": "01KMGN84PVDMYMSVF9ZKFZSVT6",
"incident_id": "01KMGAY02MN5W4Y1H2W83107Z3",
"status": "monitoring",
"updated_at": "2026-03-24T19:30:51Z"
},
{
"body": "We are continuing to see an increase in error rates from Microsoft Teams, causing a delay in sending some messages to Teams channels and DMs.\n\nWe are monitoring the situation and will provide an update by 1930 UTC.",
"created_at": "2026-03-24T18:33:15Z",
"display_at": "2026-03-24T18:33:15Z",
"id": "01KMGHYNZRX3D6WEDKH3MBZMEQ",
"incident_id": "01KMGAY02MN5W4Y1H2W83107Z3",
"status": "monitoring",
"updated_at": "2026-03-24T18:33:15Z"
},
{
"body": "We have identified increased error rates coming from Microsoft Teams that are causing delays in sending messages to Teams channels and DMs. \n\nWe'll continue to monitor the situation and we will update with more information shortly as we learn more.\n\nWe will provide the next update by 1830 UTC.",
"created_at": "2026-03-24T17:27:03Z",
"display_at": "2026-03-24T17:27:03Z",
"id": "01KMGE5F9G3XW6H15KJW76H1J7",
"incident_id": "01KMGAY02MN5W4Y1H2W83107Z3",
"status": "monitoring",
"updated_at": "2026-03-24T17:52:02Z"
},
{
"body": "We have identified increased error rates coming from Microsoft Teams. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.",
"created_at": "2026-03-24T16:30:33Z",
"display_at": "2026-03-24T16:30:33Z",
"id": "01KMGAY02M1GHB4Y7ER5VHX3PB",
"incident_id": "01KMGAY02MN5W4Y1H2W83107Z3",
"status": "identified",
"updated_at": "2026-03-24T16:30:33Z"
}
],
"name": "Increased error rates from Microsoft Teams",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-03-24T20:52:56Z",
"status": "resolved",
"updated_at": "2026-03-24T20:52:56Z"
},
{
"created_at": "2026-03-24T15:31:08Z",
"id": "01KMG7H6RDV5H54TKB9VFXVEMS",
"impact": "none",
"incident_updates": [
{
"body": "We continue to use the failover region, and Scribe performance has returned to expected levels.",
"created_at": "2026-03-24T17:02:13Z",
"display_at": "2026-03-24T17:02:13Z",
"id": "01KMGCR0EPEVG847QGK59WTE7Z",
"incident_id": "01KMG7H6RDV5H54TKB9VFXVEMS",
"status": "resolved",
"updated_at": "2026-03-24T17:02:13Z"
},
{
"body": "Our failover region is continuing to work as expected, and Scribe functionality has been restored. You may need to ask Scribe to rejoin your calls.\n\nWe'll continue to monitor the situation and are working closely with the upstream provider while they resolve the issue.",
"created_at": "2026-03-24T16:18:41Z",
"display_at": "2026-03-24T16:18:41Z",
"id": "01KMGA8968N99JHVYQ4MMSXKV3",
"incident_id": "01KMG7H6RDV5H54TKB9VFXVEMS",
"status": "monitoring",
"updated_at": "2026-03-24T16:18:41Z"
},
{
"body": "The issues were isolated to one region and we have performed a failover to a secondary region, restoring Scribe for all customers.\n\nYou may need to ask Scribe to rejoin your call.\n\nWe'll continue to monitor the situation and are working closely with the upstream provider while they resolve the issue.",
"created_at": "2026-03-24T15:33:50Z",
"display_at": "2026-03-24T15:33:50Z",
"id": "01KMG7P59M5R2AK5855JTMZX5S",
"incident_id": "01KMG7H6RDV5H54TKB9VFXVEMS",
"status": "monitoring",
"updated_at": "2026-03-24T15:43:29Z"
},
{
"body": "We have identified increased error rates with an upstream call transcription provider. This is affecting Scribe for all customers. Our team are investigating and we will update with more information shortly as we learn more.",
"created_at": "2026-03-24T15:31:08Z",
"display_at": "2026-03-24T15:31:08Z",
"id": "01KMG7H6RD4450PEX12JWP01FB",
"incident_id": "01KMG7H6RDV5H54TKB9VFXVEMS",
"status": "identified",
"updated_at": "2026-03-24T15:31:08Z"
}
],
"name": "Scribe performance degraded",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-03-24T17:02:13Z",
"status": "resolved",
"updated_at": "2026-03-24T17:02:14Z"
},
{
"created_at": "2026-03-13T14:19:16Z",
"id": "01KKKS1PTWBT4CQP2A77K64MDN",
"impact": "none",
"incident_updates": [
{
"body": "Slack have confirmed that the issue has been fully resolved, and affected customers have verified that they can log in successfully.",
"created_at": "2026-03-13T16:40:49Z",
"display_at": "2026-03-13T16:40:49Z",
"id": "01KKM14X0JECYART2EN188BNQS",
"incident_id": "01KKKS1PTWBT4CQP2A77K64MDN",
"status": "resolved",
"updated_at": "2026-03-13T16:40:49Z"
},
{
"body": "Slack have rolled back a change which caused this issue, and we have confirmed recovery.\n\nPlease reach out to support if you're still experiencing any issues signing in with Slack.",
"created_at": "2026-03-13T15:54:56Z",
"display_at": "2026-03-13T15:54:56Z",
"id": "01KKKYGW8Z0YCBXKDTMAA5QQ9N",
"incident_id": "01KKKS1PTWBT4CQP2A77K64MDN",
"status": "monitoring",
"updated_at": "2026-03-13T15:54:56Z"
},
{
"body": "Users in some Slack workspaces are unable to sign in with Slack. We have escalated this issue to Slack.\n\nSigning in with SAML and Microsoft Teams is not affected.",
"created_at": "2026-03-13T14:53:43Z",
"display_at": "2026-03-13T14:53:43Z",
"id": "01KKKV0T0WWXKN442E4X6451Y4",
"incident_id": "01KKKS1PTWBT4CQP2A77K64MDN",
"status": "identified",
"updated_at": "2026-03-13T14:53:43Z"
},
{
"body": "We are currently investigating reports that users are unable to login using Slack.",
"created_at": "2026-03-13T14:19:16Z",
"display_at": "2026-03-13T14:19:16Z",
"id": "01KKKS1PTW59JZ3DA2XH33HFQV",
"incident_id": "01KKKS1PTWBT4CQP2A77K64MDN",
"status": "investigating",
"updated_at": "2026-03-13T14:19:16Z"
}
],
"name": "Some users unable to sign in via Slack",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-03-13T16:40:49Z",
"status": "resolved",
"updated_at": "2026-03-13T16:40:49Z"
},
{
"created_at": "2026-03-12T13:20:59Z",
"id": "01KKH3A9C8B1Z8HJCX7QAF5XN4",
"impact": "minor",
"incident_updates": [
{
"body": "Traffic appears to be back to normal levels now.",
"created_at": "2026-03-12T14:27:47Z",
"display_at": "2026-03-12T14:27:47Z",
"id": "01KKH74JQDWJDB158DR14PZATB",
"incident_id": "01KKH3A9C8B1Z8HJCX7QAF5XN4",
"status": "resolved",
"updated_at": "2026-03-12T14:27:47Z"
},
{
"body": "We've identified a drop in inbound traffic to [incident.io](http://incident.io \"incident.io\") from Opsgenie. This means that alerts may be slow to show up in [incident.io](http://incident.io \"incident.io\"), and paging via Opsgenie may be slow to reflect updates.\n\nThis appears to be an issue with outbound webhooks on Opsgenie's side, we're monitoring the situation and will update as we know more.",
"created_at": "2026-03-12T13:20:59Z",
"display_at": "2026-03-12T13:20:59Z",
"id": "01KKH3A9C8S42KM9C0206BSGG1",
"incident_id": "01KKH3A9C8B1Z8HJCX7QAF5XN4",
"status": "identified",
"updated_at": "2026-03-12T13:20:59Z"
}
],
"name": "Opsgenie integration performance is degraded",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-03-12T14:27:47Z",
"status": "resolved",
"updated_at": "2026-03-12T14:27:47Z"
},
{
"created_at": "2026-02-02T11:16:51Z",
"id": "01KGF13N88J78TFTW67BHP93TQ",
"impact": "minor",
"incident_updates": [
{
"body": "Atlassian have confirmed that the issues with Statuspage have been resolved. You should now be able to reuse your original API key in our integration.",
"created_at": "2026-02-02T16:56:25Z",
"display_at": "2026-02-02T16:56:25Z",
"id": "01KGFMHEJKDYJ774BBW3KK5FWY",
"incident_id": "01KGF13N88J78TFTW67BHP93TQ",
"status": "resolved",
"updated_at": "2026-02-02T16:56:25Z"
},
{
"body": "Atlassian's status page now reports that they are rolling out a fix (\u003chttps://metastatuspage.com/incidents/ctw5xv6t643h\u003e).\n\nIn the meantime, to restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ \"incident.io.\")\n\nWe continue to monitor the issue until it is resolved.",
"created_at": "2026-02-02T16:06:59Z",
"display_at": "2026-02-02T16:06:59Z",
"id": "01KGFHPX5H4C16XD9A08GBSH51",
"incident_id": "01KGF13N88J78TFTW67BHP93TQ",
"status": "monitoring",
"updated_at": "2026-02-02T16:06:59Z"
},
{
"body": "Atlassian's status page continues to show the issue with Statuspage (\u003chttps://metastatuspage.com/incidents/ctw5xv6t643h\u003e). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ \"incident.io.\")\n\nWe'll continue to monitor this and give an update in the next hour.",
"created_at": "2026-02-02T15:41:02Z",
"display_at": "2026-02-02T15:41:02Z",
"id": "01KGFG7CR1K7EQ3HFPHH66ZKK0",
"incident_id": "01KGF13N88J78TFTW67BHP93TQ",
"status": "monitoring",
"updated_at": "2026-02-02T15:41:02Z"
},
{
"body": "Atlassian's status page continues to show the issue with Statuspage (\u003chttps://metastatuspage.com/incidents/ctw5xv6t643h\u003e). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ \"incident.io.\")\n\nWe'll continue to monitor this and give an update in the next hour.",
"created_at": "2026-02-02T14:37:26Z",
"display_at": "2026-02-02T14:37:26Z",
"id": "01KGFCJYA5GXK83KPA0D3CAWR5",
"incident_id": "01KGF13N88J78TFTW67BHP93TQ",
"status": "monitoring",
"updated_at": "2026-02-02T14:37:26Z"
},
{
"body": "Atlassian's status page continues to show the issue with Statuspage (\u003chttps://metastatuspage.com/incidents/ctw5xv6t643h\u003e). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ \"incident.io.\") \n\nWe'll continue to monitor this until the issue is resolved.",
"created_at": "2026-02-02T13:30:38Z",
"display_at": "2026-02-02T13:30:38Z",
"id": "01KGF8RM4KYC1BD1YEC2TWJM5Y",
"incident_id": "01KGF13N88J78TFTW67BHP93TQ",
"status": "monitoring",
"updated_at": "2026-02-02T13:30:38Z"
},
{
"body": "Atlassian's status page continues to show the issue with Statuspage (\u003chttps://metastatuspage.com/incidents/ctw5xv6t643h\u003e). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ \"incident.io.\") \n\nWe'll continue to monitor this until the issue is resolved.",
"created_at": "2026-02-02T12:30:14Z",
"display_at": "2026-02-02T12:30:14Z",
"id": "01KGF5A11WTDR6PZ6WGAZDGYBP",
"incident_id": "01KGF13N88J78TFTW67BHP93TQ",
"status": "monitoring",
"updated_at": "2026-02-02T12:30:14Z"
},
{
"body": "Atlassian's status page continues to show the issue with Statuspage (\u003chttps://metastatuspage.com/incidents/ctw5xv6t643h\u003e). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in incident.io. \n\nWe'll continue to monitor this until the issue is resolved.",
"created_at": "2026-02-02T11:37:08Z",
"display_at": "2026-02-02T11:37:08Z",
"id": "01KGF28SY96M0G26MR3PY8WHT6",
"incident_id": "01KGF13N88J78TFTW67BHP93TQ",
"status": "monitoring",
"updated_at": "2026-02-02T14:36:56Z"
},
{
"body": "We have identified increased error rates with our Atlassian Statuspage integration. Atlassian have acknowledged an issue on their side (\u003chttps://metastatuspage.com/incidents/ctw5xv6t643h\u003e). We'll continue to monitor this until the issue is resolved.",
"created_at": "2026-02-02T11:16:51Z",
"display_at": "2026-02-02T11:16:51Z",
"id": "01KGF13N88WVZ7B1P3YP4ZJH5A",
"incident_id": "01KGF13N88J78TFTW67BHP93TQ",
"status": "identified",
"updated_at": "2026-02-02T11:16:51Z"
}
],
"name": "Atlassian Statuspage integration degraded",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-02-02T16:56:25Z",
"status": "resolved",
"updated_at": "2026-03-11T17:56:20Z"
},
{
"created_at": "2026-01-12T15:36:15Z",
"id": "01KESDKHGT8XMTF0HYHNJBCQVC",
"impact": "minor",
"incident_updates": [
{
"body": "We've not seen any errors from Sentry since 15:35 UTC so we're closing this out. Please see Sentry's status page for any further details.",
"created_at": "2026-01-12T15:59:15Z",
"display_at": "2026-01-12T15:59:15Z",
"id": "01KESEXNWJ5Y6B63N3JY17NKQK",
"incident_id": "01KESDKHGT8XMTF0HYHNJBCQVC",
"status": "resolved",
"updated_at": "2026-01-12T15:59:15Z"
},
{
"body": "Sentry have acknowledged an issue on their side ([https://status.sentry.io/incidents/wpg3tnwnwctj](https://status.sentry.io/incidents/wpg3tnwnwctj \"https://status.sentry.io/incidents/wpg3tnwnwctj\")), and we're seeing alerts come through from them ok. We'll continue to monitor things before closing this out.",
"created_at": "2026-01-12T15:38:53Z",
"display_at": "2026-01-12T15:38:53Z",
"id": "01KESDRBV8XT2B3GBBVDZ2XDME",
"incident_id": "01KESDKHGT8XMTF0HYHNJBCQVC",
"status": "monitoring",
"updated_at": "2026-01-12T15:38:53Z"
},
{
"body": "We have identified increased error rates with our Sentry integration. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.",
"created_at": "2026-01-12T15:36:15Z",
"display_at": "2026-01-12T15:36:15Z",
"id": "01KESDKHGTH5313P1ZQSEX10PJ",
"incident_id": "01KESDKHGT8XMTF0HYHNJBCQVC",
"status": "identified",
"updated_at": "2026-01-12T15:36:15Z"
}
],
"name": "Sentry integration degraded",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2026-01-12T15:59:15Z",
"status": "resolved",
"updated_at": "2026-03-11T17:56:20Z"
},
{
"created_at": "2025-12-22T10:29:10Z",
"id": "01KD2SP5NKHRAJJ6Q7D05FN3NK",
"impact": "minor",
"incident_updates": [
{
"body": "We have managed to re-establish a connection to Sentry for almost all of the affected customers. If Sentry is still showing up as disconnected, you will need to remove the incident.io integration from the Sentry side, and then go through the reinstallation flow by opening incident.io and going to Settings → Integrations → Sentry.\n\nIf you do this, please note that Sentry will remove the \"Notify incident.io\" action from alert rules when you uninstall the integration. If that was the only action in the alert rule, the entire rule is disabled. You will therefore need to verify any alert rules after re-installing.",
"created_at": "2025-12-22T13:57:21Z",
"display_at": "2025-12-22T13:57:21Z",
"id": "01KD35KBX42QHVNQF4XEM3WZ3J",
"incident_id": "01KD2SP5NKHRAJJ6Q7D05FN3NK",
"status": "resolved",
"updated_at": "2025-12-22T13:57:21Z"
},
{
"body": "We have confirmed that we are able to restore these connections, and we are now in the process of restoring these. When this happens, you'll see that the Sentry integration no longer flags up as requiring reconnection. Once we have finished restoring access, we'll post another update here.",
"created_at": "2025-12-22T12:04:50Z",
"display_at": "2025-12-22T12:04:50Z",
"id": "01KD2Z5B3DZZXY427QGDYDZR9P",
"incident_id": "01KD2SP5NKHRAJJ6Q7D05FN3NK",
"status": "monitoring",
"updated_at": "2025-12-22T12:04:50Z"
},
{
"body": "We've verified a fix locally, and we're starting to roll this out in production now.",
"created_at": "2025-12-22T11:34:24Z",
"display_at": "2025-12-22T11:34:24Z",
"id": "01KD2XDKG4DX6M3YKXAX8XNDEZ",
"incident_id": "01KD2SP5NKHRAJJ6Q7D05FN3NK",
"status": "identified",
"updated_at": "2025-12-22T11:34:24Z"
},
{
"body": "We're currently testing the fix that will allow us to re-connect any disconnected Sentry integrations on behalf of customers, and will have another update on this in 30 minutes.",
"created_at": "2025-12-22T10:58:01Z",
"display_at": "2025-12-22T10:58:01Z",
"id": "01KD2VB07GYZ19G4E5V16W1MYH",
"incident_id": "01KD2SP5NKHRAJJ6Q7D05FN3NK",
"status": "identified",
"updated_at": "2025-12-22T10:58:01Z"
},
{
"body": "We have identified an increased rate of Sentry integrations becoming disconnected. Alert ingestion is unaffected. Please don't uninstall our application from Sentry: we are working to restore these connections on our side, and no action is currently required. We will provide an update in 30 minutes.",
"created_at": "2025-12-22T10:29:10Z",
"display_at": "2025-12-22T10:29:10Z",
"id": "01KD2SP5NKPWD04NQAS5YA7H3D",
"incident_id": "01KD2SP5NKHRAJJ6Q7D05FN3NK",
"status": "identified",
"updated_at": "2025-12-22T10:29:10Z"
}
],
"name": "Increased rate of disconnections from Sentry",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2025-12-22T13:57:21Z",
"status": "resolved",
"updated_at": "2026-03-11T17:56:20Z"
},
{
"created_at": "2025-12-15T10:31:07Z",
"id": "01KCGS0PV9GC15Z6RPXCVVCN8P",
"impact": "minor",
"incident_updates": [
{
"body": "The team have resolved this issue, and Insights are now syncing as expected.",
"created_at": "2025-12-15T14:41:54Z",
"display_at": "2025-12-15T14:41:54Z",
"id": "01KCH7BX8SP6F5MHPK0M0YVS9J",
"incident_id": "01KCGS0PV9GC15Z6RPXCVVCN8P",
"status": "resolved",
"updated_at": "2025-12-15T14:41:54Z"
},
{
"body": "We are aware of an issue that is causing delays updating data in Insights. The team are currently working on mitigating this, and we'll provide further updates soon.",
"created_at": "2025-12-15T11:49:21Z",
"display_at": "2025-12-15T11:49:21Z",
"id": "01KCGXFZ02HGPQY741Q8FDR6H1",
"incident_id": "01KCGS0PV9GC15Z6RPXCVVCN8P",
"status": "identified",
"updated_at": "2025-12-15T11:49:21Z"
},
{
"body": "We are aware of an issue that is causing delays updating data in Insights. The team are currently investigating, and we'll provide further updates soon.",
"created_at": "2025-12-15T10:31:07Z",
"display_at": "2025-12-15T10:31:07Z",
"id": "01KCGS0PV94BBMBN7K5H0XH8CP",
"incident_id": "01KCGS0PV9GC15Z6RPXCVVCN8P",
"status": "investigating",
"updated_at": "2025-12-15T10:31:07Z"
}
],
"name": "Delayed insights data",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2025-12-15T14:41:54Z",
"status": "resolved",
"updated_at": "2026-03-11T17:56:20Z"
},
{
"created_at": "2025-12-05T09:07:07Z",
"id": "01KBPW7QC585WYBZCVDECT590M",
"impact": "minor",
"incident_updates": [
{
"body": "[Cloudflare have resolved](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) the incident.\n\nWe've seen a recovery in system health - all integrations have returned to normal.",
"created_at": "2025-12-05T09:30:56Z",
"display_at": "2025-12-05T09:30:56Z",
"id": "01KBPXKAC22MQY3E011NJBNKK9",
"incident_id": "01KBPW7QC585WYBZCVDECT590M",
"status": "resolved",
"updated_at": "2025-12-05T09:30:56Z"
},
{
"body": "Cloudflare has implemented a [fix for the issue](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) and we've seen recovery.\n\nSAML sign ins are now successful, other integration health appears to be recovering.\n\nWe'll have more updates as and when things change.",
"created_at": "2025-12-05T09:19:58Z",
"display_at": "2025-12-05T09:19:58Z",
"id": "01KBPWZ82G86GBFNEKBC1JQC6Y",
"incident_id": "01KBPW7QC585WYBZCVDECT590M",
"status": "monitoring",
"updated_at": "2025-12-05T09:19:58Z"
},
{
"body": "We have identified increased error rates with a number of our platform integrations, these relate to an ongoing Cloudflare outage.\n\nThe list of impacted integrations includes: SAML sign-on, Zoom, Zendesk, Gitlab and Linear, but others may be experiencing degradation as well.\n\nOn-call notifications and our Slack and Microsoft Teams apps are unaffected.",
"created_at": "2025-12-05T09:07:07Z",
"display_at": "2025-12-05T09:07:07Z",
"id": "01KBPW7QC5X24HX59VSYFV2B6A",
"incident_id": "01KBPW7QC585WYBZCVDECT590M",
"status": "identified",
"updated_at": "2025-12-05T09:07:07Z"
}
],
"name": "Integration failures due to Cloudflare outage",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2025-12-05T09:30:56Z",
"status": "resolved",
"updated_at": "2026-03-11T17:56:20Z"
},
{
"created_at": "2025-11-29T11:33:46Z",
"id": "01KB7P7XMT3APYXV4QAJ9QWWQJ",
"impact": "minor",
"incident_updates": [
{
"body": "Sentry has resolved the incident.",
"created_at": "2025-11-29T15:20:51Z",
"display_at": "2025-11-29T15:20:51Z",
"id": "01KB837Q1PZVCHAF2ZZBY65QYW",
"incident_id": "01KB7P7XMT3APYXV4QAJ9QWWQJ",
"status": "resolved",
"updated_at": "2025-11-29T15:20:51Z"
},
{
"body": "Sentry have confirmed the recovery on [their status page](https://status.sentry.io/incidents/4w7y638y0zrh), and are investigating the root cause.\n\nWe have not seen the earlier errors return, and are continuing to monitor our integration's health.\n\nWe'll have more updates as and when things change.",
"created_at": "2025-11-29T13:42:16Z",
"display_at": "2025-11-29T13:42:16Z",
"id": "01KB7XK6NT48BTW20J03643R1J",
"incident_id": "01KB7P7XMT3APYXV4QAJ9QWWQJ",
"status": "monitoring",
"updated_at": "2025-11-29T13:42:16Z"
},
{
"body": "We've seen a recovery in error rates from Sentry.\n\n \n\nWe're continuing to monitor the recovery, and will post any updates as and when we see the situation change.\n\n\nSentry are tracking [this incident on their status page](https://status.sentry.io/incidents/4w7y638y0zrh).",
"created_at": "2025-11-29T12:29:13Z",
"display_at": "2025-11-29T12:29:13Z",
"id": "01KB7SDF2D95SZM56QY1BCB0KZ",
"incident_id": "01KB7P7XMT3APYXV4QAJ9QWWQJ",
"status": "monitoring",
"updated_at": "2025-11-29T12:29:13Z"
},
{
"body": "We're continuing to see degraded performance from Sentry.\n\nAlerts from Sentry are still being received, Sentry Issue Alerts may be missing some additional context, Sentry Metric Alerts are unaffected.\n\nThis incident is being tracked on [their status page](https://status.sentry.io/incidents/4w7y638y0zrh).",
"created_at": "2025-11-29T12:05:54Z",
"display_at": "2025-11-29T12:05:54Z",
"id": "01KB7R2RRTJRT08EZXHC30X2EX",
"incident_id": "01KB7P7XMT3APYXV4QAJ9QWWQJ",
"status": "identified",
"updated_at": "2025-11-29T12:05:54Z"
},
{
"body": "We have identified increased error rates with our Sentry integration. This is being tracked on [their status page](https://status.sentry.io/incidents/4w7y638y0zrh).\n\nAlerts from Sentry are still being received, but may be missing some additional context.",
"created_at": "2025-11-29T11:33:46Z",
"display_at": "2025-11-29T11:33:46Z",
"id": "01KB7P7XMTAA6BYETM1DJRKE92",
"incident_id": "01KB7P7XMT3APYXV4QAJ9QWWQJ",
"status": "identified",
"updated_at": "2025-11-29T11:33:46Z"
}
],
"name": "Elevated error rate from Sentry",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2025-11-29T15:20:51Z",
"status": "resolved",
"updated_at": "2026-03-11T17:56:20Z"
},
{
"created_at": "2025-11-20T11:47:29Z",
"id": "01KAGHEJEPHDWWXRQXTKN6JQ3H",
"impact": "minor",
"incident_updates": [
{
"body": "We have resolved the degraded performance affecting @incident chat.\n\nThis issue was caused by an overload from one of our AI model providers, which led to intermittent errors when using AI actions such as generating summaries or drafting updates. \\inc commands were unaffected during this time.\n\nWe have confirmed that the provider's issue has been resolved and all @incident chat features are now functioning normally.",
"created_at": "2025-11-20T12:14:33Z",
"display_at": "2025-11-20T12:14:33Z",
"id": "01KAGK04PBZ9V32GDG8N176EYT",
"incident_id": "01KAGHEJEPHDWWXRQXTKN6JQ3H",
"status": "resolved",
"updated_at": "2025-11-20T12:14:33Z"
},
{
"body": "We are experiencing degraded performance from some of our LLM model providers, causing error responses from @incident. /inc commands remain unaffected. More info on [Anthropic's status page](https://status.claude.com/incidents/xbbf1wq2dlz7 \"Anthropic's status page\")",
"created_at": "2025-11-20T11:47:29Z",
"display_at": "2025-11-20T11:47:29Z",
"id": "01KAGHEJEP3Z2K0C6H3QZZFWT2",
"incident_id": "01KAGHEJEPHDWWXRQXTKN6JQ3H",
"status": "identified",
"updated_at": "2025-11-20T12:15:05Z"
}
],
"name": "Degraded performance with @incident chat",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2025-11-20T12:14:33Z",
"status": "resolved",
"updated_at": "2026-03-11T17:56:20Z"
},
{
"created_at": "2025-11-18T12:18:09Z",
"id": "01KABED92SRXBA9RVE0HXK15S7",
"impact": "minor",
"incident_updates": [
{
"body": "Cloudflare have [confirmed](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7) that majority of impact has now resolved, and we’ve seen no impact on our systems over the last hour.",
"created_at": "2025-11-18T15:58:47Z",
"display_at": "2025-11-18T15:58:47Z",
"id": "01KABV19FXCBF4MJAHZZAA55A7",
"incident_id": "01KABED92SRXBA9RVE0HXK15S7",
"status": "resolved",
"updated_at": "2025-11-18T15:58:47Z"
},
{
"body": "Cloudflare have [confirmed](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7) that majority of impact has now resolved, and we’re seeing that Insights has recovered.\n\nWe’re continuing to monitor as a precaution.",
"created_at": "2025-11-18T15:02:46Z",
"display_at": "2025-11-18T15:02:46Z",
"id": "01KABQTQ251C445S5PSM1CT8YQ",
"incident_id": "01KABED92SRXBA9RVE0HXK15S7",
"status": "monitoring",
"updated_at": "2025-11-18T15:02:46Z"
},
{
"body": "We're continuing to monitor impact from an ongoing incident with Cloudflare, who have updated their status page [here](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7).\n\nWe’re no longer seeing any impact on the loading of status pages - we can confirm that intermittent impact was localized to Europe, for approximately 20 minutes between 13.38-13.47 UTC.\n\nThere are still intermittent errors loading Insights for some users. We're continuing to monitor the situation, and will keep providing updates.",
"created_at": "2025-11-18T14:38:28Z",
"display_at": "2025-11-18T14:38:28Z",
"id": "01KABPE6Q6CC5GDPSM6HJ68Y5W",
"incident_id": "01KABED92SRXBA9RVE0HXK15S7",
"status": "monitoring",
"updated_at": "2025-11-18T14:38:28Z"
},
{
"body": "We're continuing to monitor impact from an ongoing incident with Cloudflare, who have updated their status page [here](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7).\n\nWe're still seeing intermittent errors in Insights for some users, and some localized impact on status pages loading in Europe. We're continuing to monitor the situation, and will provide further updates soon.",
"created_at": "2025-11-18T13:57:29Z",
"display_at": "2025-11-18T13:57:29Z",
"id": "01KABM3624XV6HEXS527VFZXMP",
"incident_id": "01KABED92SRXBA9RVE0HXK15S7",
"status": "monitoring",
"updated_at": "2025-11-18T13:57:29Z"
},
{
"body": "We're continuing to monitor impact from an ongoing incident with Cloudflare, who have updated their status page [here](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7).\n\nWe're still seeing intermittent error rates for Insights for some users. We're continuing to monitor the situation, and will provide further updates soon.",
"created_at": "2025-11-18T13:10:19Z",
"display_at": "2025-11-18T13:10:19Z",
"id": "01KABHCSS6P5X9XJCVJQ0Y4YYF",
"incident_id": "01KABED92SRXBA9RVE0HXK15S7",
"status": "monitoring",
"updated_at": "2025-11-18T13:10:19Z"
},
{
"body": "We've identified an ongoing incident with Cloudflare, who have updated their status page [here](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7). We experienced brief, minor increase in dashboard latency due to an initial surge in traffic, but our systems recovered rapidly and latency is now back to baseline.\n\nInsights are still intermittently experiencing increased error rates for some users, depending on location. We're continuing to monitor the situation, and will provide further updates soon.",
"created_at": "2025-11-18T12:36:52Z",
"display_at": "2025-11-18T12:36:52Z",
"id": "01KABFFHVZGQ0RK3RBNZ15PTP4",
"incident_id": "01KABED92SRXBA9RVE0HXK15S7",
"status": "investigating",
"updated_at": "2025-11-18T12:36:52Z"
},
{
"body": "We are seeing latency increases in the dashboard and increased error rates for insights. Our team are investigating and we will share an update shortly.",
"created_at": "2025-11-18T12:18:09Z",
"display_at": "2025-11-18T12:18:09Z",
"id": "01KABED92S6815YBXE5STDT7DV",
"incident_id": "01KABED92SRXBA9RVE0HXK15S7",
"status": "investigating",
"updated_at": "2025-11-18T12:18:09Z"
}
],
"name": "Minor impact from Cloudflare outage",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2025-11-18T15:58:47Z",
"status": "resolved",
"updated_at": "2026-03-11T17:56:20Z"
},
{
"created_at": "2025-11-14T14:23:44Z",
"id": "01KA1C0BGBQAHWJ8BT81VF8Q18",
"impact": "none",
"incident_updates": [
{
"body": "Between 12:46 and 12:50 UTC, some requests to our web dashboard and API failed. Some interactions via Slack, Teams and the mobile app were also affected by this.\n\nCritical areas of our application were **unaffected**, including on-call alert notifications, alert ingestion flows, status pages, and background event processing.\n\nThe root cause of the failure was in the routing of traffic to application servers, within our internal load balancing infrastructure.\n\nWe're working to enhance our resilience to this issue in the future.",
"created_at": "2025-11-14T14:23:44Z",
"display_at": "2025-11-14T12:46:00Z",
"id": "01KA1C0BGB11D8P530MKRENAY0",
"incident_id": "01KA1C0BGBQAHWJ8BT81VF8Q18",
"status": "resolved",
"updated_at": "2025-11-14T14:23:44Z"
}
],
"name": "Web dashboard and API unavailable",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2025-11-14T12:46:00Z",
"status": "resolved",
"updated_at": "2026-03-11T17:56:19Z"
},
{
"created_at": "2025-11-07T02:24:30Z",
"id": "01K9E22CF0HPVYVDQX11K20GTJ",
"impact": "minor",
"incident_updates": [
{
"body": "Slack have confirmed on their [status page](https://slack-status.com/2025-11-06) that the issue has been resolved, and we have confirmed that Slack errors and latency are back to expected levels.\n\nIf you are still encountering issues, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux).\n\nWe'll keep monitoring for any further issues, but we're now marking this incident as resolved. ",
"created_at": "2025-11-07T07:25:47Z",
"display_at": "2025-11-07T07:25:47Z",
"id": "01K9EKA2171ZEQDG4DJH6CWEEQ",
"incident_id": "01K9E22CF0HPVYVDQX11K20GTJ",
"status": "resolved",
"updated_at": "2025-11-07T07:25:47Z"
},
{
"body": "We’re monitoring an ongoing incident affecting Slack. The impact appears to be mostly resolved, but we’ll continue to monitor until it’s fully stable. You can follow their updates [here](https://slack-status.com/2025-11/66f5fbbfdb8d6f73).",
"created_at": "2025-11-07T03:10:24Z",
"display_at": "2025-11-07T03:10:24Z",
"id": "01K9E4PDDYWR4NS085D33J76B7",
"incident_id": "01K9E22CF0HPVYVDQX11K20GTJ",
"status": "identified",
"updated_at": "2025-11-07T03:10:24Z"
},
{
"body": "We have identified increased error rates with our slack integration. \n\nWe believe latency and error rates have returned to normal and are monitoring any further changes.\n\nWe will update with more information shortly as we learn more",
"created_at": "2025-11-07T02:24:30Z",
"display_at": "2025-11-07T02:24:30Z",
"id": "01K9E22CF0NW60MQ0PPT7EVHB9",
"incident_id": "01K9E22CF0HPVYVDQX11K20GTJ",
"status": "identified",
"updated_at": "2025-11-07T02:24:30Z"
}
],
"name": "Slack integration degraded performance",
"page_id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"resolved_at": "2025-11-07T07:25:47Z",
"status": "resolved",
"updated_at": "2026-03-11T17:56:19Z"
}
],
"page": {
"id": "01HEJCK9PNPA0K8TNAZZ1DWN06",
"name": "incident.io",
"updated_at": "2026-08-28T18:41:06Z",
"url": "https://status.incident.io/"
}
}