Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Mar 18, 2026

  1. BrowserbaseSessions using Contexts experienced connection failures

    A browser service deployment introduced a compatibility issue that caused sessions using Contexts (persistent browser profiles) to fail on navigation. Affected sessions experienced connection timeouts, 503 errors, and inability to load pages. • Affected users: A small percentage of customers, specifically those who created sessions with a contextId during the impact window • Impact window: ~17 hours, from approximately 5:13 PM PT on March 16 through 8:03 AM PT on March 17, 2026 • Resolution: The browser service deployment was rolled back and full recovery was confirmed. Sessions created after the rollback operated normally. • Customer action: Customers whose Contexts were created or updated during the impact window may have experienced corruption. Affected Contexts should be deleted and recreated. Contexts created before or after the impact window were not affected.

    Resolved

Mar 17, 2026

  1. GitHubErrors starting and connecting to Codespaces

    On 16 March 2026, between 14:16 UTC and 15:18 UTC, Codespaces users encountered a download failure error message when starting newly created or resumed codespaces. At peak, 96% of the created or resumed codespaces were impacted. Active codespaces with a running VSCode environment were not affected. <br /><br />The error was a result of an API deployment issue with our VS Code remote experience dependency and was resolved by rolling back that deployment. We are working with our partners to reduce our incident engagement time, improve early detection before they impact our customers, and ensure safe rollout of similar changes in the future.

    Resolved

  2. TrueLayerEUR Payouts Degraded Performance

    Normal service has been restored. EU Payouts should now be reaching their terminal status normally. Impact start time: 17/03/2026, 22:01 UTC Impact end time: 17/03/2026, 22:34 UTC Client actions: None

    Resolved

  3. GitHubIncident with Webhooks

    On March 9, 2026, between 15:03 and 20:52 UTC, the Webhooks API experienced was degraded, resulted in higher average latency on requests and in certain cases error responses. Approximately 0.6% of total requests exceeded the normal latency threshold of 3s, while 0.4% of requests resulted in 500 errors. At peak, 2.0% experienced latency greater than 3 seconds and 2.8% of requests returned 500 errors.<br /><br />The issue was caused by a noisy actor that led to resource contention on the Webhooks API service. We mitigated the issue initially by increasing CPU resources for the Webhooks API service, and ultimately applied lower rate limiting thresholds to the noisy actor to prevent further impact to other users.<br /><br />We are working to improve monitoring to more quickly ascertain noisy traffic and will continue to improve our rate-limiting mechanisms to help prevent similar issues in the future.

    Resolved

  4. BrazeUS05 Dashboard latency

    No further issues have been experienced, and all services are operating normally. The incident is now resolved.

    Resolved

  5. BlaxelImage Build errors

    This incident has been resolved, and service is operating normally again. Thanks for your patience.

    Resolved

  6. EtsySite Issues

    This incident has been resolved. If you are still experiencing an issue, please let us know in our Etsy Forums (https://community.etsy.com/t5/Technical-Issues/bd-p/bugs).

    Resolved

  7. SumUpTransfers out impacted

    Issue resolved Downloading the latest version of the Android application would solve the problem.

    Resolved

  8. GitHubDegraded performance for various services

    On March 13, 2026, between 13:35 UTC and 16:02 UTC, a configuration change to an internal authorization service reduced its processing capacity below what was needed during peak traffic. This caused intermittent timeouts when other GitHub services checked user permissions, resulting in four to five waves of errors over roughly two hours and forty minutes. In total, 0.4% of users were denied access to actions they were authorized to perform. <br /><br />The root cause was a resource right-sizing change deployed to the authorization service the previous day. It reduced CPU allocation below what was required at peak, causing the service's network gateway to throttle under load. Because the change was deployed after peak traffic on March 12, the reduced capacity wasn't surfaced until the next day's peak. <br /><br />The incident was mitigated by manually scaling up the authorization service and reverting the configuration change. <br /><br /> <br />To prevent recurrence, we are adding further resource utilization monitors across our entire stack to detect throttling and improving error handling so transient infrastructure timeouts are distinguished from authorization failures, enabling quicker detection of the root issue.

    Resolved

  9. UpCloud[FI-HEL1]: Compute Node Issue

    We have been monitoring the situation closely over the 12 hours and can confirm that all affected services have now been fully restored. The Issue impacted some of our Managed Load Balancer instances within the FI-HEL1 Data Centre, which subsequently impacted some Managed Kubernetes clusters in that region. We sincerely apologise for this incident and we continue our internal investigation. If you have any remaining questions, please contact us via email at support@upcloud.com or through our live chat https://hub.upcloud.com/

    Resolved

Mar 16, 2026

  1. Webflow[RESOLVED] Reports of inconsistent publishing results for some sites

    Some sites experienced inconsistent publishing results. During this time, an older version of a site was not always cleared as expected after a new publish. We’re no longer seeing customer impact related to this issue, and this incident is now resolved. Thank you for your patience while we worked through this.

    Resolved

  2. LambdaUS-East 2 and US-East 3 placed under a tornado watch / severe weather warning all day - 3/16/25

    Severity Level: [Low] The incident has been resolved. US-East 2 and US-East 3 is now clear of severe thunderstorm and tornado watch. We will update agin if there are any changes over the next 24 hours. Thank you. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please open a support ticket and we’ll get back to you as soon as possible. • https://support.lambdalabs.com/hc/en-us/requests/new To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button.

    Resolved

  3. WarpIntermittent DNS Issues

    GoDaddy has resolved their issues and access to Warp appears restored. Thank you for your patience.

    Resolved

Older incidents