Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Mar 2, 2026

  1. SnowflakeAzure - Canada Central (Toronto): INC0152309

    Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0152309](https://community.snowflake.com/s/article/INC0152309)

    Resolved

  2. LinearSubset of agent app users experiencing access problems

    Any remaining affected agents are now active again in all regions. Access has been fully restored. If you continue to see Cursor, GitHub Copilot, and Codex agents in a suspended state unexpectedly, please reach out to support@linear.app.

    Resolved

  3. Help ScoutConnections Issues

    Performance is stable across the board, so we're closing this out. We'll continue to monitor all services over the next few hours.

    Resolved

  4. GitHubIncident with Issues and Pull Requests Search

    On February 23, 2026, between 21:01 UTC and 21:30 UTC the Search service experienced degraded performance, resulting in an average of 3.5% of search requests for Issues and Pull Requests being rejected. During this period, updates to Issues and Pull Requests may not have been immediately reflected in search results. <br /><br />During a routine migration, we observed a spike in internal traffic due to a configuration change in our search index. We were alerted to the increase in traffic as well as the increase in error rates and rolled back to the previous stable index. <br /><br />We are working to enable more controlled traffic shifting when promoting a new index to allow us to detect potential limitations earlier and ensure these operations succeed in a more controlled manner.

    Resolved

  5. Webflow[RESOLVED] Reports of issues purchasing or upgrading plans

    Between 07:20 UTC and 12:40 UTC, some customers were unable to complete purchases for new plans due to an issue with one of our upstream providers. They have since identified the root cause and implemented a fix. As a result, new plan purchases are now working as expected again. We sincerely appreciate your patience and understanding as we worked to resolve this issue with the support of our upstream provider, and apologize for any inconvenience caused.

    Resolved

  6. New RelicDelay in executing synthetics monitors

    Between 06:56 UTC and 08:44 UTC on March 02nd some customers in the US or EU region may have experienced Delay in executing synthetics monitors .We have investigated and resolved this service interruption and impacted services have returned to normal operations

    Resolved

Mar 1, 2026

  1. TrueLayerPayments Product Degraded Performance

    We experienced a small window of degraded performance affecting payments (Pay-ins and VRP). During this time, you may have received 500 responses. This is now resolved. Impact start time: 01/03/2026, 17:19:51 GMT Impact end time: 01/03/2026, 17:20:14 GMT Client actions: None

    Resolved

Feb 28, 2026

  1. ZuoraEmail / Notification Latency Spike

    During month end monitoring, we observed spike in email/notification processing latency. Timeframe: 5:05 am PST ~ 8:00 am PST Latency has returned to normal levels and no ongoing impact observed.

    Resolved

  2. SupabaseIncreased Edge Function Errors across multiple regions

    The issue affecting Edge Functions has now been fully resolved, and users have reported Edge Functions operating as expected. The root cause was a denial-of-service event that led to elevated error rates and 504 responses across impacted regions. Mitigations have been implemented to restore stability. We will be publishing a full post-mortem with additional details, once our internal review is complete. Thank you for your patience while we worked to resolve this issue.

    Resolved

  3. ChargebeeAPI Service Degradation

    We experienced intermittent API request timeouts during two brief one-minute windows between 14:23 and 14:46 UTC. The issue has since been resolved, and services are operating normally.

    Resolved

  4. CartesiaDegraded generation quality on public voices

    Overview • During a maintenance upgrade to Cartesia’s voice metadata, existing metadata for a narrow subset of default Cartesia voices was unintentionally overwritten, causing voice changes. • Some voices were affected more than others. A narrow subsection of voices saw increased hallucinations while 3 voices were significantly impacted. • Degradation occurred gradually as caches began expiring and was mitigated after a database restore and global cache purge. • In addition to fixing the root cause, we are updating our change management and monitoring process to prevent issues like this in the future by enforcing data upgrade safety via tooling, improving automatic detection, updating our triage process, and investing in a lower recovery time objective \(RTO\) for critical data like voices. Detailed Analysis Timeline \(UTC\) • 2026-02-25 04:57 – Upgrade completes, overwritten voice metadata starts being served as caches expire. We regularly test our model for regression, but since only a small subsection of voices were affected, they were not caught by our automated testing in this case. • 2026-02-25 23:00 - 2026-02-26 17:00 – We receive reports of voice changes and begin internal investigation to assess scope and severity. The on-call investigated but made an incorrect determination of the source and severity of the issue which delayed remediation. • 2026-02-26 18:40 – Impact triaged to high severity. • 2026-02-26 19:27 – Root cause identified; mitigation plan begins. • 2026-02-26 22:13 – Data fully restored; global cache purge begins. • 2026-02-26 23:06 – Global cache purge completes. Customers begin confirming resolution. • 2026-02-26 23:20 – Status page marked resolved Root cause A bug in the code executing a maintenance upgrade to Cartesia’s voice metadata caused the metadata for some existing voices to be regenerated and overwritten. This metadata is fundamental to how we represent voices and changes to this metadata can lead to changes in voice output. The code path containing the bug was executed because some default voices did not fulfill an invariant of the metadata upgrade process and were incorrectly identified as requiring an upgrade. The issue was not caught in manual or automated testing, because because it only reproduces in a specific state that exists in production and affects a narrow subsection of voices. Learnings and Next Steps We sincerely apologize for this incident and the disruption it caused to your business. We understand that reliable voice quality is fundamental to your trust in Cartesia. We are making the following corrections to our change management process and monitoring process to prevent issues like this in the future, targeting every step of the release and error recovery lifecycle: 1. Safer processes for routine data changes, enforced via tooling: We are investing in automated tooling to make our existing change management process even more thorough. We will incorporate additional automated tooling to triage the risk of changes, do dry runs on realistic data, and ensure multiple sign-offs beyond code review with automatic rollbacks in case of errors. 2. Improved automatic detection: We are expanding our automatic voice regression testing to expand coverage to much larger set of voices and transcripts. 3. Update triage process: The issue was incorrectly triaged. We will update our triage playbook to ensure that any reported voice issues are comprehensively checked against recent code and data changes to speed up an RCA and determine scope. This will ensure future issues are correctly escalated faster. 4. Invest in lower RTO: Our RTO for our voices infra is currently at 4 hours. However, for critical data like voices, we will invest in bringing down our RTO to 15 minutes. We will implement automation around finer grained data snapshots and data restoration that are currently manual or slow. If you have any questions or concerns about this incident, please don't hesitate to reach out to our support team.

    Resolved

Older incidents