GitHub partial outage, September 13, 2026

On Sunday, September 13, 2026, GitHub reported a Partial System Outage. The incident remains unresolved. GitHub's latest public update, posted 5:36 a.m. ET (09:36 UTC), says increased database replication delays on collab are causing increased error rates in authorization endpoints and follow-on increased error rates across the system. Status: Investigating. Impact: critical / Partial System Outage.

Times below are Eastern (UTC-4). This is a live-tracking post, last updated ~6:15 a.m. ET, and may be updated again as the incident resolves. Check the linked status pages for the latest.

Incident with several GitHub Services

Incident: Incident with several GitHub Services [1]. Status: Investigating. Page banner: Partial System Outage [2]. As of ~6:10 a.m. ET, GitHub has not marked the incident Identified, Monitoring, or Resolved, and has not published a root-cause analysis beyond the collab replication-delay statement.

• 5:16 a.m. ET (09:16 UTC) — Investigating. "We are investigating reports of degraded availability for API Requests, Issues, Pages and Pull Requests." Pull Requests listed Major Outage. API Requests, Issues, and Pages listed Degraded Performance [1].
• 5:25 a.m. ET (09:25 UTC) — Update. "Actions is experiencing degraded performance. We are continuing to investigate." Actions moved from Operational to Degraded Performance [1].
• 5:36 a.m. ET (09:36 UTC) — Update. "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" [1].

Component list as of ~6:10 a.m. ET [2]:

Major Outage: Pull Requests.

Degraded Performance: API Requests; Issues; Actions; Pages.

Operational: Git Operations; Webhooks; Packages; Copilot; Codespaces; Copilot AI Model Providers.

Git Operations remaining Operational means GitHub is not listing clones, pulls, and pushes as the named failure. The named blast radius is collaboration and workflow surfaces: pull requests, issues, the API, Actions, and Pages. Authorization-endpoint errors can still affect those surfaces even when git transport looks healthy.

GitHub has not listed a customer workaround. GitHub has not said whether the collab replication delay is fully contained. The 5:36 a.m. ET update is still Investigating.

Downstream

OpenAI posted Codex GitHub Review and Pull Request Failures beginning 5:26 a.m. ET (09:26 UTC) as downstream of this GitHub incident, citing review publication and pull request creation in Codex [3]. That is not a separate root cause. As of 5:55 a.m. ET, OpenAI was in Monitoring and wrote that GitHub had applied a mitigation. GitHub's own incident remains Investigating; GitHub has not posted a matching mitigation or monitoring update as of this writing [1][2][3].

Impact

Teams using GitHub.com this morning may see pull-request failures or errors, plus degraded API, Issues, Actions, and Pages. That combination hits code review, issue tracking, CI, and Pages builds. Copilot, Codespaces, Packages, Webhooks, and Git Operations are listed Operational on GitHub's status page, so those components are not part of the named outage in this incident.

StatusStack is tracking the same open incident at statusstack.com/service/github (HTTP 200 at last check). StatusStack previously covered GitHub's August 2026 outages at statusstack.com/blog/github-august-2026-outage.

One dashboard for GitHub and the rest of the stack is faster than tab-hopping vendor status pages during an incident. Monitor GitHub or start monitoring free.

References

[1] GitHub. (2026, September 13). Incident with several GitHub Services. Retrieved ~6:10 a.m. ET from https://www.githubstatus.com/incidents/0rn90wk115q9 and https://stspg.io/8f3xch4y0v2k

[2] GitHub. (2026, September 13). GitHub Status. Retrieved ~6:10 a.m. ET from https://www.githubstatus.com/

[3] OpenAI. (2026, September 13). Codex GitHub Review and Pull Request Failures. Retrieved ~6:10 a.m. ET from https://statuspage.incident.io/openai-1/incidents/rqp16qq5 and https://status.openai.com/incidents/rqp16qq5

[4] StatusStack. (2026, September 13). Is Github Down? Retrieved ~6:10 a.m. ET from https://statusstack.com/service/github