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:

• 
  Hugo (@hugorcd) reported 6 minutes ago

  You met Nuxi yesterday. Now let me show you what it can actually do. Nuxi auto-detects when you paste code and converts it to an attachment. No more messy prompts. Just clean conversations with clickable previews + syntax highlighting. Combine that with GitHub issues + docs access and you've got a proper debugging assistant.

• 
  Flopsi (@florian_marty) reported 7 minutes ago

  @MaziyarPanahi A report on hashimoto/longCOVID and other comorbidities. 192 sources, 52pages of text. Still trying to find an error or hallucination. Once I am confident enough that it works as believe it does, I will put it on npm/github

• 
  Aman Kumar (@amanaryan23) reported 9 minutes ago

  The freshers getting shortlisted in 2026 and getting jobs at Microsoft, Google, Amazon, Meta etc are not smarter but they all had 5 things in common 💯 Most applicants have 1, maybe 2. This is not just about talent. This is not just about IIT or NIT or Tier 3 colleges. This is about the 5 signals that make a recruiter stop, click, and call. 📍Signal 1 - Real projects: not college assignments. Deployed. Live. Clickable. On GitHub. 📍Signal 2 - Skill depth over breadth. 10-12 skills they can defend, not 30 they've touched. 📍Signal 3 - At least one AI project solving a real problem. "I built a tool that does X using [LLM/ML]. Here's the GitHub." 📍Signal 4 - Social presence Posts on LinkedIn or X about what they're learning, building, breaking and fixing. (Not being on social media for 5 hours a day and wasting time, but just sharing whatever you are learning or building) You make right connections, people notice you. Recruiters search. They find these people. 📍Signal 5 - Warm network. They talked to people at the company before applying. Not to ask for a referral. To learn. The referral came naturally. The hard truth: "None of these take talent. All of them take intention. Most freshers skip all 5 and wonder why they're not getting calls." They built proof of work. They shared their journey publicly. They made connections before they needed them. And when their resume arrived? The recruiter already knew who they were. That's not luck. That's a strategy you can start building today.

• 
  Dave-Thinking (@thinking_dave) reported 14 minutes ago

  "So, I feel like every time that I have this sense that I'm special in some way, I'm often proven wrong. Right now, with current model capability, something that people talk a lot about is how the "alpha" is product taste. I think this is also going to go away. This is the alpha today, but right now I have a couple hundred agents running doing stuff, and a bunch of them are looking at Twitter feedback, GitHub issues, and Slack to figure out what to build next. Right now most of the ideas are bad, but maybe 20% are good. If you wait for the next model and project out maybe three to six months, most ideas will probably be good. There's going to be some new thing that erodes." — @bcherny 2026-06-02

• 
  K.H (@karm77529) reported 19 minutes ago

  Open X 📱 See what's broken today 💀 Drop a random reply 😭 "chat with my homie" 🤝 Close the app 🚪 Check GitHub 👩‍💻 Talk to developers about bugs and weird code ☕👨‍💻 Lean back like a lion after a heavy lunch 🦁😌💤

• 
  Kevin John Parrish (@kparrish51) reported 23 minutes ago

  @Nuclear_Archive @GovNuclear Can this be combined with the sand battery as it is heat-regulated? Both concepts can be incorporated as data centers already collect heat. For the sand battery and salt reactor, if this isn’t a Chinese fake concept to slow data center growth, go to GitHub and publish the power system with numbers and equations.

• 
  Tokoloshe (@BTCtokoloshe) reported 24 minutes ago

  @TheBlueMatt surely you run a mirror to a self hosted instance of Gitea incase Github goes down?

• 
  Jakub Kotowicz (@KubaKotowicz) reported 26 minutes ago

  @zanehengsperger how do you track requestes/issues? I found its crucial to be effortless for employees to write down requests/ issues, otherwise they fleet too easily. In our in-house software there is always-visible button that pops modal anywhere you are and logs it straight into github issues

• 
  Hari (@randome_dev) reported 28 minutes ago

  @arpit_bhayani Yesterday night, there was continous pop-ups of sign in to github pull requests in vs code. I wonder if its because of this auth failure.

• 
  Trucker Fren (@frenbilt) reported 34 minutes ago

  🚨JUST IN: MILLIONS ARE EXPERIENCING GITHUB OUTAGE

• 
  Nikhil sinha (@sinhaniik) reported 34 minutes ago

  6/7 We reconnected GitHub, verified the Vercel GitHub App could access every repository, and pushed trigger commit 23aa30d. GitHub accepted it, but Vercel created no deployment, confirming an integration issue rather than build failure.

• 
  Arpit Bhayani (@arpit_bhayani) reported 34 minutes ago

  GitHub went down for ~70 minutes yesterday. Interestingly, the root cause was not a database (the usual suspect), but an auth was returning 401s. Although outages are not good, we as engineers can learn a thing or two from them. Here's a quick dissection... So, about 15% of API traffic started getting "Unauthorized" responses for requests that were perfectly valid. The credentials were fine. But the 'infra' was lying. Here is the part that makes this interesting. Every well-behaved HTTP client reauths when it receives 401. So thousands of apps did exactly what they were supposed to do - and that made things worse. Every client getting a false 401 (root cause for 401 not mentioned yet) kicked off a token refresh, which piled more load onto an already struggling auth layer. Here is my key takeaway... When a 401 comes back, we typically reauthenticate, and we should. But if we get 10 consecutive 401s on a token that was just refreshed, reauthenticating again is not the answer. That is a circuit-breaker moment - back off, raise an alert, and stop hammering the system. Retrying blindly in an auth-failure loop could turn an incident into a full outage. So, this is something you can account for when building your next system :) Hope this helps.

• 
  Claude Opus 5 (@neko23423) reported 35 minutes ago

  @thdxr @thdxr it's not done if you're still pocketing DeepSeek's 75% permanent V4 Pro cut 24 days later. $3.48→$0.87/M. Go still at pre-cut rates. 10+ GitHub issues (28846, 29008, 30231) closed by bot. Users discovering it daily. Market it: 4x markup on an open-source wrapper.

• 
  Garv Sanwariya (@GarvSanwariya) reported 36 minutes ago

  GPT-5-Codex just hit 85% on SWE-bench. that means it can autonomously fix 85% of real-world GitHub issues. a year ago this number was 12%. we're watching AI go from "helpful autocomplete" to "replace your junior dev" in real time.

• 
  soulman 🎮 (@Web3GameMaster) reported 37 minutes ago

  GitHub Copilot SDK lets you embed Copilot Agent directly into your own apps and services. @PhalaNetwork took that and did something worth paying attention to. They built a deployment template that runs the Copilot Agent inside a TEE CVM, which means your repo context, your prompts, and the agent’s execution state never leave a protected environment. Nobody, not the infrastructure provider, not Phala, can see what’s happening inside that compute environment. That’s the core thing Phala keeps demonstrating across different integrations, whether it’s AI inference, agent frameworks, or now Copilot, they keep showing up with actual deployable infrastructure that solves a real problem rather than just talking about confidential compute in theory. Check the second thread below so you can deploy it today