Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Sep 29, 2026

  1. AkamaiEdge Delivery issues in Canada

    Our third-party service provider has confirmed that the issue was mitigated at 16:08 UTC on September 28, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001W3hnvCAB or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.

    Resolved

  2. UpstashBrief connection proxy degradation in us-east-1

    Between 15:12 and 15:16 UTC, we observed a brief increase in load on the connection proxy layer in us-east-1, which may have affected some existing and new connections. The team responded quickly and resolved the issue. All systems are now fully operational.

    Resolved

  3. OVHcloud - Public Cloud[US-EAST-VA][Storage] - Object Storage incident notification

    We are pleased to inform you that the incident affecting our Storage offering has been resolved. <b>Start time :</b> 25/09/2026 11:00 UTC <b>End time :</b> 29/09/2026 14:22 UTC <b>Root Cause :</b> This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

    Resolved

  4. KernelElevated errors for residential proxy creation

    Elevated latency affecting residential and mobile proxy creation has subsided, and proxy creation is back to normal. Existing proxy traffic and ISP and datacenter proxy creation were not affected. We’re continuing to monitor.

    Resolved

  5. GitHubIncident across several services

    Starting at 07:57 UTC on September 23, GitHub experienced elevated 500 and 404 responses across several application pages. This caused failures when installing GitHub Apps, creating organizations, and making some organization membership changes. Customers also experienced delayed label updates and stale search results in Projects. <br /><br />The infrastructure failure was isolated to our Azure Central US region. The API errors were mitigated by 10:58 UTC on September 23. Projects' processing continued to recover while an accumulated backlog was drained, and full service was restored at 04:55 UTC on September 24. <br /><br />The incident was caused by a failed planned maintenance operation on a primary database. Automated recovery initiated an emergency database failover, after which several replicas in the affected region were unable to resume replication correctly. This reduced available database capacity and caused the API errors and downstream Projects processing delays. <br /><br />We have mitigated the immediate failure mode. We are also improving maintenance safety checks, database failover handling, post-failover replica validation, and downstream processing resilience to reduce the likelihood and impact of similar incidents.

    Resolved

  6. NetlifyError accessing Netlify-hosted sites

    This incident has been resolved. Sites on the High-Performance Edge have returned to normal operation, and we are no longer seeing elevated error rates.

    Resolved

  7. JFrogJFrog Cloud Platform degraded performance for GCP regions

    We identified an issue affecting Artifactory upload and download functionality for some customers hosted in the Google Cloud Platform (GCP) US Central, US West, and Europe West regions The investigation indicates the issue originated with our cloud provider, Google Cloud. Services are currently operating normally. JFrog engineers are working with Google Cloud to confirm the root cause and are continuing to closely monitor service health.

    Resolved

  8. Vonage APIIssues impacting Customer Dashboard Aggregations for Verify v2

    Vonage services have been fully restored following today's service interruption, which began at 2026-09-28 21:00 UTC. Full resolution has been confirmed effective 2026-09-29 00:53 UTC. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com

    Resolved

  9. HarnessAPI Login failures

    # Root Cause Analysis Report ## Brief API Login Failures Due to a Security Policy Misconfiguration ## 1. Executive Summary On September 11, 2026, a change to one of our network security policies was deployed with a configuration error. For approximately 6 minutes, this caused login requests to be incorrectly blocked, preventing some users from logging in. ‌ The issue was detected automatically by our monitoring systems. The problematic change was fully reverted within 5 minutes of detection, restoring normal login functionality. # 2. Impact * For approximately 6 minutes \(12:30–12:36 PM CT on September 11, 2026\), login requests matching certain URL paths were incorrectly blocked. * Any user attempting to log in during this window could have been affected * No other functionality was affected. Users already logged in prior to the window were not impacted. # 3. Root Cause As part of a planned security enhancement, our team implemented a new network security policy intended to block a small number of specific, exact URL paths. During implementation, the rule was configured with an erroneous matching condition instead of the intended exact-match condition. ‌ As a result, the policy blocked any request whose path began with those values, rather than only the exact paths intended ,  which included legitimate login requests that happened to share that prefix. This caused those login attempts to be rejected during the affected window. # 4. Resolution * The problematic policy change was identified and fully reverted within 5 minutes of the first alert. * Normal login functionality was confirmed restored immediately following the revert. # 5. Risk of Recurrence & Preventive Actions‌ | **Corrective / Preventive Action** | | --- | | Enhanced our QA validation step in the process for this class of security policy change, so the deployed configuration is checked against its intended specification before go-live. | | Enhanced automated test coverage that specifically validates exact-match versus prefix-match behavior for path-based rules, as an additional safeguard on top of the review process. |

    Resolved

Sep 28, 2026

  1. ConvexAI gateway unavailable

    An issue with an upstream provider caused requests to the AI Gateway to be rejected. The issue has been resolved and service has been restored. We apologize for the disruption.

    Resolved

  2. DeepgramElevated Latency and Errors for Batch STT (US)

    An issue affecting some of our pre-recorded transcription servers slowed request processing. As requests took longer to complete, some customers saw elevated latency or received 429 errors. We identified and mitigated the issue, service has returned to normal.

    Resolved

  3. AttioWorkflow processing delayed

    The issue affecting workflow execution and webhook delivery has now been resolved. We’re sorry for any inconvenience caused.

    Resolved

  4. CloudflareNetwork Performance Issues in Eastern North America

    Cloudflare observed issues with network performance in Eastern North America today, 2026-09-28, between approximately 19:50 and 20:20 UTC. Customers may have observed elevated error rates for traffic in this region during this period.

    Resolved

  5. HootsuiteComposer "Oops! Something went wrong" error

    We are aware of a service disruption that impacted the Composer recently. Between the times 3:22am-11:21am (PST) on September 28, customers may have experienced difficulties in the Composer. Customers may have encountered an error message displaying "Oops! Something went wrong" in the Composer when trying to publish/schedule a post. This issue has now been resolved and all services have been restored to normal operations. Kindly note we need to refresh our page/tab to clear the existing error in the Composer. Please reach out to our Customer Support team if you encounter any further issues.

    Resolved

Older incidents