Quorum incident

Increased Error Rates and Latency

Major Resolved View vendor source →

Quorum experienced a major incident on October 20, 2025 affecting Quorum Platform (WebUI), lasting 8h 6m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 04:05 PM UTC
Resolved
Oct 21, 2025, 12:12 AM UTC
Duration
8h 6m
Detected by Pingoru
Oct 20, 2025, 04:05 PM UTC

Affected components

Quorum Platform (WebUI)

Update timeline

  1. investigating Oct 20, 2025, 04:05 PM UTC

    We’re currently experiencing increased error rates and latency across multiple Quorum services due to an ongoing AWS service disruption in the US-EAST-1 region. We sincerely apologize for the delay in posting this update—our status page was also affected by the same regional AWS outage, which temporarily limited our ability to communicate in real time. Thank you for your patience as we work through this issue. We’ll continue to provide updates here as services recover and stabilize.

  2. identified Oct 20, 2025, 04:40 PM UTC

    We are still experiencing elevated error rates and latency due to the ongoing AWS service disruption in the US-EAST-1 region. Our team continues to monitor the situation closely while we wait for our service provider to complete their recovery efforts. We’ll share another update as soon as we have more information. Thank you for your continued patience.

  3. identified Oct 20, 2025, 05:13 PM UTC

    We are still experiencing elevated error rates and latency due to the ongoing AWS service disruption in the US-EAST-1 region. Our team continues to monitor the situation closely while we wait for our service provider to complete their recovery efforts. We’ll share another update as soon as we have more information. Thank you for your continued patience.

  4. identified Oct 20, 2025, 05:53 PM UTC

    We are still experiencing elevated error rates and latency due to the ongoing AWS service disruption in the US-EAST-1 region. Our team continues to monitor the situation closely while we wait for our service provider to complete their recovery efforts. We’ll share another update as soon as we have more information. Thank you for your continued patience.

  5. identified Oct 20, 2025, 06:31 PM UTC

    We are still experiencing elevated error rates and latency due to the ongoing AWS service disruption in the US-EAST-1 region. Our team continues to monitor the situation closely while we wait for our service provider to complete their recovery efforts. We’ll share another update as soon as we have more information. Thank you for your continued patience.

  6. identified Oct 20, 2025, 07:10 PM UTC

    We’re beginning to see a reduction in errors and latency; however, elevated levels may still persist due to the ongoing AWS service disruption in the US-EAST-1 region. Our team continues to actively monitor the situation while we await full recovery from our service provider. We’ll share another update as soon as more information becomes available. Thank you for your continued patience and understanding.

  7. identified Oct 20, 2025, 07:38 PM UTC

    Services are beginning to come back online, and we’re seeing a reduction in errors and latency. However, elevated levels may still persist due to the ongoing AWS service disruption in the US-EAST-1 region. Our team is actively monitoring the situation as we await full recovery from our service provider. We’ll provide another update as soon as more information becomes available. Thank you for your continued patience and understanding.

  8. identified Oct 20, 2025, 08:21 PM UTC

    Services continue to come back online, and many are now fully operational. We’re seeing a reduction in errors and latency; however, some elevated levels may still persist due to the ongoing AWS service disruption in the US-EAST-1 region. Our team is actively monitoring the situation as we await full recovery from our service provider. We’ll share another update as soon as more information becomes available. Thank you for your continued patience and understanding.

  9. identified Oct 20, 2025, 08:56 PM UTC

    Services continue to come back online, and many are now fully operational. We’re seeing a reduction in errors and latency; however, some elevated levels may still persist due to the ongoing AWS service disruption in the US-EAST-1 region. Our team is actively monitoring the situation as we await full recovery from our service provider. We’ll share another update as soon as more information becomes available. Thank you for your continued patience and understanding.

  10. monitoring Oct 20, 2025, 09:09 PM UTC

    We’re pleased to report that AWS has restored most of its functionality following the recent service disruptions. Our monitoring indicates that all primary Quorum services are now operating normally, with significant improvements in response times and overall reliability. While systems have stabilized, our team continues to actively monitor performance to ensure ongoing stability. We sincerely appreciate your patience throughout the disruption and will continue to keep you informed of any further developments. Thank you for your continued understanding and support.

  11. monitoring Oct 20, 2025, 10:01 PM UTC

    We are continuing to monitor for any further issues.

  12. resolved Oct 21, 2025, 12:12 AM UTC

    This incident has been resolved.

  13. postmortem Oct 31, 2025, 07:16 PM UTC

    ## Post-Incident Summary: AWS US-East-1 Regional Outage \(October 20, 2025\) On October 20, 2025, a widely publicized AWS outage in the US-East-1 region caused major disruptions across numerous cloud services globally. During this event, Quorum and Phone2Action experienced database connectivity issues and intermittent downtime beginning around 2:50 AM ET, resulting in core application impact throughout the day. Quorum and Phone2Action experienced database connectivity issues and intermittent downtime beginning around 2:50 AM ET, resulting in core application impact throughout the day. Our engineering team detected the issue before AWS’s public notice and took precautionary measures to protect system integrity, including pausing production deployments until stability was confirmed. Once AWS services recovered, all Quorum systems were fully operational by 4:53 PM ET. While this incident originated within AWS infrastructure, our primary infrastructure-as-a-service provider, we are implementing additional improvements on our side — including enhanced service health monitoring, deployment safeguards, and incident response processes — to further strengthen resilience and response time during large-scale provider events. All Quorum and Phone2Action services are now fully operational. We appreciate your patience during this industry-wide outage and thank you for your continued trust.