ismyagentdownAll agentsAlerts
All agents  /  GitHub  /  History  /  Sep 13, 2026

GitHub outage on Sep 13, 2026: incident with several GitHub Services

Resolved after 1 h 29 min.

09:16 UTC to 10:44 UTC your time. GitHub: “Incident with several GitHub Services.” 0 reports here during the incident.

GitHubUpRight now GitHub is up. See live status

Reports during the incident

Every 15 minutes, 08:15 UTC to 11:45 UTC. Grey: normal. Red line: official incident.
08:15 UTC09:16 UTC10:44 UTC11:45 UTC

What people reported

0 reports during the incident

No reports in this window.

GitHub's updates

Quoted from www.githubstatus.com

  1. 09:16 UTC

    Investigating

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

  2. 09:25 UTC

    Investigating

    Actions is experiencing degraded performance. We are continuing to investigate.

  3. 09:36 UTC

    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 - we are investigating

  4. 10:26 UTC

    Investigating

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

  5. 10:28 UTC

    Investigating

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  6. 10:44 UTC

    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, Code Scanning, Git LFS, and new account signup. At peak, 8.8% of requests to create GitHub App installation access tokens failed. Token issuance for Actions workflows was also affected, impacting approximately 4% of workflows during the incident time frame. Creating issues through the web interface failed for about 96% of attempts, and signup failures were above 90%. <br /> <br />The cause was an internal data-cleanup job that began writing to a shared database cluster at 07:33 UTC. That cluster stores permission data read on nearly every authenticated request. The safeguard that was pacing the background job watched only one health signal — how far the database replicas were lagging — and that signal stayed low the whole time. It did not account for the load building on the primary itself, so the job kept writing while the primary quietly ran toward its limit. <br /><br />When the primary ran out of available connections, requests that needed it could not complete. First, there w…

Other GitHub incidents

Nov 81 h 57 minIncrease in timeouts for some unauthenticated usersDetails
Nov 545 minDegraded performance for multiple GitHub servicesDetails
Nov 552 minIncident with ActionsDetails
All GitHub incidents

Other agents

Claude CodeUpCodexUpCursor IDEUpGitHub CopilotUpGemini CLIUpClaude APIUpOpenAI APIUp

Know the moment it's back.

Coral shows it in your Mac's notch, and tells you which agent needs you. Free.

Get Coral for Mac

Official status from Anthropic, OpenAI, GitHub, Google and Cursor, checked every minute. Reports come from people on this site. We keep no IP address and set no cookies.

AlertsRSSPrivacyMade by Coral