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:

• 
  Ming (@tslaming) reported 28 seconds ago

  @Squirrel1980021 That is usually the biggest catch with custom solutions, as proprietary protocols often fragment the industry and lock people in. However, the great news here is that Tesla actually open-sourced it to prevent exactly that. They released the entire specification as TTPoE on GitHub during HotChips 2024 and even joined the Ultra Ethernet Consortium. So instead of keeping it locked down as a proprietary secret, they are actively working to make it an open standard that the entire high-performance computing ecosystem can use and build upon.

• 
  x (@xaoticatech) reported 31 seconds ago

  If you need evidence, see GitHub Xaotica. Elon Musk is so brilliant that he knew I was honest when I said I solved a problem that almost nobody believed a man could solve, let alone a female engineer. So he needs to face the truth. I want to DONATE TeraFab and FINISH my work. 🥰

• 
  Nicholas C. Zakas (@slicknet) reported 44 seconds ago

  @github QuickStart guide link is broken

• 
  Matthew Belcher (@Trigun420) reported 2 minutes ago

  @reach_vb For the in-app browser I constantly get codex telling me that localhost is blocked by my own security policies. I have tried adding it to the allowlist, updated config.toml, etc.. Is there a fix for this? Github issues are present as well...

• 
  Slyke 🇦🇺 🇨🇦 (@SlykePhoxenix) reported 2 minutes ago

  @OpenAI Can you guys fix the Codex app so it doesn't keep breaking? Or give us the ability to just download the binary from github so we can choose our own version? Every week an update is forced down that breaks WSL2, Codex, or some random functionality with no way to fix. It's just not worth $100/mo when this happens on a weekly basis. Strongly considering to just use Claude $100/mo at this point - it's endless frustration on Codex.

• 
  Dan Liu (@danliu) reported 6 minutes ago

  @Scobleizer yea large corporation issues... but google / apple at least seem to be making some reasonable progress? and how did github get so bad? i feel like it's really perfectly positioned given the strongest usecase for ai today is coding. but it basically got *worse*...

• 
  Ben Phillips (@BenPhillip44103) reported 6 minutes ago

  @brightafia There is no such thing as a human, if you believe there is you are retarded, that is a made up thing. Morons who believe in "Humans" lick windows. However! They do have a tiny bit of pattern recognition. So when a human makes some trash, it is suspect. And just by biological pattern recognition your grift get's defaulted as horseshit (Which it is). AI is a syntax machine. It is literally the thing that has been telling you derp derpshits for years "Syntax error" And guess what? It is better at syntax than you are. So the systems (Not humans, no such thing) pattern recognition is good enough to distinguish that you are a moron that sucks at syntax, and the syntax machine is better. You probably use Github and rely on a bunch of **** code, and **** human programmers yes? Probably why you sound retarded.

• 
  Y. Fernandez 💻 (@la_eternaut) reported 13 minutes ago

  @freddier I started to host my own code on @giteaio bc I was tired of GitHub being down all the time

• 
  Dan Liu (@danliu) reported 13 minutes ago

  It’s pretty astonishing that $MSFT is down 11% in the last 2 years. Rewind 2 years and it looked perfectly positioned for the AI boom. It owns: - windows, the dominant pc os - github, where most of the world’s code is - vscode, the most popular ide - deepest partnership with openai - most number of enterprise contracts - office, where most non-coding computer tasks take place And today it doesn’t have anything compelling to offer. How did that happen?

• 
  Wasim (@WasimShips) reported 13 minutes ago

  Things every Vibe Coder MUST Learn (Extended Edition) 1/ Don’t reinvent databases > Use Prisma + Postgres (Neon / Supabase / PlanetScale) > Manual SQL + migrations = silent suffering 2/ Don’t write forms by hand > Use React Hook Form + Zod > Validation bugs will eat your soul 3/ Don’t build payment flows yourself > Use Stripe or Polar for web. Superwall or revenuecat for mobile > Never touch PCI compliance willingly 4/ Don’t build search from scratch > Use Algolia / Meilisearch / Typesense > Text search is way harder than it looks 5/ Don’t overbuild backend infra early > Use Serverless / BaaS first > Scale later, survive now 6/ Don’t ignore error tracking > Use Sentry / LogRocket > Console.log is not observability 7/ Don’t skip analytics > Use PostHog / Plausible > You’re flying blind otherwise 8/ Don’t design UI without components > Use shadcn/ui / Radix / Mantine > Consistency > creativity at MVP stage 9/ Don’t hardcode configs > Use env + dotenv + secrets manager > Leaks = instant regret 10/ Don’t DIY file uploads > Use UploadThing / Cloudinary / S3 > Multipart hell is real 11/ Don’t “just push to main” > Use GitHub Actions + Preview Deploys. Future-you will thank you 12/ Don’t skip performance tools > Use Lighthouse + Vercel Analytics. Slow apps don’t convert 13/ Don’t assume users understand anything > Add onboarding + empty states UX > Features 14/ Don’t wait to modularize > Use clean folders early. Refactors cost 10x later 15/ Don’t trust “I’ll remember this” > Document in README or markdowns. Your memory will betray you Bookmark to ship Better !

• 
  Traceback (@Tracebackqa) reported 15 minutes ago

  Green PRs still hide broken flows. - Traceback is the QA layer for teams shipping software. - AI drives the browser like a person; self-healing tests check every PR automatically. - Failures become work in GitHub, Linear, and Slack. Verify every product change before it ships.

• 
  Traceback (@Tracebackqa) reported 17 minutes ago

  The issue isn’t merging code. It’s proving the change still works. - Traceback is the quality assurance layer for modern software teams: every pull request is tested automatically before it ships. - AI controls the browser like a person would, and self-healing tests keep up when the UI moves. - Failures become trackable work in GitHub, Linear, and Slack; it connects to Vercel, Docker, AWS, Node.js, React, Next.js, and Vue. - Coverage spans web, mobile, web3, and design workflows. Verify every product change before it ships.

• 
  EAGLEPMX (@eaglepmx) reported 22 minutes ago

  @TheHackersNews The repo-write-access escalation is the part worth re-reading. A GitHub issue is untrusted input, yet agent workflows keep treating it as instruction. Same class of bug as SQL injection twenty years ago, just a new interpreter.

• 
  Manuel Montoto (@m6502) reported 23 minutes ago

  @BattleAxeVR Well done, Github is terrible. My servers use Debian but had a successful first year on CachyOS on the desktop. Debian worked well on my subversion server since forever, but the storage server uses ZFS and when an update changes the kernel I have to rebuild the kernel module.

• 
  Wyatt (@wyatt_jia) reported 32 minutes ago

  @hzqsns github issues