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:

• 
  Preetham Kyanam (@pkyanam) reported 3 minutes ago

  my god github runners are so slow i now see the value in @useblacksmith and will be working to integrate it into my workflows asap

• 
  altmind (@altmind) reported 7 minutes ago

  @saltyAom you can probably find a github issue with the list of problems they have?

• 
  Abhijay Rana (@abhijaymrana) reported 7 minutes ago

  seeing these comparisons a lot lately, but despite the hype i'm not really sold 1) swe-bench verified is a broken benchmark > super contaminated bc all tasks are just public github patches from issues/prs, so its all in distribution > the evals are poor, 59% of hard tasks fail bc of bad tests with false-positives/negatives or are extremely contrived. this makes them either flawed or unrealistic. 2) these scores are pretty cherry-picked & use a custom harness, not the standard public swe-bench harness. this is why the scores are unreproducible + not on official leaderboards. > opus 4.7 with custom harness scored 87.6%, over 14% more than the harness-optimized qwen. *this* is the truly fair comparison 3) infra costs are still exploding which is already pricing out some “frontier” open source models. > does china have enough capex for a frontier buildout? research talent is obviously not the problem but this may be the constraint > i wonder how much china govt will subsidize here, bc i'm unsure how these models will make money and break even. china is notoriously cutthroat but even then, some may eventually move to closed-source just to stay operational

• 
  Senior PowerPoint Engineer (@ryxcommar) reported 8 minutes ago

  Github Actions needs to get their **** together. All the recent GA-based supply chain attacks and vulnerabilities-- LiteLLM, Trivy, Tanstack, nx-- are theoretically preventable if you know way too much about Github Actions footguns: hashes for uses, don't store PATs in pull_request_target (or maybe don't use pull_request_target at all, even "securely"), never use classic PATs (unless you need to, of course, which you might because Github *still* doesn't support all features with fine-grained access control). But it's also ridiculous that's the state of things. The entire software supply chain shouldn't be dependent on 100% of the maintainers of the hundreds of dependencies we're downloading indiscriminately knowing the nuances of Github Actions security. Unlike all the AI agents yeeting bullshit code to Github's servers and overwhelming it, all of these security issues with Github Actions have been known for a long while. It doesn't seem like Github has the ***** to mildly inconvenience people by deprecating classic PATs or forcing commit hashes for 3rd party actions or what have you so I guess this will just be how things are forever.

• 
  Alan Martinez (@pev_de) reported 11 minutes ago

  @steipete Our agents auto-tag GitHub issues by department. The legal one started filing cookie compliance bugs nobody asked about. The SEO agent found 404s nobody knew existed. Agents creating work you didn't know needed doing > agents reviewing work you already did.

• 
  Douwe Tjerkstra (@tjerkienator) reported 12 minutes ago

  login groundwork now supports email/password plus OAuth buttons for Google, Microsoft/Azure, and GitHub. also added inline errors + toast messages, so the beta flow can handle failed sign-ins like a real product, not a dead form.

• 
  Max (@MaxMakesMods) reported 12 minutes ago

  @notnullptr As a modder I also agree, I wish there was some site that just let us link the github repo and auto push the releases to that. Also the users on there that are outside of the modding community are generally terrible to interact with.

• 
  M. Yahia (@maddada) reported 14 minutes ago

  @robinebers Github and npm could do so much to stop these in their tracks. I mean socket detected the issue within 6 minutes, but Microsoft couldn't do any scans to catch this? They're dropping the ball do hard.

• 
  Kush (@kushbhuwalka) reported 15 minutes ago

  I find that an underrated way to get a lot of startup ideas is to just do a startup. here’s my list of spaces that i find interesting / have had problems with. - ci/cd - github actions alts - agent o11y - slackbot / iMessage / WhatsApp dx - coding agent optimization - dynamic UIs - agent harness testing on docs - software digital twins for testing - ui/ux bots - clicky but for your product - permissioning for agents - agent onboarding & auth - billing and cost tracking

• 
  Varnell Hill 🇵🇹🇵🇹🇵🇹🇵🇹 (@Yellowman617) reported 17 minutes ago

  GitHub just proved that if you store it, they can steal it. Aethelgard proves that if you liquidate it, there's nothing to take. We don't fix the headers; we remove the prize. My own ZSA protects me from things like this because that's exactly why I built it...stay safe out there....

• 
  Pranab Gambhir (@pranabgmbhir) reported 17 minutes ago

  @CodeWithAmann I think because GitHub has become synonymous with development that we often forget that at the end of the day someone created this as a business, solving a very big problem while making a lot of money! And most importantly now, the data!

• 
  Mad Orkestra (@MadOrkestra) reported 19 minutes ago

  What vibe coders don't seem to understand: Creating your own solution for the same problem is easy. Collaborating, contributing and iterating on an existing solution is much harder. But that is what open source means. Not just pushing random stuff to Github and calling it a day.

• 
  Karim C (@BrandGrowthOS) reported 25 minutes ago

  @github the chat mode is legit. way faster than copy-pasting error messages into claude when something breaks. actually feels like talking to someone who understands the codebase

• 
  Rasmus Hjulskov (@RasmusHjulskov) reported 27 minutes ago

  @mikker Everything that doesn’t need me in the loop or things that’s easier to be handled over discord on the phone. It’s still not an alternative for my main coding agent, but it works on most of my codebases more like an intern on my old laptop with their own GitHub account and a shared Obsidian vault where it creates a llm-wiki and a shared Kanban board. I have tried moving it deeper down the afk coding paradigm, but I pretty much always come back to why I hate waterfall development - or at least that the project I’m currently tinkering with is so early, that there isn’t much to win if any. So it’s mainly the complete overview over all I’m doing and all the codebases if needed, which have resulted in I’m using that instead of most of what was prior a Gemini/chatgpt chat and only less than I expected of what I was doing with local coding agents.

• 
  Arzvak (@RealMITian) reported 28 minutes ago

  @CliftonSellers Imagine you're building a science project in a team. You're working on part x, teammate on y etc. Now how do you know which person has done what? Are you guys doing the same thing at the same time? conflicts arising? You can think of Github as something which is made to fix that. Shows how much work is done, by whom, what changed since last night, who else worked on what, etc. etc.