incident.io

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-02 22:33 UTC

   Some customers on Slack Enterprise Grid who sign in with Slack are seeing Slack-originating errors when logging in. We've raised this with Slack and are monitoring for a fix. Customers using SAML sign-in aren't affected. Alert ingestion and our On-call product's paging...

2. resolved 2026-10-02 23:47 UTC

   This incident has been resolved. Login via Slack is operating normally again, and no further action is required.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-20 14:42 UTC

   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.

2. identified 2026-08-20 15:31 UTC

   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.

3. resolved 2026-08-20 16:31 UTC

   Latency has now returned to normal. Between 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.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-18 11:24 UTC

   We've identified an issue listing alerts. Regular alerting and paging is unaffected.

2. resolved 2026-08-18 11:37 UTC

   We've now rolled back and listing alerts is working normally again.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-03 15:56 UTC

   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.

2. resolved 2026-08-03 17:04 UTC

   Opsgenie webhook delivery returned to normal at around 17:48 BST

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-01 00:08 UTC

   We detected increased error rates with some AI features.

2. resolved 2026-08-01 02:45 UTC

   Between around 00:00 and 02:44 UTC, some AI features returned increased error rates. We are now seeing full recovery.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-16 08:32 UTC

   We're aware of issues affecting some customers logging in using SAML - we're investigating and will provide an update shortly.

2. identified 2026-07-16 09:12 UTC

   This issue remains ongoing and we're working on a resolution. All 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.

3. monitoring 2026-07-16 09:27 UTC

   SAML logins are now working with increased latency. We'll continue to monitor until fully recovered. All other functionality remains unaffected.

4. monitoring 2026-07-16 10:16 UTC

   We're continuing to see elevated errors and latency with SAML logins. All other functionality remains unaffected.

5. monitoring 2026-07-16 10:29 UTC

   SAML logins are now performing as normal. We'll continue to monitor for any further issues.

6. resolved 2026-07-16 10:54 UTC

   SAML login has continued to perform as normal.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-06-23 19:45 UTC

   We have identified increased latency and timeouts affecting some requests to our dashboard. Issues seem to be transient, and we recommend refreshing. We are continuing to investigate.

2. monitoring 2026-06-23 19:55 UTC

   Latency and error rates have returned to normal. We're continuing to monitor for any further issues.

3. resolved 2026-06-23 20:25 UTC

   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. Latency and error rates are back to...

4. resolved 2026-06-25 11:51 UTC

   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. The cause of these elevated errors was due to...

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-27 22:42 UTC

   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.

2. identified 2026-05-27 23:02 UTC

   Slack have acknowledged the incident on their side. You can follow their status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f).

3. monitoring 2026-05-27 23:21 UTC

   Error rates and latency on Slack operations have returned to normal, and the integration has recovered. You can follow updates on Slack's status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f).

4. monitoring 2026-05-28 00:19 UTC

   We are continuing to monitor Slack as it continues to recover, and are no longer seeing any direct impact on our Slack app You can follow updates on Slack's status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f "here").

5. monitoring 2026-05-28 02:31 UTC

   We are continuing to monitor Slack as it recovers. We are not seeing any direct impact on our Slack app. You can follow updates on Slack’s status page [here](https://slack-status.com/2026-05/46d9d5d41fbedd9f "here").

6. resolved 2026-05-28 06:29 UTC

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

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-14 14:08 UTC

   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.

2. identified 2026-05-14 14:12 UTC

   We've confirmed the issue is relating to errors being returned by Slack. This is affecting a number of features of our integration, including: • Creating incident channels • Sending messages • Syncing Slack user groups Our web dashboard continues to be available and Scribe is...

3. monitoring 2026-05-14 14:41 UTC

   Slack have acknowledged the incident on their side. You can follow their status page [here](https://slack-status.com/2026-05/fe557ca05fdb64fa).

4. monitoring 2026-05-14 15:15 UTC

   We're continuing to monitor the situation - Slack have posted an update on their status page to confirm that they're working on it.

5. resolved 2026-05-14 15:45 UTC

   The issue has been resolved on Slack's side and we've confirmed that things look normal on our side too.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-07 07:12 UTC

   The web dashboard is unavailable due to a JavaScript deployment issue.

2. resolved 2026-05-07 07:25 UTC

   The website is now up and working as normal.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-04-27 23:58 UTC

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

2. resolved 2026-04-28 00:14 UTC

   Webhooks appear to arriving as normal again, so you should no longer see any delays.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-09 07:33 UTC

   We have identified increased error rates with our Atlassian Statuspage integration. Atlassian have published this to their status page [here](https://metastatuspage.com/incidents/94fwk40f4z15).

2. resolved 2026-04-09 07:55 UTC

   Error rates have returned to normal levels.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-03-24 16:30 UTC

   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.

2. monitoring 2026-03-24 17:27 UTC

   We have identified increased error rates coming from Microsoft Teams that are causing delays in sending messages to Teams channels and DMs. We'll continue to monitor the situation and we will update with more information shortly as we learn more. We will provide the next update...

3. monitoring 2026-03-24 18:33 UTC

   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. We are monitoring the situation and will provide an update by 1930 UTC.

4. monitoring 2026-03-24 19:30 UTC

   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. We are continuing to monitor to ensure performance remains as expected, and we will...

5. resolved 2026-03-24 20:52 UTC

   We are no longer seeing elevated latency and error rates from Microsoft Teams.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-03-24 15:31 UTC

   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.

2. monitoring 2026-03-24 15:33 UTC

   The issues were isolated to one region and we have performed a failover to a secondary region, restoring Scribe for all customers. You may need to ask Scribe to rejoin your call. We'll continue to monitor the situation and are working closely with the upstream provider while...

3. monitoring 2026-03-24 16:18 UTC

   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. We'll continue to monitor the situation and are working closely with the upstream provider while they resolve the issue.

4. resolved 2026-03-24 17:02 UTC

   We continue to use the failover region, and Scribe performance has returned to expected levels.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-13 14:19 UTC

   We are currently investigating reports that users are unable to login using Slack.

2. identified 2026-03-13 14:53 UTC

   Users in some Slack workspaces are unable to sign in with Slack. We have escalated this issue to Slack. Signing in with SAML and Microsoft Teams is not affected.

3. monitoring 2026-03-13 15:54 UTC

   Slack have rolled back a change which caused this issue, and we have confirmed recovery. Please reach out to support if you're still experiencing any issues signing in with Slack.

4. resolved 2026-03-13 16:40 UTC

   Slack have confirmed that the issue has been fully resolved, and affected customers have verified that they can log in successfully.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-03-12 13:20 UTC

   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. This appears to...

2. resolved 2026-03-12 14:27 UTC

   Traffic appears to be back to normal levels now.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-02-02 11:16 UTC

   We have identified increased error rates with our Atlassian Statuspage integration. Atlassian have acknowledged an issue on their side ( ). We'll continue to monitor this until the issue is resolved.

2. monitoring 2026-02-02 11:37 UTC

   Atlassian's status page continues to show the issue with Statuspage ( ). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in incident.io. We'll continue to monitor this until the issue is resolved.

3. monitoring 2026-02-02 12:30 UTC

   Atlassian's status page continues to show the issue with Statuspage ( ). 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.") We'll continue to monitor this...

4. monitoring 2026-02-02 13:30 UTC

   Atlassian's status page continues to show the issue with Statuspage ( ). 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.") We'll continue to monitor this...

5. monitoring 2026-02-02 14:37 UTC

   Atlassian's status page continues to show the issue with Statuspage ( ). 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.") We'll continue to monitor this...

6. monitoring 2026-02-02 15:41 UTC

   Atlassian's status page continues to show the issue with Statuspage ( ). 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.") We'll continue to monitor this...

7. monitoring 2026-02-02 16:06 UTC

   Atlassian's status page now reports that they are rolling out a fix ( ). In 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.") We continue to...

8. resolved 2026-02-02 16:56 UTC

   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.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-01-12 15:36 UTC

   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.

2. monitoring 2026-01-12 15:38 UTC

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

3. resolved 2026-01-12 15:59 UTC

   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.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-22 10:29 UTC

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

2. identified 2025-12-22 10:58 UTC

   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.

3. identified 2025-12-22 11:34 UTC

   We've verified a fix locally, and we're starting to roll this out in production now.

4. monitoring 2025-12-22 12:04 UTC

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

5. resolved 2025-12-22 13:57 UTC

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

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-15 10:31 UTC

   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.

2. identified 2025-12-15 11:49 UTC

   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.

3. resolved 2025-12-15 14:41 UTC

   The team have resolved this issue, and Insights are now syncing as expected.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-12-05 09:07 UTC

   We have identified increased error rates with a number of our platform integrations, these relate to an ongoing Cloudflare outage. The list of impacted integrations includes: SAML sign-on, Zoom, Zendesk, Gitlab and Linear, but others may be experiencing degradation as well....

2. monitoring 2025-12-05 09:19 UTC

   Cloudflare has implemented a [fix for the issue](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) and we've seen recovery. SAML sign ins are now successful, other integration health appears to be recovering. We'll have more updates as and when things change.

3. resolved 2025-12-05 09:30 UTC

   [Cloudflare have resolved](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) the incident. We've seen a recovery in system health - all integrations have returned to normal.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-29 11:33 UTC

   We have identified increased error rates with our Sentry integration. This is being tracked on [their status page](https://status.sentry.io/incidents/4w7y638y0zrh). Alerts from Sentry are still being received, but may be missing some additional context.

2. identified 2025-11-29 12:05 UTC

   We're continuing to see degraded performance from Sentry. Alerts from Sentry are still being received, Sentry Issue Alerts may be missing some additional context, Sentry Metric Alerts are unaffected. This incident is being tracked on [their status...

3. monitoring 2025-11-29 12:29 UTC

   We've seen a recovery in error rates from Sentry. We're continuing to monitor the recovery, and will post any updates as and when we see the situation change. Sentry are tracking [this incident on their status page](https://status.sentry.io/incidents/4w7y638y0zrh).

4. monitoring 2025-11-29 13:42 UTC

   Sentry have confirmed the recovery on [their status page](https://status.sentry.io/incidents/4w7y638y0zrh), and are investigating the root cause. We have not seen the earlier errors return, and are continuing to monitor our integration's health. We'll have more updates as and...

5. resolved 2025-11-29 15:20 UTC

   Sentry has resolved the incident.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. identified 2025-11-20 11:47 UTC

   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")

2. resolved 2025-11-20 12:14 UTC

   We have resolved the degraded performance affecting @incident chat. This 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...

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 12:18 UTC

   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.

2. investigating 2025-11-18 12:36 UTC

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

3. monitoring 2025-11-18 13:10 UTC

   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). We're still seeing intermittent error rates for Insights for some users. We're continuing to monitor...

4. monitoring 2025-11-18 13:57 UTC

   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). We're still seeing intermittent errors in Insights for some users, and some localized impact on status...

5. monitoring 2025-11-18 14:38 UTC

   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). We’re no longer seeing any impact on the loading of status pages - we can confirm that intermittent...

6. monitoring 2025-11-18 15:02 UTC

   Cloudflare have [confirmed](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7) that majority of impact has now resolved, and we’re seeing that Insights has recovered. We’re continuing to monitor as a precaution.

7. resolved 2025-11-18 15:58 UTC

   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.

Excerpts are shortened. Read the full incident on incident.io's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-11-14 12:46 UTC

   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. Critical areas of our application were **unaffected**, including on-call alert notifications, alert ingestion flows,...

Excerpts are shortened. Read the full incident on incident.io's status page.