Skip to content
NO FEED

Understand the changes. Choose the tools. Put AI to work.

← News
News

GitHub ran a critical incident for 1h 29m on Sunday morning. The rest of the window produced one release.

GitHub opened a critical incident at 09:16 UTC on 13 Sep and resolved it at 10:45 — 1h 29m of degraded availability across API Requests, Issues, Pages and Pull Requests. GitHub has promised a root cause analysis and has not published one yet. Anything that drove the GitHub API through that window — CI, review bots, agent harnesses that clone, comment or open pull requests — failed inside it.1

OpenAI logged three incidents in the same 24 hours, all resolved and all short: Codex GitHub Review and pull request failures, 0.5h, minor, from 09:26 UTC Sunday; elevated errors for ChatGPT users in Europe, 0.9h, minor, from 16:56; and elevated error rates for Codex and ChatGPT Work, 1.2h, from 02:46 UTC this morning, impact recorded as none.345

Use it

Nothing to install beyond Cline desktop 0.0.27. Re-run any GitHub-dependent job that failed between 09:16 and 10:45 UTC on Sunday before you spend time debugging it.

Sources

  1. GitHub status — Incident with several GitHub Services (critical, 09:16–10:45 UTC 13 Sep) · read
  2. OpenAI status — Codex GitHub Review and Pull Request Failures · read
  3. OpenAI status — Elevated errors for ChatGPT users in Europe · read
  4. OpenAI status — Elevated error rates for Codex and ChatGPT Work · read
Originally part of the 14 September 2026 edition.

The useful part, in your inbox.

One complete edition every weekday, with practical takeaways.