← Live dashboard

Disruption with some GitHub services

ResolvedmajorOfficial source confirmedFirst recorded update Oct 5, 2026, 11:47 PM · Resolved Oct 6, 2026, 01:32 AM

On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests to the service that powers these pages.<br /><br />This was caused by a networking failure, which disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database services. We mitigated the incident by shifting the database traffic to a healthy region.<br /><br...

GitHub live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with GitHub now? Check the current status

Updates (3)

  1. Oct 6, 2026, 01:32 AM
    Disruption with some GitHub services

    On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests to the service that powers these pages.<br /><br />This was caused by a networking failure, which disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database services. We mitigated the incident by shifting the database traffic to a healthy region.<br /><br />We

    GitHub ↗
  2. Oct 6, 2026, 12:05 AM
    Disruption with some GitHub services

    Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.

    GitHub ↗
  3. Oct 5, 2026, 11:47 PM
    Disruption with some GitHub services

    We are investigating reports of impacted performance for some GitHub services.

    GitHub ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow GitHub's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.