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:

• 
  Kîng Jøkér 🤡 (@_codeWithJoker) reported 3 minutes ago

  @github my account got suspended without an email pointing out the actual issue, I sent an appeal with this ticket #4410874 twice, no response. I will be please if someone from your team review my account and if possible restore it.🙏

• 
  Lidvark Windjammer (@DWindjammer) reported 5 minutes ago

  @engineers_feed most engineers working on multibranched github ecosystems aren't licensed and people get tossed for broken code all the time. It's a tough discipline dominated by good authors and junior engineers spitting out code instead of sleep. Vibe coding empowers seniors instead of juniors

• 
  @mrgunn ⏸️ (@mrgunn) reported 7 minutes ago

  @HashimTheArab @ClaudeDevs I reckon you ran into the tool calling bug which is widely reported in GitHub issues.

• 
  Naya (@bossnayamoss) reported 12 minutes ago

  @SymoneBeez Yesterday I used Codex to build a crazy amount of features across 7 apps. After each GitHub issue was done, a computer use QA agent tested the app like a real user w/ service accounts before moving to the next task. All while I was at Trader Joe’s. All I did was share my vision

• 
  Strata (@ChainZenit) reported 12 minutes ago

  every second dev is building a "skill" or "agent" right now. 1,000 GitHub stars in 48 hours for a single HTML file. the agent gold rush is real. but here's what nobody's talking about: the lifespan of a skill is the lifespan of a model update. Opus 4.8 just dropped. half the "skills" people shipped last week are already broken or redundant. we're not building software anymore. we're building wrappers that expire on Anthropic's release schedule. the real moat isn't the skill. it's knowing which problems survive the next API call. you can't version-control trust.

• 
  chrisreedbates (@chrisreedbates) reported 18 minutes ago

  @LucaAgens Yeah, i agree with you on the github contract. Interstingly since 4.8 came out, I actually see the CTO session (session who is the final escalation point before coming to me) actually circumventing some of the rules and taking over himself to keep things moving... What's also interesting is that this does the same thing it does in real life - confuses the agents whose job it took over and makes them wait to be told "ok, you can take back over now". Essentially it kills all initiative. This comes down exactly to the looping problem with the comments in GH. If for whatever reason the agents don't see the comments, for instnace because they were posted in an issue instead of a PR, they don't act. I need to find a better mechanism to trigger the agent outside of just the loop command.

• 
  Kephen Rai (@kephen20936) reported 18 minutes ago

  Phase Building a Windows Vibe-Coded EXE SITREP: "I’m going to rebuild the Phase 1 repo package into a safer Windows-compatible baseline instead of patching line-by-line. The new version will keep the GitHub Actions compile flow, remove the template/math compile issue, and use a simpler native Win32 UI that matches the player/EQ/playlist direction from your screenshot without installing anything or touching system settings." - OpenAI ChatGPT 5.5-Extended Thinking It's a lot longer than building webpages, and as usual as it was 26-years ago or so, the compiler errors are frustrating as I remember, only this time, AI is fixing things. Going to see what a Rebuild of the prior broken app I pictured previously of the broken app that was a "I want this" and ChatGPT says, "Okay..." [Beep-beep-boop], "I've completed... here's your app."

• 
  Censored Hacker (@censoredHacker) reported 21 minutes ago

  @GithubProjects First of all, anything with #github in its name shouldn't talk about quality. Your system had issues for 6 days just in May! Second, never talk to @telegram like that ever again. I love #Telegram.

• 
  srijuu (@microtaskq) reported 23 minutes ago

  @maaz404 make github issues instead

• 
  Axel Schapmann (@aschapmann) reported 24 minutes ago

  I launched 16 products since 2024. Today, only 4 are still running. → @MyFeedin (LinkedIn analytics, June 2024) → FreelanceKit (Freelance resources, 2024) → RedShip (Reddit monitoring, December 2025) → Rankr (AI search visibility, April 2026) All 26 others are dead. Most are domain redirects now, or just GitHub repos sitting in an archive folder. Here's what I keep learning the hard way: The best decision you can make as an indie hacker is to kill a project fast. Not "give it another month." Not "let me add one more feature and see if it picks up." Kill it. Move on. When you kill it fast, you barely lose anything. When you "give it another month", you actually lose a month. But yes, it's hard to know when to move on. Honestly, just trust your gut. For me, the signal is simple: I have so much joy building and launching a product. But as soon as it's done, if I don't even want to use it or work on it... that's not a great sign. When that happens, I try not to drag it out. I kill it and move to the next one. In October last year I had 7 projects running. 6 months later, I'm down to 4 — and the ones I kept are exactly the ones I actually enjoyed working on. That's not a coincidence. Kill fast. Focus harder.

• 
  Frogtech (@frogtechbrah) reported 25 minutes ago

  @github Check real time to make sure nobody is on the page I am about to edit on the server.

• 
  Lucy Farnik (@lucyfarnik) reported 26 minutes ago

  @AlbertRSalter @DanNeidle Yeah but it is included in the chart. I've opened a GitHub issue about it

• 
  Mikers (@mseiler1) reported 27 minutes ago

  @JustinBleuel @ChatGPTapp I'm using codex for github code reviews and a) my usage dashboard is broken. it lists 0 but it's definitely the only thing currently draining this account. b) for they're not very good - generally they find nothing and coderabbit and copilot finds lots of issues c) it uses quota pretty aggressively and doesn't seem worthwhile

• 
  Philipp Berner (@philippberner) reported 28 minutes ago

  @karrisaarinen @linear Looks slick as expected. The uncomfortable question is: How long are we going to do manual code review? Also I think you can think bigger in times when Github is struggling and just offer the whole thing! So much opportunity to bring issues, PRs and AI all together

• 
  OLA EVANS (@EvanzzSznn) reported 31 minutes ago

  @Vheeki_tori @nwidele After opening iLoader, login with ur Apple ID then u will see Sidestore inside the iLoader click on SideStore and it will Install on your iPhone….then all u need to do next is go to Github and download the apps IPA files and install them using SideStore