‹ Back to incident history

Incident across several services

ResolvedMinor incidentGitHub
Wednesday, September 23, 2026 18:11 – Thursday, September 24, 2026 12:55 (18 hr 44 min)
Affected components
API Requests
Updates
ResolvedThursday, September 24, 2026 12:55

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.

MonitoringThursday, September 24, 2026 12:55

The degradation has been mitigated. We are monitoring to ensure stability.

InvestigatingThursday, September 24, 2026 11:14

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.

InvestigatingThursday, September 24, 2026 10:00

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.

InvestigatingThursday, September 24, 2026 08:16

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.

InvestigatingThursday, September 24, 2026 05:39

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.

InvestigatingThursday, September 24, 2026 04:26

We are preparing to deploy a change that will mitigate the impact.

InvestigatingThursday, September 24, 2026 02:42

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.

InvestigatingThursday, September 24, 2026 01:30

We will post another update in approximately one hour to share our progress.

InvestigatingThursday, September 24, 2026 01:01

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.

InvestigatingWednesday, September 23, 2026 21:35

Users may experience stale Project search results. We are working to increase indexing speed. All other services are available.

InvestigatingWednesday, September 23, 2026 19:38

We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.

InvestigatingWednesday, September 23, 2026 18:58

The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.

InvestigatingWednesday, September 23, 2026 18:57

Database replicas have been restored. Org creation and the GitHub API are no longer degraded.

InvestigatingWednesday, September 23, 2026 18:20

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.

InvestigatingWednesday, September 23, 2026 18:11

We are investigating reports of degraded performance for API Requests

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview