Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Mar 16, 2026

  1. AmplitudeExperiment Evaluation Service Outage

    Duration: March 16, 2026, 11:20 AM PT to 1:17 PM PT Between 11:20 AM PT and 1:17 PM PT, the Experiment Evaluation Service experienced a partial outage, resulting in elevated 500, 502, and 503 errors for some requests. Our team has successfully resolved the issue, and the service is now operating normally. We apologize for any inconvenience this disruption may have caused.

    Resolved

  2. GitHubDegraded Codespaces experience

    On March 12, 2026, between 01:00 UTC and 18:53 UTC, users saw failures downloading extensions within created or resumed codespaces. Users would see an error when attempting to use an extension within VS Code. Active codespaces with extensions already downloaded were not impacted.<br /><br />The extensions download failures were the result of a change introduced in our extension dependency and was resolved by updating the configuration of how those changes affect requests from Codespaces. We are enhancing observability and alerting of critical issues within regular codespace operations to better detect and mitigate similar issues in the future.

    Resolved

  3. KeeperResolved: KeeperPAM Connection Errors in US Data Center

    At 11:08 AM PST, DevOps and customers reported sporadic error messages occurring after login for KeeperPAM customers with connections and tunnels enabled. While vault login itself was not affected, the errors were triggered asynchronously after login due to a communication issue with the KeeperPAM router endpoint. Further investigation determined that a "scheduler" database within the AWS RDS environment - used for certain PAM scheduling operations - was encountering an unexpected error. The operations team resolved the underlying database issue and restarted the affected services. This scheduler service was inadvertently impacting connection establishment. To prevent similar issues in the future, we will be implementing software changes to ensure that scheduling-related errors cannot affect connection functionality. Additional monitoring and alerting have also been implemented for the scheduler databases to help detect and prevent similar issues going forward. Full service for connection and tunneling capabilities was restored by 11:40 AM PST.

    Resolved

  4. Intercom - EUIntercom Inbox is experiencing difficulties

    This incident is resolved. The Inbox had high latency and errors between 15:44 UTC and 16:07 UTC. The Messenger was impacted between 16:03 UTC and 16:09 UTC. We will provide a root cause analysis here within 48 hours.

    Resolved

  5. AmplitudeIntermittent Errors in Analytics and Experiment

    Between 2026-03-16 08:57 AM PT (15:57 UTC) and 09:23 AM PT (16:23 UTC), some Amplitude users experienced intermittent 500 errors when loading charts, dashboards, and reports in Analytics and Experiment. A second brief interruption occurred at approximately 09:49 AM PT (16:49 UTC), during which some requests again returned 500 errors. The issue was caused by a temporary database disruption that has since automatically recovered. Our team has confirmed that services are operating normally. No data loss occurred, and no customer action is needed. We are actively investigating the root cause to prevent recurrence and will continue to monitor the system.

    Resolved

  6. GitHubActions failures to download (401 Unauthorized)

    On March 12, 2026 between 02:30 and 06:02 UTC some GitHub Apps were unable to mint server to server tokens, resulting in 401 Unauthorized errors. During the outage window, ~1.3% of requests resulted in 401 errors incorrectly. This manifested in GitHub Actions jobs failing to download tarballs, as well as failing to mint fine-grained tokens. During this period, approximately 5% of Actions jobs were impacted <br /><br />The root cause was a failure with the authentication service’s token cache layer, a newly created secondary cache layer backed by Redis – caused by Kubernetes control plane instability, leading to an inability to read certain tokens which resulted in 401 errors. The mitigation was to fallback reads to the primary cache layer backed by mysql. As permanent mitigations, we have made changes to how we deploy redis to not rely on the Kubernetes control plane and maintain service availability during similar failure modes. We also improved alerting to reduce overall impact time from similar failures. <br />

    Resolved

  7. ElevenLabsSIP Call Failures and Initial Audio Delay

    EU Residency: Starting Saturday, March 14th at approximately 17:00 UTC, some calls were affected by connection failures, or connected with silent audio. This was fully resolved at 08:00 UTC on March 16th. Cross-Region: Starting Sunday, March 15th at approximately 01:00 UTC, some conversations experienced a 1 second delay to initial audio. In some cases, this caused disconnections due to how some SIP trunks handled the audio delay. This issue was fully resolved at 16:00 UTC on March 16th.

    Resolved

  8. ClickHouse CloudClickStack UI is not loading

    The incident was caused by an overloaded database. The instance was scaled up. It is stable again now. We are investigating heavy queries and will apply improvements.

    Resolved

  9. BufferIssue Publishing Posts to TikTok

    The issue with TikTok posts has been fully resolved, and all systems are now operational. We appreciate your understanding and apologise for any disruption this may have caused.

    Resolved

Mar 15, 2026

  1. KernelElevated API error rates

    The issue was resolved by our downstream provider, and error rates have been stable for the past few hours.

    Resolved

Mar 14, 2026

Mar 13, 2026

  1. AirtableMCP Server Unavailable

    A fix has been implemented and the Airtable MCP server is now fully available. Please reach out to Airtable Support if you have any further questions.

    Resolved

Older incidents