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:

• 
  Mate Gal (@555kindofguy) reported 3 minutes ago

  @survivetheark Guys put game files on github repo and we’ll fix it, you verify it and deploy

• 
  doublemover (@doublemover) reported 3 minutes ago

  Damn codex github issues are becoming a ****** garbage dump. Some ****** retard has what I can only assume is openclaw chiming in with useless bullshit on every issue

• 
  Bollish (@99_Bollish) reported 6 minutes ago

  @King_Memento That’s exactly what I’ve started noticing too. The funny part is that nobody gets angry when someone shills a larp. People only get angry when someone points it out. A larp project can waste thousands of hours of attention and millions in volume, and somehow that’s acceptable. But the moment someone opens the GitHub, checks the docs, and asks questions, suddenly they’re “ruining trades.” At the end of the day, fake utility projects don’t just hurt buyers. They also steal attention, liquidity, and volume from teams that are actually building. And i've already accepted that some people will hate it. If exposing a larp ruins a trade, maybe the problem isn’t the exposure. Maybe the problem is the larp. The market gets healthier when capital flows to builders instead of storytellers.

• 
  Nebojša Obradović (@Nebojsa_Galilej) reported 7 minutes ago

  @AnthropicAI I was charged $58.58 in a few hours due to a known bug in Claude Code v2.1.161 (GitHub issue #40524) that inflates token usage ~40% through broken prompt caching. Support says API credits are non-refundable even when the overcharge is caused by your own software defect. Is this really your policy?

• 
  Sam Thapa (@SThapa123456) reported 8 minutes ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. want it shorter, or is this length working for the thread you have in mind? (credits to claude for articulating this for me)

• 
  Zypheen (@Zypheen_) reported 11 minutes ago

  @robdezendorf fix dex screener and link your profile and github, someone random paid dex and linked a drainer. dev or someone fix this plz ES6ZcfTUTVET37RaYW9qDhX1DBBDEaTuvg87Lw9epump

• 
  Stackcrafted (@Stackcrafted) reported 13 minutes ago

  PewDiePie’s recent project with 45,000+ stars on GitHub is being drowned in PR slop from LLM coding agents. When automated PRs pile up like this, security becomes harder to guarantee. Review gets noisy and it only takes one missed change to introduce serious auth or access control issues.

• 
  LeslieT (@TLeslie__) reported 13 minutes ago

  Can't launch my tech start up because @Microsoft is garbage and won't fix its systems. From github to windows to vscode I have to be migrating because Microsoft doesnt care

• 
  Dawid Skinder (@DawidSkinder) reported 16 minutes ago

  Use it. Share it. Stress-test it. If something is wrong, missing, outdated, or unclear, open an issue or pull request on GitHub. Terra Classic needs public infrastructure that the community can improve. 13/14 🧵

• 
  Jimmy Koppel (@jimmykoppel) reported 18 minutes ago

  @JongwonPar9958 I see. So your result basically counts Github issues over the lifespan of the project?

• 
  Imran (@imranity) reported 22 minutes ago

  @github is broken ...

• 
  EleanorFang (@Eleanor42032721) reported 23 minutes ago

  Hi vibe coders, Do you actually use GitHub to back up your projects? As someone with no coding background, I find GitHub surprisingly hard to use. 🤯 Anyone else having the same issue?

• 
  Chelm's Deep (@ChelmsDeep) reported 25 minutes ago

  @plainionist @PaulGugAI This actually works ridiculously well. Was having problems with recurring errors and debug loops. I harvested information from some github repos built in the same stack, added a skill to read the knowledge base and search the repos, fixed 12 issues on the first turn.

• 
  MoaddebSepideh-IIvyOnassis55320 (@MoaddebSepideh) reported 26 minutes ago

  When will you release my yahoo account because I gave my passwords to Musk as Doge, and now I am really sorry I did that. I have a problem with Github X. I doubt they will insert the ideology of Quantum as a piece of process for the State Department to know that @SenatorBlinkin. And also @Forbes are both with other business's are in my Yahoo. Account. This is hijacking of the Doge, and I believe the hijacking is personal right now. With the people who have assited me in the power of to be I have much respect for the men in the process of hearing me out. After the Law exam, there will be a Law suit. It will be big, and I am the center of it. I will sue myself based on a discrimination, Men, pregnancy and a lot more issues clamness, you will be in court-I think for sure as will the Men of the orign of the Swiss Alps knowing the promise is not the evasion but it's the clamness not the ***** of Quantum to a degree they have made a big mistake of the plans I have for not allowing me to see what I wrote for LSAT and also for Grossman.

• 
  AIDegen (@nrsvv11) reported 26 minutes ago

  A Chinese developer posted a 41 second video on Bilibili showing the dashboard for his one person company. 19 autonomous AI agents handled everything 30 human employees used to do. Electricity bill: around 600 dollars a month. He pointed at the grid of cards on his monitor. Researcher. Copywriter. Designer. Developer. Sales. Support. Checker. The system ran 24 hours a day. He approved decisions from his phone on the subway. A laid off mid level manager at a Shenzhen electronics factory recognized the cubicle in the wider shot. He sent one screenshot to a Bilibili tech forum: timestamp 0:23. Pause at 0:23. Ignore the dashboard. Ignore the Dell monitors. Look at the giant union sign on the shelf in the upper right corner of the frame. That sign is not a decoration. That is the entry sign of his old employer's union office. The cubicle in the video was not his apartment. The cubicle was the corner desk in the union office where laid off workers came every morning for free coffee and wifi. He had not built a one person company that replaced 30 employees. He had been one of the 30. The company had laid him off six months earlier when they bought a SaaS platform that did eighty percent of what his department used to do. The 19 AI agents were real. The agents were also a demo. He had been running the system for himself for six months. He had pitched it to his former employer twice. Both times they had passed. The Dell monitors were not his. They belonged to the union steward's desk. He used them every morning from 9 AM to 1 PM because the union office had air conditioning and his apartment did not. The 600 dollars a month electricity bill was real. The electricity was the union office's. The union steward had agreed to let him plug in his local server in exchange for him helping ten other laid off workers polish their resumes. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The laid off manager had been one of them. He had built the 19 agent system on top of that fork as proof that the company that fired him had been wrong about him. He was not a founder demonstrating the future of one person companies. He was the first laid off middle manager in his city to figure out the only way to win the AI replacement argument was to present yourself as the one who pressed the button. The clip is at 2.1 million views. The zoom on the union sign got another 1.6 million. Chinese tech viewers are still sharing the video. Still nodding. Still asking how to license the system. The system is still running. The cubicle is still at the union office. He still has not heard back from his former employer. He told the internet he had replaced 30 employees. The 30 employees he claimed to have replaced included him.