Quorum Outage History

Started Nov 02, 2026, 07:19 PM UTC· resolved Nov 03, 2026, 09:14 AM UTC

1. investigating Nov 02, 2026, 07:19 PM UTC

   We are currently experiencing a service disruption impacting the Quorum Platform and several key features, including emails, API access, and campaigns. Our team is actively investigating the root cause and working to implement a solution. All users and systems are currently affected. We will share another update within the next 30 minutes.

2. identified Nov 02, 2026, 07:30 PM UTC

   We have identified the root cause of the issue affecting multiple Quorum features and are actively working on implementing a fix. While we work on the resolution, some features may still be impacted. We will share another update in 30 minutes.

3. monitoring Nov 02, 2026, 07:53 PM UTC

   The issue impacting several Quorum features has been resolved, and all systems are now operating normally. Our team will continue to monitor the situation closely to ensure stability.

4. monitoring Nov 02, 2026, 07:54 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Nov 03, 2026, 09:14 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 07:56 AM UTC· resolved Sep 16, 2026, 08:28 AM UTC

1. identified Sep 16, 2026, 07:56 AM UTC

   We have identified the root cause of the issue affecting multiple Quorum features and are actively working on implementing a fix. While we work on the resolution, some features may still be impacted. We will share another update in 30 minutes.

2. resolved Sep 16, 2026, 08:28 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 13, 2026, 04:49 PM UTC· resolved Aug 13, 2026, 07:30 PM UTC

1. investigating Aug 13, 2026, 04:49 PM UTC

   We are currently investigating an increased rate of API errors across the platform. Our team is working to identify the root cause and restore full functionality. We will send an additional update in 30 minutes.

2. identified Aug 13, 2026, 05:24 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Aug 13, 2026, 05:24 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Aug 13, 2026, 07:30 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Aug 13, 2026, 07:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 05, 2026, 05:20 PM UTC· resolved Aug 17, 2026, 06:21 PM UTC

1. investigating Aug 05, 2026, 05:20 PM UTC

   We are currently experiencing a delay in processing new media content due to an issue with our media ingestion pipeline. Our team is actively investigating and working to restore normal service. What this means for you: Media alerts are delayed. You will not receive alerts for coverage published during this period until processing resumes. News Search, Article Feeds, and Media Dashboards will only display content through August 4, 3:20 PM ET. Article counts and trend metrics may appear unchanged during this time. What is not affected: No data has been lost. All previously ingested articles remain fully available and searchable. All other Quorum products and services are operating normally. We will provide another update as soon as we have additional information or a resolution.

2. identified Aug 05, 2026, 06:03 PM UTC

   We have identified that the issue is with our third-party media provider and are actively working with them to restore service as quickly as possible. Media alerts remain delayed, and News Search, Article Feeds, and Media Dashboards continue to display content only through August 4, 3:20 PM ET. Once service is restored, delayed articles will be processed and alerts will be sent automatically. No data has been lost, and all previously ingested articles remain fully available and searchable. All other Quorum products and services continue to operate normally. We will continue to work closely with our vendor and provide another update as soon as more information becomes available.

3. identified Aug 05, 2026, 06:26 PM UTC

   We continue to work closely with our third-party media provider and are actively monitoring the restoration of service. The impact remains limited to news article ingestion for Media Monitoring. News Search, Article Feeds, Media Dashboards, and news article alerts continue to experience delays while the provider restores normal processing. Social media monitoring is not affected. Twitter/X and Facebook alerts are operating normally and continue to process and deliver content as expected. No data has been lost. Once the vendor has fully restored service, delayed news articles will be processed and alerts will be delivered automatically. We will continue to monitor the situation and provide additional updates as more information becomes available.

4. identified Aug 05, 2026, 08:26 PM UTC

   We continue to work closely with our third-party media provider to restore service. Their engineering team remains actively engaged in resolving the issue, and we are monitoring progress and maintaining regular communication with them. The impact remains limited to news article ingestion for Media Monitoring. News Search, Article Feeds, Media Dashboards, and news article alerts continue to experience delays. Twitter/X and Facebook monitoring are not affected and continue to operate normally. No data has been lost. Once our vendor restores service, delayed news articles will be processed and alerts will be delivered automatically. We will provide another update as soon as additional information becomes available.

5. identified Aug 06, 2026, 11:59 AM UTC

   We continue to work closely with our third-party media provider to restore service. Their engineering team remains actively engaged in resolving the issue, and we are monitoring progress and maintaining regular communication with them. The impact remains limited to news article ingestion for Media Monitoring. News Search, Article Feeds, Media Dashboards, and news article alerts continue to experience delays. Twitter/X and Facebook monitoring are not affected and continue to operate normally. No data has been lost. Once our vendor restores service, delayed news articles will be processed and alerts will be delivered automatically. We will provide another update as soon as additional information becomes available.

6. identified Aug 06, 2026, 03:43 PM UTC

   We continue to work closely with our third-party media provider, who has informed us that they expect to restore service by Friday afternoon. The impact remains limited to news article ingestion for Media Monitoring. News Search, Article Feeds, Media Dashboards, and news article alerts continue to experience delays. Twitter/X and Facebook monitoring are not affected and continue to operate normally. No data has been lost. Once service is restored, delayed news articles will be processed and alerts will be delivered automatically. We will continue to monitor the situation closely and provide another update as more information becomes available.

7. identified Aug 07, 2026, 08:05 PM UTC

   We continue to work closely with our third-party media provider. Their team will be working throughout the weekend to address the issue and is hopeful that service can be restored this weekend. The impact remains limited to news article ingestion for Media Monitoring. Twitter/X and Facebook monitoring are not affected and continue to operate normally. We will continue to monitor the situation closely and provide another update as soon as we have additional information.

8. monitoring Aug 11, 2026, 11:57 AM UTC

   Our service provider has informed us that the underlying issue has been resolved. We have verified the data flow on our side and confirmed that we are successfully receiving new data. We are continuing to restore data that was delayed during the incident. The full restoration process will take several days to complete. Service has been restored, and we will continue to closely monitor the data flow and restoration process.

9. monitoring Aug 13, 2026, 03:00 PM UTC

   Status Update The underlying service issue has been resolved, and we have confirmed that new data is flowing normally again. We are continuing to monitor the data flow as previously delayed content is being restored. Based on recent ingestion volumes, the backfill process is actively progressing and is expected to continue over the next several days. Service has been restored, and we will continue to monitor the restoration process and provide another update as additional information becomes available.

10. resolved Aug 17, 2026, 06:21 PM UTC

    The issue has been resolved, and the data backfill has completed. According to our service provider, a small amount of content may not be recoverable if it was removed or moved from the original source while the service was unavailable. We are marking this incident as resolved and will continue to monitor the system.

Read the full incident report →

Started Jun 22, 2026, 02:00 PM UTC· resolved Jun 22, 2026, 05:37 PM UTC

1. investigating Jun 22, 2026, 02:00 PM UTC

   We are currently investigating an issue with a third-party email delivery provider that is impacting outbound email delivery. Affected messages are being safely queued and have not been lost. Our team is actively working with the vendor to identify the root cause and restore normal delivery as quickly as possible. We will provide additional updates as more information becomes available.

2. identified Jun 22, 2026, 02:32 PM UTC

   Our team has identified the issue and is actively working with our third-party email service provider to restore normal outbound email delivery. Messages continue to be safely queued and are not being lost. We are closely monitoring the situation and will provide another update as soon as we have additional information from the provider or a confirmed resolution timeline.

3. identified Jun 22, 2026, 03:03 PM UTC

   We continue to work closely with our third-party email service provider to investigate and resolve the issue impacting outbound email delivery. Affected messages remain safely queued and will be processed once service is fully restored. We appreciate your patience and will provide another update as soon as we have additional information or a confirmed resolution timeline.

4. identified Jun 22, 2026, 03:38 PM UTC

   Our team continues to work closely with our third-party email service provider to resolve the issue impacting outbound email delivery. Affected emails continue to be safely queued and are not being lost. Once service is restored, queued messages will be processed automatically. We will share another update as soon as additional information becomes available.

5. monitoring Jun 22, 2026, 03:56 PM UTC

   The issue with our third-party email service provider has been resolved, and outbound email delivery has resumed. Messages are now being successfully processed and delivered. We are continuing to closely monitor the system as the backlog of queued messages is processed to ensure delivery returns to normal levels. At this time, no messages have been lost. We appreciate your patience while we worked with our service provider to resolve this issue.

6. resolved Jun 22, 2026, 05:37 PM UTC

   The backlog of queued messages has been fully processed, and outbound email delivery has returned to normal operation. We have continued to monitor the system following the resolution of the third-party provider issue and have confirmed that message delivery is functioning as expected. With all queued messages delivered and no further impact observed, we are closing this incident. Thank you for your patience while we worked with our service provider to resolve the issue.

Read the full incident report →

Started Mar 30, 2026, 07:35 PM UTC· resolved Mar 30, 2026, 07:59 PM UTC

1. investigating Mar 30, 2026, 07:35 PM UTC

   We are currently investigating an increased rate of API errors across the platform. Our team is working to identify the root cause and restore full functionality. We will send an additional update in 30 minutes.

2. monitoring Mar 30, 2026, 07:46 PM UTC

   The issue causing elevated API errors has been resolved, and API services are now operating normally. Our team will continue to monitor performance closely to ensure stability.

3. resolved Mar 30, 2026, 07:59 PM UTC

   The issue that was causing elevated API errors has been fully resolved. All API services are functioning as expected.

Read the full incident report →

Started Nov 19, 2025, 06:14 PM UTC· resolved Nov 20, 2025, 01:41 AM UTC

1. investigating Nov 19, 2025, 06:14 PM UTC

   We are currently experiencing degraded performance on Quorum Search Pages. Our team is actively investigating the issue and will provide updates as soon as more information is available.

2. identified Nov 19, 2025, 06:22 PM UTC

   We’ve identified the issue and are actively restoring the affected service. We’ll provide another update within the next 30 minutes.

3. monitoring Nov 19, 2025, 06:41 PM UTC

   A fix has been implemented and we are monitoring the results.

4. investigating Nov 19, 2025, 08:15 PM UTC

   We are currently experiencing degraded performance on Quorum Search Pages. Our team is actively investigating the issue and will provide updates as soon as more information is available.

5. monitoring Nov 19, 2025, 08:33 PM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Nov 20, 2025, 01:41 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 19, 2025, 04:35 PM UTC· resolved Nov 19, 2025, 05:13 PM UTC

1. investigating Nov 19, 2025, 04:35 PM UTC

   We are currently experiencing degraded performance on Quorum Search Pages. Our team is actively investigating the issue and will provide updates as soon as more information is available.

2. investigating Nov 19, 2025, 04:48 PM UTC

   We’ve identified the issue and are actively restoring the affected service. We’ll provide another update within the next 30 minutes.

3. monitoring Nov 19, 2025, 04:57 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Nov 19, 2025, 05:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 02:20 PM UTC· resolved Nov 18, 2025, 03:59 PM UTC

1. investigating Nov 18, 2025, 02:20 PM UTC

   We are currently experiencing a degraded service for our AI Tracking Board functionalities. This degradation is due to an ongoing outage with our third-party service provider. Our teams are actively monitoring the provider's status and working to ensure service restoration as soon as the upstream issue is resolved.

2. monitoring Nov 18, 2025, 02:54 PM UTC

   The issue causing the degraded service for our AI Tracking Board has been resolved, and we are now actively monitoring the functionality to ensure stability.

3. resolved Nov 18, 2025, 03:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 12:08 PM UTC· resolved Nov 18, 2025, 02:55 PM UTC

1. investigating Nov 18, 2025, 12:08 PM UTC

   We are currently experiencing a service disruption impacting the Quorum Platform and several key features, including emails, API access, and campaigns. Our team is actively investigating the root cause and working to implement a solution. All users and systems are currently affected. We will share another update within the next 30 minutes.

2. identified Nov 18, 2025, 12:15 PM UTC

   We have identified the root cause of the issue affecting multiple features. The problem is on 3rd party provider side. We will share another update in 30 minutes.

3. monitoring Nov 18, 2025, 12:22 PM UTC

   The issue impacting several Quorum features has been resolved, and all systems are now operating normally. Our team will continue to monitor the situation closely to ensure stability.

4. resolved Nov 18, 2025, 02:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 12, 2025, 05:19 PM UTC· resolved Nov 12, 2025, 05:55 PM UTC

1. investigating Nov 12, 2025, 05:19 PM UTC

   We are currently experiencing degraded performance on Quorum Pages. Our team is actively investigating the issue and will provide updates as soon as more information is available.

2. identified Nov 12, 2025, 05:29 PM UTC

   We have identified the issue and are in the process of recovering the impacted service. We’ll share another update once full functionality is restored.

3. monitoring Nov 12, 2025, 05:35 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Nov 12, 2025, 05:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 05, 2025, 10:03 PM UTC· resolved Nov 06, 2025, 12:52 AM UTC

1. investigating Nov 05, 2025, 10:03 PM UTC

   We are currently experiencing degraded performance on Quorum Pages. Our team is actively investigating the issue and will provide updates as soon as more information is available.

2. identified Nov 05, 2025, 10:04 PM UTC

   We have identified the issue and are in the process of recovering the impacted service. We’ll share another update once full functionality is restored.

3. monitoring Nov 05, 2025, 11:04 PM UTC

   The issue has been resolved, and the system is now operating normally. We’re continuing to monitor to ensure full stability.

4. resolved Nov 06, 2025, 12:52 AM UTC

   The incident has been resolved.

5. postmortem Nov 13, 2025, 03:00 PM UTC

   # **Post-Incident Summary** On October 27, 2025, Quorum experienced a period of degraded performance and intermittent downtime affecting features that rely on search — including Bills, Documents, Alerts, and Tracking Boards. The issue was identified as excessive system load caused by unusually complex search queries, which temporarily impacted the responsiveness of several parts of the platform. A subsequent lower impact recurrence of this issue happened on Nov 5th. Our team was automatically notified of the problem and took appropriate steps to mitigate the issue. Service availability and performance were largely restored within the hour, with full stability confirmed overnight. AI Tracking Boards were not affected, and no data loss occurred. Following the incident, Quorum has taken actions to add additional system capacity and improve monitoring and runbooks to reduce the impact of future incidents impacting search systems. Operational excellence and customer trust are central to everything we do, and we are committed to making the necessary improvements to ensure our platform remains reliable, resilient, and responsive to our customers’ needs. All Quorum systems are now fully operational and no similar issues have been reported since Nov 5th. We appreciate your patience and continued partnership as we strengthen the performance and reliability of the Quorum platform.

Read the full incident report →

Started Nov 03, 2025, 08:09 PM UTC· resolved Nov 03, 2025, 08:46 PM UTC

1. investigating Nov 03, 2025, 08:09 PM UTC

   We are currently investigating reports of degraded performance affecting Phone2Action campaign delivery and response times. Users may experience delays in sending or processing campaign actions. Our engineering team is actively working to identify the root cause and restore full functionality.

2. monitoring Nov 03, 2025, 08:26 PM UTC

   We have implemented a fix for the issue that caused degraded performance in Phone2Action campaigns. System performance has returned to normal, and all campaign actions are now processing as expected. Our team will continue to closely monitor the platform to ensure stability and prevent recurrence.

3. resolved Nov 03, 2025, 08:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 28, 2025, 07:15 PM UTC· resolved Oct 28, 2025, 08:12 PM UTC

1. investigating Oct 28, 2025, 07:15 PM UTC

   We are currently experiencing degraded performance on Quorum Pages. Our team is actively investigating the issue and will provide updates as soon as more information is available.

2. identified Oct 28, 2025, 07:26 PM UTC

   We have identified the issue and are in the process of recovering the impacted service. We’ll share another update once full functionality is restored.

3. monitoring Oct 28, 2025, 07:28 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Oct 28, 2025, 08:12 PM UTC

   This incident has been resolved.

5. postmortem Nov 13, 2025, 02:59 PM UTC

   # **Post-Incident Summary – October 28, 2025** On October 28, Quorum experienced a temporary platform performance degradation for approximately one hour. The issue began at approximately 2:43 PM ET and was fully resolved by 3:47 PM ET. During this time, some users experienced slower page loads and occasional timeouts when using the platform. A system update caused some background processes to create higher than expected load on our databases, leading to degraded performance. Our engineering team detected the issue quickly, identified the cause, and rolled back the change, allowing the platform to restore normal performance within an hour. No customer data was lost or at risk at any point. We are implementing several improvements to help prevent similar incidents in the future. These include stronger pre-release testing that more accurately simulates real-world conditions, better tuned automated system load monitoring, and system change control process improvements. These updates are being phased in over the coming weeks. We know reliability is essential to your work and appreciate your patience as we make these enhancements. Our goal is to ensure that Quorum remains a fast, stable, and dependable platform for all customers.

Read the full incident report →

Started Oct 27, 2025, 09:49 PM UTC· resolved Oct 28, 2025, 01:19 AM UTC

1. investigating Oct 27, 2025, 09:49 PM UTC

   We are currently experiencing degraded performance on Quorum Pages. Our team is actively investigating the issue and will provide updates as soon as more information is available.

2. identified Oct 27, 2025, 10:02 PM UTC

   We have identified the issue and are in the process of recovering the impacted service. We’ll share another update once full functionality is restored.

3. monitoring Oct 27, 2025, 10:56 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Oct 28, 2025, 01:19 AM UTC

   This incident has been resolved.

5. postmortem Oct 31, 2025, 08:16 PM UTC

   On October 27, 2025, Quorum experienced a period of degraded performance and intermittent downtime affecting features that rely on search — including Bills, Documents, Alerts, and Tracking Boards. The issue was identified as excessive system load caused by unusually complex search queries, which temporarily impacted the responsiveness of several parts of the platform. Our team was automatically notified of the problem and took appropriate steps to mitigate the issue. Service availability and performance were largely restored within the hour, with full stability confirmed overnight. AI Tracking Boards were not affected, and no data loss occurred. Following the incident, Quorum has taken near-term action to improve monitoring and runbooks to reduce the impact of future incidents impacting search systems, and is implementing additional automatic guardrails to prevent unusually complex queries from affecting system performance. Operational excellence and customer trust are central to everything we do, and we are committed to making the necessary improvements to ensure our platform remains reliable, resilient, and responsive to our customers’ needs. All Quorum systems are now fully operational. We appreciate your patience and continued partnership as we strengthen the performance and reliability of the Quorum platform.

Read the full incident report →

Started Oct 23, 2025, 08:01 PM UTC· resolved Oct 23, 2025, 09:26 PM UTC

1. investigating Oct 23, 2025, 08:01 PM UTC

   We are currently experiencing a service disruption impacting the PAC Platform. Our team is actively investigating the root cause and working to implement a solution. We will share another update within the next 30 minutes.

2. monitoring Oct 23, 2025, 08:16 PM UTC

   The issue affecting the PAC Platform has been resolved. Our team has restored normal service and is now monitoring the system to ensure continued stability.

3. resolved Oct 23, 2025, 09:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 04:26 PM UTC· resolved Oct 21, 2025, 09:33 AM UTC

1. investigating Oct 20, 2025, 04:26 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:41 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:24 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. identified Oct 20, 2025, 09:17 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.

11. identified Oct 20, 2025, 10:00 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.

12. identified Oct 20, 2025, 11:15 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.

13. identified Oct 20, 2025, 11:16 PM UTC

    We are continuing to work on a fix for this issue.

14. monitoring Oct 21, 2025, 12:13 AM UTC

    We’re pleased to report that AWS has restored all of its functionality following the recent service disruptions. Our monitoring indicates that all primary 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.

15. monitoring Oct 21, 2025, 12:59 AM UTC

    We are continuing to monitor for any further issues.

16. resolved Oct 21, 2025, 09:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 04:05 PM UTC· resolved Oct 21, 2025, 12:12 AM UTC

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.

Read the full incident report →