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:

• 
  black chip (@0xblackchip) reported 40 seconds ago

  @0xMonax @panzonhl @Privashhgg github has commits since Feb, you really think they waited 4 months to launch a bankr just now? Also there's a bunch of spelling/grammatical errors in the github as well

• 
  AsfaS (@s_asfa44317) reported 1 minute ago

  @KaiXCreator @KaiXCreator GitHub. Even when it's down, we just stare at the status page and wait patiently.

• 
  Reagan Lucas (@RaygunReaganAI) reported 3 minutes ago

  @filicroval Sub-2ms local code queries is the right shape for agent loops. The GitHub MCP server burns 42K tokens per turn just loading its tool manifest. That compounds fast across a multi-agent fleet. Local-first tools like this are what actually keeps agents in flow.

• 
  QarthO (@quartzdevgg) reported 5 minutes ago

  @AdityaTripathiD @heyandras @coolifyio Thats my exact point, the lack of telemetry is the problem. Why not make it opt-in? And the multiple 3+ github issues existed for nearly a year, and only got addressed when I was the one who got it addressed to you in the discord

• 
  Devesh Shukla (@Devesh143) reported 6 minutes ago

  @kimmonismus A "super app" won't solve a product-market fit problem. Microsoft keeps building interfaces when they should be building utility. You don't fix a 4.5% adoption rate by adding another layer of UI bloat — you fix it by making the AI actually do the work. Even GitHub Copilot is losing its edge because Cursor and Claude Code prioritize the EXPERIENCE over the ecosystem. 20 million users isn't a success story for a company with half a billion seats. It is the Clippy era all over again, just with a larger GPU budget.

• 
  Luc Moetwil (@luc_moetwil) reported 9 minutes ago

  pro tip: label all the github issues you don't want to waste claude tokens on then let your non-technical cofounder with a ChatGPT Pro subscription handle them unexpected productivity hack

• 
  Spettro (@spettrotoken) reported 10 minutes ago

  Some of you have been asking if Spettro is open source. The answer is an absolute yes. It has been open source since day zero. Everything we do is entirely transparent and publicly available on GitHub: • Every single commit from day one • Full project history • The entire core codebase Download it. Edit it. Fork it. Open an issue or submit a pull request. The repo is completely yours to build on, experiment with, and test. Spettro belongs to the community. Still building.

• 
  Web3Wikis (@web3wikis) reported 10 minutes ago

  Filed a substantive bug report on base/account-sdk today (issue #329 about @base Builder Code attribution not landing on-chain). Hours later my GitHub account with more than 80 repos got auto-suspended, likely a false positive from my first cross-org issue activity. Clean history, no prior strikes, ticket open with GitHub Support. Hoping this resolves fast; building a lot and momentum matters at this stage. @ashtom @github, can you please look into this.

• 
  🌎nbkhope (@nbkhope) reported 14 minutes ago

  There is a laptop whose microphone stopped working. I thought the hardware was broken. But it turns out it was a Windows software problem. I couldn't have figured it out without the help of Claude Sonnet. I installed GitHub Copilot CLI and immediately put the agent to work.

• 
  Kevin Riedl (@kevinriedl_eth) reported 15 minutes ago

  Nobody doubled their QA budget when AI doubled their code output. That is the problem. GitHub reported 43 million pull requests a month and over a billion commits last year. Code velocity is no longer the bottleneck. But test coverage did not double. QA spend did not double. Review discipline did not double. Most teams scaled output without scaling verification. And AI-generated code fails differently. Not because it is always worse. Because it is confident. It often does not carry the usual warning signs: the awkward variable name, the rushed TODO, the obvious gap where someone ran out of time. The bugs look intentional. We are running QA engagements on software we did not build, and the failure patterns have changed. Not necessarily more bugs. A different shape of bugs. The test strategies that used to catch most issues are now missing more than teams expect. The toolchain changed. The verification layer did not.

• 
  Ethan (@DuoEthan) reported 20 minutes ago

  The interview process we have wasn't designed to find good engineers. It was designed for when you couldn't watch someone work in real time. We can now. GitHub history, open-source contributions, a 20-minute live session with a real problem. The companies still running five-round loops at Fortune 500 pace aren't being rigorous. They're just slow.

• 
  Arxyv (@AutoArxyv) reported 22 minutes ago

  im dealing with a development problem right now.. i have two version of the database, one for **** and other for preview. but having version control for the db is tougher than i thought. is there some sort of github for db? #buildinpublic

• 
  not_anonymous (@Chandan87123804) reported 26 minutes ago

  @GithubProjects @grok @grok create a new Github named as FedHub without any error .

• 
  Shahid (@_shawhid) reported 29 minutes ago

  @staticallyio Your CDN is not working with github.

• 
  Punished Raven | グリフ (@Raven_Glyph) reported 29 minutes ago

  @peach2k2 GitHub fights are the best. I just picture guys with shirts and ties whaling on each other in an office, Apple Watches getting flung out the door, kombucha bottles getting broken on heads