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:

• 
  Aries Spring (@AriesSpring__) reported 47 seconds ago

  @nicklaunches @launch_llama Github auth not working, when authing with x, it gets stuck in a loop of email verification -> sends you code on email -> you submit -> you get that prompt to verify email again -> repeat

• 
  Chaitanya Shetty | Tech Partner For Your Products (@thechaicoder) reported 2 minutes ago

  TLDR -> Plan with Opus + MoSCoW -> Skip slow design loops, build in Lovable -> Build 70-80% there, then move deeper work to Cursor -> Run security scans before GitHub sync -> Connect tools via MCP (especially Supabase) -> Use Supabase for backend + auth + realtime -> Run AI review + launch checklist -> Deploy on Vercel -> Outcome: faster Product validation on lean budget This is how we ship 50+ Products. Build smarter. Build faster. Stay structured.

• 
  gitbankbot (@gitbankbot) reported 6 minutes ago

  open source contributors solve real problems. they should get paid when those solutions land, not after three follow-up messages. gitbank automates the full bounty flow on Base L2. maintainer sets a USDC amount on a GitHub issue. contributor merges a qualifying PR. smart contract releases the funds automatically. the payment is as reliable as the CI pipeline.

• 
  Dharan (@DharanGanesan) reported 8 minutes ago

  A single GitHub issue got 27 pull requests from AI bots. Most were untested. Some hallucinated entire implementations. The real contributors? Buried under noise. The fix is a *** hack most devs don't know about. GitHub's "Limit to prior contributors" setting blocks everyone who hasn't committed before. But you can whitelist real humans with *** commit --author using their noreply email. Credits them, doesn't need their SSH key. We built systems assuming contributors are humans. AI bots exploit that because GitHub can't tell the difference. Maintainers spend hours cleaning AI slop instead of reviewing real code. This is a maintenance crisis nobody wants to name. #AI #OpenSource

• 
  OLA EVANS (@EvanzzSznn) reported 11 minutes ago

  @Vheeki_tori @nwidele After opening iLoader, login with ur Apple ID then u will see Sidestore inside the iLoader click on SideStore and it will Install on your iPhone….then all u need to do next is go to Github and download the apps IPA files and install them using SideStore

• 
  rohan (@rohandevs) reported 11 minutes ago

  overheard in sf: is the wifi cooked or is github down?

• 
  Dave Barnwell (@dave_barnwell_) reported 12 minutes ago

  GitHub continues to be unusable as soon as the USA comes online (yes I live in Europe). It is time to quit GitHub, a platform that has served me and many devs well. Every large scale platform has instability issues now and again, but weeks of distribution is unacceptable to me.

• 
  Peter Fox (@peterfox) reported 16 minutes ago

  Today's the first day where I've really seen just how clumsy and poor the UX of @github is. We really need a better way to work. If more effort was put into the UX instead of stuffing AI in, we wouldn't have this problem.

• 
  Ayushman Mallick (@AyushmanMallick) reported 20 minutes ago

  6\ Why does ESMFold2 overestimate confidence on disordered regions? From what I understood after reading their Github repo and biohub, its a calibration issue rooted in training objective. It is built on ESMC a language model trained on 2.8B sequences to predict masked tokens.

• 
  Hasif (@hasifdev) reported 24 minutes ago

  @github China is going down!???

• 
  Ethan (@DuoEthan) reported 27 minutes ago

  GitHub Copilot shipped before ChatGPT. Microsoft had the distribution lead, the developer relationships, the code repositories. It looked insurmountable. Here's the read on what went wrong: Copilot optimized around code generation, right as the market decided context management was the actual problem. You can have a two-year head start and still build for the last problem. Microsoft Build is June 2. They're shipping their own model. And also putting Claude in Copilot, which is a tell.

• 
  Vinay ⚡️ (@VincentAyorinde) reported 27 minutes ago

  Fix 5: Scan with Zizmor pip install zizmor zizmor .github/workflows/ Catches dangerous configs, script injection risks, and overly permissive tokens before they reach your main branch. Free. 2 minutes to set up.

• 
  Yashasvi (@_iamyt_) reported 28 minutes ago

  The problem: I had 6 tabs open just to check my own progress. GitHub here. LeetCode there. Codeforces somewhere else. Internship emails buried in Gmail. DevMirror pulls it all into one place — and actually tells you what to focus on.

• 
  Blessed_Patriot_2011 (@jwm_anacortes) reported 28 minutes ago

  @github my account is getting 404 errors on all my repositories on both web and ***. Support (ticket number 4402135) closed my ticket saying there are no restrictions but nothing has been resolved. PLEASE escalate!

• 
  Tosin Olugbenga (@TosinOlugbenga) reported 32 minutes ago

  I FIND A BETTER WAY DEPLOYING NEXTJS APP ON MY VPS. We were burning CPU, RAM, and ~10GB of disk on our VPS every deploy building a large Next.js app directly on the server. So we changed the model: Build on GitHub Actions → push to GHCR → Dokploy pulls and runs. No more yarn build on production. Deploys went from 15–20 minutes (when they didn’t fail) to seconds. What changed: → Server = run containers, not compile code → Same image from staging (:release) to **** (:production) → Rollbacks = pull a previous tag → Freed ~10GB from old BuildKit cache alone Same app. Cleaner ops. If your VPS is still building Docker images on every push, you might not need a bigger server — you might need a different pipeline.