Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

May 9, 2026

  1. NetlifyIssues Processing Account Changes

    We experienced issues processing account changes between 19:09 and 19:33 UTC. Users may have encountered issues when attempting to use Agent Runners, purchase credits, view credit usage, or complete account transactions. This issue is now resolved.

    Resolved

  2. KlaviyoCampaign and flow page loading errors

    Analytics processing for campaigns and flows is fully caught up and operating normally. We appreciate your patience throughout this incident. This incident has been resolved.

    Resolved

  3. ChatGPT / OpenAIElevated errors for Responses API

    All impacted services have now fully recovered. Between 4:05pm and 4:40pm PT on May 8, some customers using the Responses API may have experienced elevated 404 errors. We identified the issue as related to a recent deploy and rolled it back. Responses API traffic has recovered, and we are marking this incident as resolved.

    Resolved

May 8, 2026

  1. GitHubIncreased Latency and Failures for SSH Git Operations

    Between approximately 14:00 and 16:10 UTC on May 5, 2026, SSH-based Git operations experienced elevated latency and intermittent failures. On average, the error rate was 0.46% and peaked at 0.6% of SSH write requests. HTTP-based Git operations, including web UI and HTTPS clones, were not affected. <br /><br />The impact was caused by reduced SSH capacity at one of our data center sites. During a period of high traffic, the remaining hosts became overloaded, leading to connection exhaustion and some failures for SSH-based operations. <br /><br />Additional capacity was provisioned to expand SSH capacity and resolve the incident. The expanded capacity was fully online by 18:18 UTC. <br /><br />To reduce the likelihood of similar incidents, we will implement faster scaling solutions for SSH infrastructure and improved alerting for host availability and capacity thresholds.

    Resolved

  2. GitHubIncident with Issues and Webhooks

    On 2026-05-04 at 3:37:17 PM UTC we detected increased latency on issues resulting in timeouts, and elevated 500 errors on webhooks. A scheduled workload drove high utilization on the primary host of a critical datastore, saturating the connection pool. We paused the job to mitigate the problem at 4:40:05 PM UTC and have implemented measures to prevent recurrence.

    Resolved

  3. ZapierErrors when creating or reconnecting app connections

    Our Engineering team has monitored our backend for any spikes in errors after the fix was released, and we're happy to see that we're at normal operation and no longer seeing errors. As such, the incident is now considered resolved. Please reach out to our Support team if you continue to see issues or have questions about the incident.

    Resolved

  4. DigitalOceanLet's Encrypt Outage Affecting Certificate Issuance and Managed Databases Operations

    The upstream outage with Let's Encrypt has been resolved. Customers should now be able to issue Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains. Our Engineering team has also confirmed that stuck or delayed actions with Mongo, Advanced PG, and Advanced MySQL databases should complete normally now. We appreciate your patience. If you continue to experience any issues, please open a support ticket from within your account.

    Resolved

  5. SnykCLI Monitor Degredation

    CLI Monitor performance is stable. Post-mitigation monitoring is complete, and the incident response has concluded.

    Resolved

  6. RollbarItem Processing impact for RUBY and PHY SDKs

    Earlier today we identified and resolved an issue impacting customers using our PHP and Ruby SDKs. A backend API change deployed on Friday 5/8/26 ~2:30PM PT inadvertently broke request parsing for certain payloads sent with the Ruby and PHP SDKs. As a result, occurrences sent during this window were rejected and not recorded. We rolled back the change this morning (5/9 at 8:30 am PT) and occurrence ingestion is back to normal. Unfortunately, occurrences that were dropped during the affected window, were not stored and cannot be recovered. We understand thats a gap in your observability and we take that seriously. We’re conducting a full postmortem and will publish details on our statue page. In the meantime if you’re still seeing issues or have questions, please don’t hesitate to reply here.

    Resolved

  7. DigitalOceanMultiple Services in NYC2

    Our engineering team has resolved the issue with multiple services in NYC2 region, and all services should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and thank you for your patience.

    Resolved

  8. PlanetScaleAWS use1-az4 thermal event

    PlanetScale is not observing any database impact resulting from the AWS use1-az4 thermal event. Please contact support if you have any questions or notice any disruption.

    Resolved

  9. KlaviyoProcessing delays

    Segmentation continues to process in real-time and is fully recovered. We determined the delays resulted from instability with an upstream infrastructure provider (AWS). This incident is now resolved.

    Resolved

  10. UdemyService disruption

    The issue caused by a third-party infrastructure problem has been resolved. Systems are now back to normal, and services are running as expected. We’ll keep monitoring closely, but things are looking good on our side.

    Resolved

  11. BufferIssue with Threads comments

    The issue with Threads has been fully resolved, and it’s functioning as expected again. If you encounter any further problems, please don’t hesitate to reach out to our team.

    Resolved

  12. GitHubIncident with Actions, we are investigating reports of degraded availability

    On May 6, 2026, from approximately 06:45 UTC to 09:15 UTC, GitHub Actions Standard Ubuntu hosted runners were degraded. 17.1% of jobs requesting a standard runner failed.<br /><br />This was caused by an unexpected data shape in the allocation configuration data for standard runners. That data was introduced as part of post-incident remediation work for an incident the previous day and caused new allocations to be blocked as load ramped up for the day. Removing that data at 08:51 allowed allocations to proceed and hosted runner pools to scale up and recover.<br /><br />We are updating the filter logic for this allocation data to be resilient to abnormal data shapes and improving monitoring to alert when allocations are blocked, allowing the team to respond before customer impact starts.

    Resolved

  13. GitHubIncident with Actions

    On May 5, 2026, from approximately 13:22 UTC to 17:05 UTC, GitHub Actions hosted runners in the East US region were degraded. 13.5% of jobs requesting a standard runner failed and ~16% of requested Larger Runners with private networking pinned to East US failed or were delayed by more than 5 minutes. Copilot Code Review requests were also impacted. Approximately 8,500 code review requests timed out during this window. Affected users saw an error comment on their pull requests and were able to retry by re-requesting a review. Most runner requests were picked up by other regions automatically, but a portion of requests still routing to East US were impacted.<br /><br />This was triggered by a scale-up operation for hosted runner VMs in the East US region. This is a regular operation, but the VM create load hit an internal rate limit when VM creates pull images from storage. Existing backoff logic was not triggered because of the response code returned in this case. The rate limiting and VM creation failures were mitigated by reducing load to allow for recovery and allowing queued work to be processed. By 15:34 UTC, queued and failed job assignments were mostly mitigated, with less than 0.5% of runner assignments impacted between 15:34 and full recovery at 17:05.<br /><br />We are improving our system’s throttling behavior when limits occur, improving our controls to more quickly mitigate similar situations in the future, and reviewing all limits end-to-end for similar operations. We also immediately paused all scale and similar operations until these changes are in place and validated.

    Resolved

  14. SumUpCloud Api transactions are failing

    The issue has been fixed and we’re confident it’s resolved SumUp services have returned to normal. You can stay up to date on the status of our services anytime here on our status page: https://status.sumup.com.

    Resolved

Older incidents