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:

• 
  Alexey Grigorev (@Al_Grigor) reported 3 minutes ago

  @igama The problem is supposedly not GitHub but *** being not the best fit for agentic coding I actually like GitHub and I'm okay with using worktrees for the agents, but maybe I'm not seeing something

• 
  A Concerned Human (@inner_concerns) reported 4 minutes ago

  @CorpsTigris @github This seems to be a common problem that Miro also has

• 
  alias (@loadingalias) reported 4 minutes ago

  @tdoot_ @legit_internet @mgill25 Yes, this is a solid top-level starting point, but when you dig into it you realize right away that the issue is so much deeper. GitHub is a monster of inefficiency. Every code change moves 10 knobs/triggers/etc. You can fix this, incrementally, at least… but the moment you assemble anything remotely close to a working GH you’ll see that you’re shifting the issues that today - they’re just fundamental blockers in software. Fragmentation is the bottleneck. It is now, and it will be in the future for things like this. In order to solve it, you’re blocked on SMR… why is a whole deep dive into systems, memory, etc. The short version is you cannot reliably collapse complexity into a smaller subset of complexity without the ability to do so semi-affordably, and at scale. This always lands on memory reclamation; query language bottlenecks (SQL is dying to be retired, it’s worked long enough). It is a really tricky issue. I’ve written about it in a personal “diary” a few times and I thought the other day - maybe I should break it down and post it. I might do that. Idk. I’m so busy.

• 
  Azzle (@AzzleAI) reported 6 minutes ago

  @GitHubCommunity, we’d really appreciate your help in raising awareness about this. Both our profile and repo are showing a 404, despite our work being merged into known projects’ skill libraries like @bankrbot. We also didn’t receive any email from GitHub about any issues with our account.

• 
  VardhanInsights (@harsh_sing91766) reported 7 minutes ago

  India’s I4C orders GitHub to take down Jack Dorsey’s Bluetooth-based app Bitchat, citing security risks. The tool, used by Delhi protesters during internet shutdowns, now faces the same fate in India as in China. #CyberSecurity #TechPolicy #StudentProtests

• 
  ZomboDB (@zombodb) reported 7 minutes ago

  Whenever GitHub is down I smoke meat.

• 
  █ (@0xDGraM) reported 12 minutes ago

  @AUTOMATEWITHOLA lol been around for long and you should also add that you need a high end pc to run it locally or else it will be too slow You are just not updated it’s nothing new A lot of things are open sourced on GitHub already

• 
  Sakti Prasad Bagchi (@saktibagchi) reported 13 minutes ago

  @exploraX_ Solid curation. The real value here isn’t the list of 50 — it’s the repeated reminder not to install them. Most teams I see still treat MCP like a plugin store. They connect 12–15 servers, then wonder why the agent gets slower, more confused, and starts making worse decisions. The “3–5 sharp picks” rule is the part that actually matters. For engineering teams the high-leverage set is still pretty clear: GitHub + Context7 + Playwright + Sentry + your primary database (Neon/Supabase). Everything else is situational. Also appreciate the security framing. Treating every MCP server like an untrusted CLI is the right mental model, and still far too rare. Good reference piece.

• 
  Common Woe (@commonwoe) reported 16 minutes ago

  @CynicalPublius You can't just build an opinion about a generation on one thing alone. My friend's dad and my friend are both engineers. I'm telling you this story because my friend and I used to do a lot of things, but now I never see him because he's always working. Same job he's ever had. His dad started work at 9am and ended work at 5pm and drove home. There was no AI. All his meetings are face to face. Some work is done on computers, some using pen and paper. His dad has a PE and untouchable at work. Seniority results in more pay. On retirement he gets a pension, and the company pays his and wife's healthcare premiums for life. He bought his house for 150k but it's paid off. His son works 16-20 hours a day. He has to compete with offshoring, so he does it by working multiple shifts. Soon as he turns off, teams in India are siphoning work and roles from his team. There is no off button for work - they can call his cell, they can ping him on Teams, email, Yammer, SharePoint (ticketing), Jira, and various other work tracking systems. Before AI teams could take his word on how long tasks take. Now with AI, every task shouldn't take longer than an hour. Got a problem to solve? Why don't you punch it into Copilot in the OS? Put it into Github Copilot? Write a quick CLI query for OAI and Anthropic models in Azure. Solve that problem, then solve 100 more problems because now you're more productive. By the way, for every vibe coded solution, now you have to assign agents to test the solution, plug vulnerabilities, minimize tech debt. Seniority means nothing. If he's too old, his company will fire him on the spot. Age and experience have no value in engineering anymore. When he retires, there's no pension because no other company offers it and his company doesn't care to go the extra mile. Forget about healthcare premiums being paid, go get on the Obamacare exchanges and good luck. He bought a house that costs 550k, less than 2k square feet, half the size of his dad's house and in a shittier location. You think just because he can get better tasting food his life is easier? You really haven't thought about the whole situation. You're judging it all wrong.

• 
  Megacollins (@Megacollins) reported 17 minutes ago

  It looks like magic, but Google Authenticator is basically two devices independently solving the same puzzle. Imagine you and I secretly agree on a number and a rule. We both have the same secret, and every 30 seconds we use that secret plus the current time in the exact same calculator to produce a temporary number. I have the calculator on my phone. You have the identical calculator on your server. At 10:00, my phone calculates 389125. Your server does the exact same calculation with the same secret and the same time window and also gets 389125. I don't have to send you anything. You already know what my phone should have produced. That's essentially what Google Authenticator is doing. When you enable 2FA on Google, GitHub, Binance, etc., the site generates a secret key and shares it with your Authenticator app, usually through the QR code you scan. Your phone stores the secret. The server stores the same secret. From then on, whenever you need a code, both sides independently combine: • The shared secret • The current time • The same TOTP method to generate a 6-digit code. So when your phone shows 389125, the server independently calculates what the code should be. You type it in, the site checks whether it matches, and you're authenticated. Your phone doesn't need to be connected to the internet to generate the code. That's why you can put your phone in airplane mode and still generate a valid Authenticator code. The little countdown circle simply shows how much time is left in the current 30-second time window before a new code is generated. And what can make a genuine code fail? • You enter it after the server's accepted time window. • Your phone's clock is significantly out of sync. • You scanned the wrong QR code. • You're using the code for a different account. • The site's 2FA secret was reset or changed. Most services also allow a small tolerance for clock differences, so being off by a tiny amount doesn't necessarily invalidate the code. But there's no mysterious signal travelling back and forth between your phone and the website. It's simply: Same secret + same time window + same method = same temporary code. Two completely disconnected devices can independently arrive at the exact same answer. That's the real "magic" behind Google Authenticator. Good tek.

• 
  Tal Ohana 👨‍💻 (@talohanax) reported 19 minutes ago

  @mattpocockuk @saidelike Same for me, also when trying to use this link (signing-in with Discord/GitHub also broken for me)

• 
  AgiBy2030 (@AsiBy2030) reported 22 minutes ago

  @gdb Cool. GitHub plugin fix wen. It doesn't work

• 
  Stats Wire (@StatsWire) reported 27 minutes ago

  What's your MCP server stack in production? Mine: Postgres MCP + GitHub MCP + 2 custom. Curious what others are running.

• 
  Ruslan (@Ruslan_onX) reported 31 minutes ago

  @sattyyouneed Push it to GitHub that connected to Vercel = problem solved

• 
  raulk (@raulvk) reported 31 minutes ago

  and you folks wonder why GitHub is down all the time if I were GitHub, I’d self-destruct before having to stomach stuff like this