GitHub outage on September 23, 2026: Incident across several services

GitHub reported an incident affecting GitHub for 18 hours 44 minutes on 23 September 2026, from 10:11 to 04:55 UTC.

github.com All times UTC

Resolved

Official incident reported by GitHub

Started: 10:11; 23 Sep 2026 UTC
Resolved: 04:55; 24 Sep 2026 UTC
Duration: 18h 44m; 18 hours 44 minutes
Impact: Minor; as rated by GitHub
Updates: 16; posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Incident across several services

Resolved Minor impact 23 Sep 2026 10:11 UTC View on GitHub's status page

23 Sep 10:11 Official
Investigating
We are investigating reports of degraded performance for API Requests
23 Sep 10:20 Official
Investigating
Database replicas have detached. We're working to restore the database replicas. Users may experience issues beyond creating organizations and a degraded experience with the GitHub API and Projects.
23 Sep 10:57 Official
Investigating
Database replicas have been restored. Org creation and the GitHub API are no longer degraded.
23 Sep 10:58 Official
Investigating
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
23 Sep 11:38 Official
Investigating
We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.
23 Sep 13:35 Official
Investigating
Users may experience stale Project search results. We are working to increase indexing speed. All other services are available.
23 Sep 17:01 Official
Investigating
Updates to issue labels may be delayed in being reflected in Projects by about ~10 minutes. We have added some capacity to work through the backlog more quickly, but it'll likely be a few hours to complete processing the full backlog of messages. All other services are available.
23 Sep 17:30 Official
Investigating
We will post another update in approximately one hour to share our progress.
23 Sep 18:42 Official
Investigating
Continuing to investigate the lag that may be experienced in issue labels being accurately reflected in Projects. We are working on alternate solutions to process the backlog of label updates.
23 Sep 20:26 Official
Investigating
We are preparing to deploy a change that will mitigate the impact.
23 Sep 21:39 Official
Investigating
Updates to issue labels may be delayed in being reflected in Projects. We are continuing to deploy a change that will accelerate processing of the backlog of label updates. All other services are available. We will provide another update within the next hour.
24 Sep 00:16 Official
Investigating
We've deployed a change intended to accelerate processing of the backlog of issue label updates in Projects. A sizable backlog still remains and we continue working through it. All other services are operating normally. We will provide another update within the next hour.
24 Sep 02:00 Official
Investigating
We are continuing to process the backlog of issue label updates for Projects. Users may still see delays before label changes are reflected in Projects. All other services are operating normally.
24 Sep 03:14 Official
Investigating
We are continuing to process the backlog of issue label updates for Projects. Label changes may still be delayed. All other services are operating normally.
24 Sep 04:55 Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
24 Sep 04:55 Official
Resolved
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. 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. 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. 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...

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

All GitHub incidents Live GitHub status Every service we track

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.