# Service disruption on October 20, 2025

DevFeed: [Service disruption on October 20, 2025](<https://devfeed.tech/articles/service-disruption-on-october-20-2025-11984.md>)

Original publisher: [Read original article](<https://incident.io/blog/service-disruption-october-20th-2025>)

Author: Pete Hamilton

Published: 2025-10-22T19:00:00Z

Content type: article

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Incident response](<https://devfeed.tech/topics/incident-response.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [site-reliability-engineering](<https://devfeed.tech/topics/site-reliability-engineering.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [ai](<https://devfeed.tech/tags/ai.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [outage](<https://devfeed.tech/tags/outage.md>), [platform](<https://devfeed.tech/tags/platform.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>)

## AI overview

This article examines incident.io's response to the major AWS outage on October 20, 2025. Although most of the platform remained available through multi-region Google Cloud hosting, AWS-dependent services including on-call notifications, SAML authentication, and the Scribe incident note taker were affected. It describes the resulting load, monitoring activity, response challenges, and changes that improved resilience, including dynamically moving Scribe workloads to another AWS region.

## Source excerpt

During the October 20th AWS outage, our platform handled 12,500 hours of incident response and 4.5M requests/hour. Here's how we diagnosed cascading failures in real-time and deployed fixes within hours to build greater resilience.