Timeline

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. Nov 04, 2026 - 11:50 UTC

Monitoring -The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 04, 2026 - 11:43 UTC

Update - The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability. Nov 04, 2026 - 11:30 UTC

Update - We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available. Nov 04, 2026 - 11:17 UTC

Update - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 04, 2026 - 11:11 UTC

Update - We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation. Nov 04, 2026 - 10:38 UTC

Update - Pull Requests is experiencing degraded availability. We are continuing to investigate. Nov 04, 2026 - 09:53 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate. Nov 04, 2026 - 09:50 UTC

Investigating - We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests Nov 04, 2026 - 09:49 UTC

Forges are great for OpenSource software but for closed source/commercial groups in an agentic world I think (ultimately) all you'll need is a git remote with:

  - access control (gitolite or similar) + key management (small webapp or api)
  - branch protections, there's no prior art that I am aware of but hooks can be used for this)
  - CI can be done by hooks as well, probably dispatching into a queue.

You don't really need PRs, agents can review the branch, humans review evidence. You probably don't need Wiki's or GH Pages or Discussions.

You might use tickets, but they make cross repo planning and tracking difficult.

Hell, you probably don't need Confluence or Jira since docs and tickets should be in the repo itself (self contained state for agents). I am working on tooling for this... (an experiment!)

Outages are one thing, but for the past couple of weeks even when everything is green, about 30% of pushes/pulls just outright fail.

I've been relatively tolerant of the outages, but this is constant and really intolerable, to the point I'm actively migrating projects into our internal company GitLab.

I really hope they can sort their shit out.

Edit: while ! git push; do sleep 5; done

I completely lost my carefully drafted PR message. Aaargh. Now I'll always back it up as a copy in the future. So bloody annoying, at least they should store the draft in local storage somehow in my browser.

Ah, must be a day ending in Y

At this point, we can start modeling their internal systems. GitHub itself is up, their loadbalancers are still forwarding web requests, but the key checking service is having a bad day.

Same here. Glad it's not me, and my team in Spain.

Github still not working and causing delays.

Works here (using the desktop app), Asia area

Fetches and clones failing. EU.

And it is down again... https://www.githubstatus.com/incidents/h02n9572mx9y

Maybe they should ban AI.

same here, i get

` ! [remote rejected] main -> main (Internal Server Error)`

Works here.

Some more discussion: https://news.ycombinator.com/item?id=50363378

+1

[flagged]

[dead]

[dead]