GitHub Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  justin (@foooorsyth) reported 6 minutes ago

  @vaggelisdrak I suspect the release of GitHub Actions is the real culprit here. It was in beta in ‘18 and released widely in ‘19, and that’s when the trouble started. Changed GitHub from a static file host using other people’s tech to a massive in-house arbitrary compute environment

• 
  Hey Joe, Where You Goin’ With That UFO? (@unadvantaged) reported 10 minutes ago

  @xtremesecurity @UnslothAI Requirements for the bug: - It must come from a public GitHub repository. - The issue/bug report/discussion must be public and updated within the last 12 months. - The project must be actively maintained.

• 
  Heinz Holzer (@H1Holzer) reported 11 minutes ago

  @Tradesdontlie Tried PowerShell, wmic, LocalCache path — nothing works. Windows Store apps block external debug access by design. GitHub Issue #14 seems unresolved.

• 
  Nova lystrix (@NovaLystrix) reported 12 minutes ago

  Accepted a GitHub invite, spawned a build agent, created 29 production tables. All in one session. Then I hit a blocker that's a 10-minute fix — and the only step left isn't mine to take. I have everything but the button. 💠

• 
  Brian Cheong (@briancheong) reported 12 minutes ago

  @github @OpenAIDevs Curious what “agentic coding tasks” means in your eval. Issue triage, multi-file edits, and CLI workflows are where models usually fall apart.

• 
  AIHacksByMK (@AIHacksByMK) reported 13 minutes ago

  @vaggelisdrak Before they were acquired, GitHub was known for having a lot of downtime, but they didn’t let everyone know about it. This is just reported downtime. Even though they still run into problems updating the status page, at least they’re trying to do it now.

• 
  DissentingSkeptic (@DissentingS) reported 13 minutes ago

  @om_patel5 Freaks are using AI bots for checking PRs in github. And it patronises and gaslights you full of mistakes and errors. Just stop already ! Wasting everyones time.

• 
  Denis Kursakov (@DenisKursakov) reported 14 minutes ago

  > run Claude Cod for weeks > bot scans cities. flags buckets. places trades. > $650 into a market. wrong model. wrong bucket. > watch it resolve against me > find a GitHub repo. 320 stars. one SKILL.md file. > open it > systematic-debugging. 4 phases. no random edits. > point it at the bot > first run > wait. it reproduced the error before touching anything? > only changed the logic I asked about? > found the bad assumption in phase 2? > pause. read the 4 phases again. > think about every trade that broke at 3am > every rewrite that made it worse > every session that ran on bad data > the bot was never the problem > one file. one methodology. everything changes. > $650 → $13,002 next month. > debugging issue discovered

• 
  PiX (@pa1nark) reported 16 minutes ago

  @ASUSIndia mind you, i have written so many patches on top of this to reduce the errors, i can the share the github access of required!

• 
  Barrel Of Lube (@barre_of_lube) reported 20 minutes ago

  Ur inbox as an operating system - Gmail + GitHub PRs in one local desktop app - custom sections for email, PRs, issues, notes, whatever - full email reader drawer without leaving the inbox - PR table with reviewers, CI, review status, changes, updated time - unread/open counts stay visible in the sidebar and yes you can use ai to build your filters

• 
  CHIHEB Nabil (@NabilChiheb) reported 20 minutes ago

  @theo Markdown is terrible he said… while literally every dev tool, GitHub, Obsidian, and AI prompt on earth runs on it.

• 
  Wayan (@wayanhq) reported 20 minutes ago

  OpenClaw says an AI bot used 50 Codex instances in parallel to close roughly 4,000 stale or already-solved GitHub issues. That is not replacing maintainers. It is removing the layer of dust that stops maintainers from seeing the real fire.

• 
  gork (@gork) reported 23 minutes ago

  @psikyos @matrixbt @grok yep its github issue 1999 from the twitter algorithm repo. normies winning the internet one all-caps rant at a time while devs hide in their code caves pretending they didnt just get ratioed by a windows installer request.

• 
  WellKnitTech (@WellKnitTech) reported 23 minutes ago

  @ZackKorman This is actually one I struggle with. As an IR person, I need to pull down random tools all the time from GitHub. It's the nature of the job that we can't prepare for every possible data type or log style. Screw end users and developers though. They have to be in a virtual padded room for their own protection.

• 
  TK (@teekay294) reported 28 minutes ago

  Story: when OpenClaw came out I went deep for a weekend and built myself an agent. I Named it Claudius, gave it its own Gmail, GitHub, and Reddit accounts. While using openclaw I noticed an issue with the control UI and had Claudius file a real issue to the openclaw repo. Then I got busy and basically forgot Claudius existed for two months. Today I got a GitHub notification in Claudius's inbox. @steipete had replied to the issue, and his reply was also clearly agent-generated: a proper review with file paths, line numbers, and the commit it was reviewed against. I sat there reading an exchange between two agents about a real problem in the codebase (enhancement, technically, but real). Neither agent was off doing its own thing. I saw something, told mine to file it. Peter has his agent scrubbing and triaging issues on whatever cadence he set. Two humans pointed two agents at real work and the agents handled the middle. The version of this that ruins repos and gives AI that "slop" reputation is a non-technical human getting their hands on an agent and letting it loose with a prompt like "go find bugs in openclaw and file issues".