GitHub incident across several services resolved

GitHub says an official service incident is resolved.

Sep 24, 2026
•
4 min read
Technobezz
GitHub incident across several services resolved

Don't Miss the Good Stuff

Get tech news that matters delivered to your inbox.

Updated 12:55 a.m. Eastern on September 24, 2026

GitHub reported an incident across several services. The most recent official update states the incident has been resolved.

What is affected

The incident affected API Requests and Projects, including delayed issue label updates and stale Project search results.

Official update timeline

, marked Investigating

We are investigating reports of degraded performance for API Requests

, marked 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.

, marked Investigating

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

, marked Investigating

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

, marked Investigating

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

, marked Investigating

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

, marked 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.

, marked Investigating

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

, marked 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.

, marked Investigating

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

, marked 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.

, marked 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.

, marked 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.

, marked 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.

, marked Monitoring

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

, marked Resolved

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the official GitHub status page.

Track GitHub in the Technobezz status catalog.

Share