What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with GitHub now? Check the current statusAffected services
Updates (16)
- Sep 24, 2026, 04:55 AMIncident 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
GitHub ↗ - Sep 24, 2026, 04:55 AMIncident across several services
The degradation has been mitigated. We are monitoring to ensure stability.
GitHub ↗ - Sep 24, 2026, 03:14 AMIncident across several services
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.
GitHub ↗ - Sep 24, 2026, 02:00 AMIncident across several services
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.
GitHub ↗ - Sep 24, 2026, 12:16 AMIncident across several services
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.
GitHub ↗ - Sep 23, 2026, 09:39 PMIncident across several services
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.
GitHub ↗ - Sep 23, 2026, 08:26 PMIncident across several services
We are preparing to deploy a change that will mitigate the impact.
GitHub ↗ - Sep 23, 2026, 06:42 PMIncident across several services
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.
GitHub ↗ - Sep 23, 2026, 05:30 PMIncident across several services
We will post another update in approximately one hour to share our progress.
GitHub ↗ - Sep 23, 2026, 05:01 PMIncident across several services
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.
GitHub ↗ - Sep 23, 2026, 01:35 PMIncident across several services
Users may experience stale Project search results. We are working to increase indexing speed. All other services are available.
GitHub ↗ - Sep 23, 2026, 11:38 AMIncident across several services
We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.
GitHub ↗ - Sep 23, 2026, 10:58 AMIncident across several services
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
GitHub ↗ - Sep 23, 2026, 10:57 AMIncident across several services
Database replicas have been restored. Org creation and the GitHub API are no longer degraded.
GitHub ↗ - Sep 23, 2026, 10:20 AMIncident across several services
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.
GitHub ↗ - Sep 23, 2026, 10:11 AMIncident across several services
We are investigating reports of degraded performance for API Requests
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.