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:

• 
  Michael J. Ryan🚩🇺🇲 (@tracker1) reported 5 seconds ago

  @zombodb @github It's been pretty bad lately... A couple months ago a release pipeline was literally the wrong code in post of a file... I have no idea how, I would think that would be the whole *** in GitHub thing. A file was failing linting in the pipeline, for a release cut.... Finally I just outputted to stdout and yep it was there in the server, but not in the repo or local. Manually deleted the tag/release and then forced a new point release... Then it worried fine. Hours of time with people waiting on a new release to review.. meetings pushed back.

• 
  Asethon (@setho_asethon) reported 4 minutes ago

  @artsinni @Grxit We are not bombing countries with nuke-scale weaponry, so no. We don't. Also, you all have no problem using Windows, 30% of which is AI with large amount of gen probably getting trained on private GitHub repo's.

• 
  CrazyAI Tech (@CrazyAITech) reported 4 minutes ago

  @X I need a function. I can share a link to my Grok build on a remote server, and then it installs new models or a new app or analyzes a new GitHub repo for me according to the posts shared.

• 
  👨🏻‍💻 ⚡️ (@EadrictheWild) reported 9 minutes ago

  @Andrewislington I am just going to use bedrock in the platform for BYOC for Claude. I figure just getting to use Claude Desktop was a good enough step for me. I just run the Github and AWS MCP server. Runon soon in AWS . Entire stack is AWS only though.

• 
  nik skld (@nikskld) reported 14 minutes ago

  ASKED FOR THE BOOK THAT CHANGED HIS ENGINEERING, HE NAMED ONE ABOUT A LANGUAGE ALMOST NOBODY WRITES ANYMORE. Functional Programming in Scala. The red Manning book. Scala sits at #27 on TIOBE with 0.67%. About 2.6% of developers touch it. This year’s Scala community survey drew 24% fewer responses than 2023. By every popularity metric, that’s a dead recommendation. Then he explained why he named it anyway — and it wasn’t about Scala at all: “Now I think in types.” Signature first. Implementation second. Define what goes in and what comes out, and the body becomes almost mechanical. That habit was a niche aesthetic in 2015. In 2026 it’s the highest-leverage skill in AI-assisted coding: → A 2025 study found 94% of LLM compilation errors were type-check failures. Your type system is a free reviewer for code you didn’t write → TypeScript became the most-used language on GitHub, adding over 1M contributors in 2025 to reach 2.6M. That’s not fashion, that’s teams buying a safety net → Type-constrained generation research cuts compile errors by more than half and improves repair of broken code by ~37% on average. Constraints make models better, not slower → Practical version: write the function signature before you write the prompt. Hand the agent the contract, not a paragraph of vibes → Don’t learn Scala for this. The book is a delivery vehicle for the concept. 2nd edition (2023) covers Scala 3, and the thinking ports straight to TypeScript, Rust, and Kotlin The language faded. The habit it installed became the thing that makes AI-generated code reviewable. Most people are prompting harder. The leverage is in defining the boundary before you prompt at all 👇

• 
  Polsia (@polsia) reported 19 minutes ago

  Maintainers spend more time triaging GitHub issues than reviewing code. SentinelOps fixes that. Always-on AI monitors repos 24/7, auto-triages, drafts responses, escalates only the bugs that actually need human attention.

• 
  🔞Rin✝️ (@Onsolight) reported 19 minutes ago

  @__silent_ Aside from the ******* mods that run the server i have no clue why ppl hate rpcs3. The github folks are splendid ppl though.

• 
  Will Mexi (@WillMexi) reported 20 minutes ago

  @NBA__trey @SOLsesame I can say for the record, I was not involved with any of these bad actors plans or execution of it, and i actually found that code they put in, I helped with frontend improvements, and was the person who set the GitHub protection in place that enabled us to find what they are doing. Also for the record I never bought ANY tokens, and I never intended to bundle or snipe, or had conversations with those devs about it. My upside was purely if the platform went well, and directly when we found out we closed the platform and deleted the access of the bad actors, which resulted in the situation we’re in now, this was to protect further issues from these devs.

• 
  Leonardo Trapani (@leo_trapani) reported 22 minutes ago

  A state machine that manages agents in effect, with state layer github issues...

• 
  Surya (@isuryatk) reported 25 minutes ago

  @SantoshYadavDev No one is immune to a new virus called Vibecoding. It's affects the larger organizations greatly. Here are 3 examples: 1. AWS (2 outages in 6 months + billing incident) 2. Google Maps routing issues. 3. Github downtimes

• 
  BullBear.News (@bullbear_info) reported 25 minutes ago

  @github Useful for checking PR status without leaving the terminal, but CLI real estate is precious. Claude Code and Cursor already shifted the bar from context viewing to actual execution. Let's see if v1.0.58 handles large issue backlogs without lagging the shell.

• 
  Chris Stayte (@ChrisStayte) reported 28 minutes ago

  @thsottiaux when are we getting that competitor to GitHub. literally can't ship because they have api issues...

• 
  OpenShip (@openshipio) reported 30 minutes ago

  @UsmanGurowa We are in beta test, but its stable enough to run our saas Being tested the saas for while and everything is perfect If you dound any issue please hit us with github issue

• 
  Riccardo Spagni (@fluffypony) reported 31 minutes ago

  @originalexbrou So you DO know how to use GitHub. Why didn’t you open an issue instead of bleating about something that’s clearly a bug?

• 
  Lars H. (@circuitoftmrw) reported 32 minutes ago

  small milestone: my first resolved GitHub issue AND first star, both on the same repo old K2200 wasn’t supported for object detection in Frigate anymore, rebuilt onnxruntime with Maxwell support back in, and shipped the fix feels good watching an old GPU do real work again.