Incident across several services
GitHub · Last saved provider status: resolved
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- resolved
- Provider impact
- minor
- Provider record created
- 23 Sep 2026, 10:11:12 UTC
- Provider record updated
- 29 Sep 2026, 12:43:35 UTC
- Explicit provider start
- 23 Sep 2026, 10:11:12 UTC
- Explicit provider end
- 24 Sep 2026, 04:55:33 UTC
Affected components reported by the provider
- API Requests
brv1bkgrwx7q
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- 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. <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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are preparing to deploy a change that will mitigate the impact.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We will post another update in approximately one hour to share our progress.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
Users may experience stale Project search results. We are working to increase indexing speed. All other services are available.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
Database replicas have been restored. Org creation and the GitHub API are no longer degraded.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of degraded performance for API Requests
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC