Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Oct 7, 2026

  1. OVHcloud - Public Cloud[AF-NORTH/EU-WEST/EU-NORTH][LocalZones] - IPv6 incident notification

    We had an incident on LocalZones offer for AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC regions which has now been resolved. Here are some supplementary details : <b>Start time :</b> 07/10/2026 08:00 UTC <b>End time :</b> 07/10/2026 12:00 UTC <b>Impacted Service(s) :</b> IPv6 was temporarily unavailable for the specified LocalZones. <b>Customers Impact :</b> Customers were temporarily unable to use IPv6 in AF-NORTH-LZ-RBA, EU-WEST-LZ-DL, EU-NORTH-LZ-OSL and EU-WEST-LZ-MNC LocalZones. <b>Root Cause :</b> This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.

    Resolved

  2. SinchDelivery Issue USA - AT&T

    This incident has been resolved. Incident Start Time: 2026-10-07 05:18 UTC Incident End Time: 2026-10-07 09:44 UTC

    Resolved

  3. OVHcloud - Public Cloud[GRA][Compute - Instance] - Some Instances incident notification

    We had an incident on Compute - Instance offer which has now been resolved. Here are some supplementary details : <b>Start time :</b> 07/10/2026 05:07 UTC <b>End time :</b> 07/10/2026 05:15 UTC <b>Impacted Service(s) :</b> Some instances in the GRA regions were unreachable via public and vRack network. <b>Customers Impact :</b> Some customers were temporarily unable to access instances located on the specified regions. <b>Root Cause :</b> A service disruption occurred due to an unexpected infrastructure failure. We thank you for your understanding and patience throughout this incident.

    Resolved

  4. VapiSIP Server downtime

    There will be reactive maintenance on SIP outbound dialing infrastructure, US region Status: Scheduled What is affected: Our SIP infrastructure provider will upgrade the web server/API that controls outbound dialing, as part of remediating the root cause of today's incident. Inbound calls are not affected. When: Tuesday, October 6, 21:00–21:15 PT (04:00–04:15 UTC, Oct 7) What to expect: This work is not expected to be customer-impacting or noticeable. Outbound calls may briefly stall during the window; any impact should last less than 10 minutes. Action needed: None

    Resolved

Oct 6, 2026

  1. GitHubIncident with Actions

    On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. <br /><br /> <br />During the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve normally. A portion of customers also encountered intermittent errors in repository lists, licensing and billing pages, and some Copilot features. Self-hosted runners were not affected. <br /><br /><br />The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services. <br /><br /><br />We mitigated the incident by shifting database and storage traffic to healthy regions and endpoints and increasing capacity for affected compute services. GitHub Actions and Hosted Runners recovered by 21:54 UTC, and all affected services recovered by 22:49 UTC. <br /><br /> <br />We are partnering with our cloud provider to understand the network failure and identify improvements to network-path resilience, detection, and recovery for similar incidents.

    Resolved

Older incidents