Incident with several GitHub Services

At a glance · GitHub's status

ResolvedLasted 1 h 28 min

First posted
on GitHub Status
Ended
· marked resolved
Affects
5 services: GitHub Actions, GitHub API requests, GitHub pull requests +2
Edited
Not since we first saw it
Source
GitHub Status · checked just now

In short

GitHub reported a major outage affecting 5 GitHub services, including GitHub Actions, GitHub API requests and GitHub pull requests, starting 09:16 UTC on 13 Sep. GitHub marked it resolved at 10:44 UTC after 1 h 28 min.

GitHub says

GitHub's latest update, , in short excerpts.

On September 13, 2026, between 08:43 and 10:44 UTC, GitHub experienced degraded availability across approximately 28 services, including Issues, Pull Requests, Actions, Codespaces, Pages, Notifications…

GitHub,

Read the full update on GitHub's status page

Timeline

Times in UTC, GitHub's own where it gives them.

  1. 13 Sep

    GitHubFirst public postFrom GitHub's own incident history, before our archive started.

  2. +1 h 29 min

    GitHubResolved

What GitHub changed

GitHub adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on GitHub's page.

One version so far. If GitHub edits it, each change shows here with what was removed and added.

  1. First version we captured ·

    As first seen: resolved · 5 services
    Status
    resolved
    Services
    5: GitHub Actions, GitHub API requests, GitHub pull requests +2

    Seen by us · GitHub's timestamp · GitHub's page

Affected services

Official updates

Posted by GitHub Status, newest first. The newest are quoted in their first sentence; the full text of each is on GitHub's page.

  1. Resolved ·

    On September 13, 2026, between 08:43 and 10:44 UTC, GitHub experienced degraded availability across approximately 28 services, including Issues, Pull Requests, Actions, Codespaces, Pages, Notifications…

  2. Investigating ·

    Pull Requests is experiencing degraded performance.

  3. Investigating ·

    We have reduced load on this cluster with internal load-shedding and are seeing signs of recovery but continue to monitor

  4. Investigating ·

    We're seeing increased database replication delays on collab which is causing increased error rates in authorization endpoints and follow-on increased error rates across the system…

  5. Investigating ·

    Actions is experiencing degraded performance.

  6. Investigating ·

    We are investigating reports of degraded availability for API Requests, Issues, Pages and Pull Requests

Read the full update on GitHub's status page

Last updated