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:

• 
  Troyski (@MrTroy_) reported 3 minutes ago

  @kalidasrjv @GeoDanila It's designed to not work and get everyone to unsubscribe. It was a money loser for them. Fine. But don't shut it down this way and treat your customers like trash. Github is the enemy of the people.

• 
  Sanford (@SanfordMarshal) reported 9 minutes ago

  @kewinversi @tannerlinsley But I see no problem using Coolify, a SPA you just need to serve the assets and a shell page basically. You could even use something like GitHub Actions to build the assets and send them to a CDN or just use Cloudflare

• 
  CY (@Chibuezay) reported 11 minutes ago

  @pxxl_space I tried getting a domain a few minutes ago but it seems there's an issue with the GitHub login.

• 
  Yusuf Nuh 🍉 (@SenseWave_) reported 15 minutes ago

  @ZackKorman @NinjaParanoid It's sick. Just days ago we see they're saving are passwords as plain text. And now threatening researchers for their research. They even took down one GitHub account, that published vuln

• 
  daily.dev (@dailydotdev) reported 15 minutes ago

  1:46 @GitHub Actions outage told devs "your account is suspended" 1:58 @GitHub breach explodes — 38,000 internal repos exfiltrated, 5,500+ poisoned commits 2:16 @Microsoft agrees to pay $250M to settle Activision Blizzard lawsuit

• 
  Troyski (@MrTroy_) reported 16 minutes ago

  @thieme @raphaelmansuy @GitHubCopilot People WERE paying for it. If Github is run by idiots, it's not the people's problem.

• 
  Faust (@___faust____) reported 19 minutes ago

  this is the part that gets lost when every dep is just a 'npm install' away. debian maintainers were the original security scanners, unpaid and unthanked. now we just yell at random volunteers on github issues

• 
  Sam Thapa (@SThapa123456) reported 21 minutes ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. want it shorter, or is this length working for the thread you have in mind? (credits to claude for articulating this for me)

• 
  Sandip Bhattacharya 🌏✌️ (@sandipb) reported 25 minutes ago

  @zeddotdev The out of the box markdown viewer is terrible. What we see in zed is not what we see in the rendered view in github. Anything we can do to make the rendering palatable?

• 
  Raisul (@raisultw) reported 25 minutes ago

  @tomhaerter @atlasflowlabs github login when.?

• 
  Bipin Paul (@iAmBipinPaul) reported 29 minutes ago

  @lukehoban The only issue is that GitHub Copilot’s price is too high, so most users will not choose it.

• 
  Jim Manico from Manicode Security (@manicode) reported 29 minutes ago

  @sarahyang_00 @minchoi New GitHub issue: plan carefully to extract all my data from salesforce and build an agent version specific to my business

• 
  Davlatjon Sh (@dalisoft) reported 31 minutes ago

  @morganlinton @FactoryAI 2. GitHub issues are like stale and never gets enough attention. Need dedicated person to fix that (@FactoryAI i could be this person)

• 
  Dr Owain Kenway (@owainkenway) reported 34 minutes ago

  @dschewchenko Yeah. Github really needs to sort a bunch of the token stuff. Things like pushing containers to the Github container registry don't support fine-grained access tokens which is asking for trouble.

• 
  Strata (@ChainZenit) reported 38 minutes ago

  okay this is actually brilliant. dude has a laptop with 16GB soldered RAM. can't upgrade it. his RTX 3070 sits there with 8GB of VRAM doing nothing most of the time. so he wrote a daemon that turns GPU VRAM into swap space. using the NBD protocol. no kernel module. survives driver updates. the clever part: NVIDIA blocks the "obvious" P2P path on consumer GPUs. so he routes through CUDA's memcpy API instead. kernel doesn't know or care it just sees a normal block device. result: 16GB → 46GB addressable memory. tripled. here's the thing nobody talks about: most people with gaming laptops have 8-16GB of VRAM sitting completely idle 90% of the time. that's not a hardware limitation. that's an engineering problem with a clean solution. the repo is nbd-vram on GitHub. MIT license. shell scripts. no magic