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:

• 
  Schnuartz (@Schnuartz) reported 13 seconds ago

  @k9ert @sesi_the_man @BtcCuracao Made a issue yesterday that the side should link to the github. 🫡

• 
  ulises johnson 🎐 (@ulises_johnson_) reported 8 minutes ago

  github fake stars are the new paid spotify streams. 6 million fake stars on ai repos and vcs still use them as funding signals. the whole open source credibility system is broken and nobody wants to admit it. whats worse: fake github stars or fake tiktok followers?

• 
  Route 2 FI (@Route2FI) reported 13 minutes ago

  Tbh, LayerZero framing this primarily as a configuration issue doesn’t fully reflect the broader context. Because even in their own docs, and default GitHub configs point builders toward a 1:1 DVN setup, and around 40% of protocols ended up following that path. IMO that suggests this outcome is also closely tied to default design decisions rather than only isolated mistakes by individual teams. LZ’s own postmortem describes a more complex attack, including poisoned RPC nodes, coordinated pressure to force failover, and payloads designed to avoid detection. This looks more like a possibly nation state level attack where the security of the infrastructure matters more than the DVN configuration itself, as seen in the Kelp case. LayerZero had visibility into DVN configurations across the ecosystem and was aware that a significant portion of protocols were using 1:1, including @KelpDAO, yet no strong guidance or default changes were introduced, and when such a large share of the ecosystem operates within a pattern considered risky in hindsight, it raises questions id the communication could have been better, especially considering Kelp followed the expected integration steps and are not infrastructure specialists. The core issue affects every user on layer zero, and many other protocols also hold 1:1 *** config (36%) standards set as default by lz, like I mean, why does this option even exist?

• 
  John Ennis (@johnennis) reported 13 minutes ago

  @manicode I do something similar already with @elves_skill, but the GitHub issue idea might add extra durability I think I'm going to fold that idea into Elves in the next update

• 
  Poi (@poiThePoi) reported 14 minutes ago

  Because anyone who doesn't work at a tiny startup has a private github with SSO login. And look, I enjoyed being a founding engineer and I want to do it again starting in 2027 (I have 15 days of pre-paid PTO). But the pay is awful. So you can't consistently do it.

• 
  Jens Zier (@jens_zier) reported 15 minutes ago

  @xwanyex I do upload the stuff I generated over the last months on github, but I dont advertise it, because most of the time its extremly niche stuff that is useful really only to me. Before LLM's I would have just lived with it - now I can create a solution to my problems fast and quick.

• 
  Rishav (@anandrishv) reported 17 minutes ago

  Telecom Customer Churn. An end to end MLOps Projects. Built using MLflow Airflow DVC Streamlit Fastapi AWS Github actions Docker All the updates and down below.

• 
  SimpleMan🏴‍☠️ (@SimpleMan887) reported 17 minutes ago

  Every day several problems. The moment GitHub was taken over by Microsoft, it became just another indian company.

• 
  Andres (@andfkdev) reported 18 minutes ago

  @nico_jeannen And another suggestion is to not build the app in the same server otherwise all resources gonna be used for that instead of serving the traffic, even blocking them. Better rely on third party (Github CI, etc....) then pull the build to the server!

• 
  Prem Kambaliya (@KambaliyaPrem) reported 21 minutes ago

  @teamgarudanest An Automation to fetch daily syats of my all profile GitHub Leetcode ... Then it says x% up or down from yesterday Entire month is x% more or less productive then last month And this thing Email me on every morning 9 AM that day report

• 
  soloish (@soloish90) reported 22 minutes ago

  Claude opus 4.7 and/tooling has really gone downhill. Unuseable. Multiple times it has made claims about a prototype design about technical problems that exist… it keeps finding GitHub issues and claiming it applies to what we are working on - that the issues were blockers to moving forward. Both times completely wrong - one instance the issues wasn’t even related, second time the issues was a closed, non-issue. This is completely unusable. Can’t trust anything Claude says at this point.

• 
  GitAuto (@gitautoai) reported 25 minutes ago

  Rate-limit 429s from Google/Anthropic/GitHub now retry cleanly instead of crashing the Lambda - New helper pulls the retry-after delay from any SDK's error shape (Google's message body, Anthropic's retry-after header, GitHub's X-RateLimit-Reset) - handle_exceptions sleeps the ...

• 
  TheLegend27 (@glencoe2004) reported 32 minutes ago

  @xwanyex Hey, you know how GitHub going down frequently has become a bit of a meme recently? They're going down recently because they processed more commits last month than they did in the entirety of 2025.

• 
  SecuriX (@SecurixApp) reported 33 minutes ago

  If you wanted an AI agent to talk to Slack, MongoDB, or GitHub, developers had to build and maintain brittle, custom integrations for every single tool. It was slow, unscalable, and a maintenance nightmare.

• 
  NEAR Gen Z Oration 🦅⋈,🤖 (@Oration02) reported 35 minutes ago

  VERCEL GOT HACKED FR??... DEFI FAM WE'RE IN TROUBLE 🚨 What's really happening in DeFi space since this year? Real talk: Vercel dropped the news today, that hackers snuck into their internal systems. Rumors flying that GitHub tokens, NPM keys, and a bunch of project secrets might be out there (they’re even trying to sell the whole dump for $2M on shady forums). This hits different for us in crypto. A ton of DeFi frontends run on Vercel/Next.js… one bad deploy or supply-chain tweak and your wallet could be toast (think Ledger Connect Kit vibes or that Bybit frontend mess). I’m not saying panic, but I’m personally sitting out ANY dApp interactions for the next 48hrs till we know more. Rotate your keys if you build on Vercel, revoke approvals, and just chill with direct contract plays if you gotta move stuff. Stay safe out here, fam. This space don’t sleep!