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:

• 
  Luis Bezzenberger (@bezzenberger) reported 13 seconds ago

  has anyone gotten Kimi K2.6 on dual mac studio 512gb via @exolabs to work with an agentic harness? if so, would love to chat. it works for chat, but stops after just 1 response when put into an agentic harness like opencode, vscode. many people have similar issues on github

• 
  The V Programming Language (@v_language) reported 58 seconds ago

  @tauraamuix @IroncladDev Please report gitly issues via github, they will be quickly fixed this way. You can report multiple issues in one github bug report.

• 
  Tom Ballard (@tcballard) reported 1 minute ago

  @pxue if you have any questions or feedback fire them my way, either public or DM (or issues on GitHub, I don’t mind) planning to ship an updated version later today with the VSCode Extension, and some other cool little features as well…

• 
  Iprashant10 (@Iprashant10) reported 2 minutes ago

  Dear ministry of IT, Scammers are using Outlook, JIRA, Github, MS teams to circulate the NEET paper. Kindly issue a ban on the lines of telegram.

• 
  Emi (@SrEdm00) reported 2 minutes ago

  @pierceboggan @code Yes, but not. The problem of using GitHub Copilot instead of Pi, is that GH Copilot introduces a lot of information in the first prompt (tools desc, skill defs, etc) so KV Cache prefill takes a lot

• 
  Xovion Labs (@xovionai) reported 3 minutes ago

  Microsoft just hired AWS to run GitHub. AI demand broke Azure's forecast. From the leaked planning docs: • 2025 Copilot commits: 1B. 2026 projection: 14B • GitHub now does 1.4B commits per month • Copilot error rates peaked at 21% • Planned 10x Azure expansion became 30x in 4 months Owning the data center stops mattering when your own AI floods it. Investors already filed a Copilot disclosure suit.

• 
  Nigel (@nigel1) reported 4 minutes ago

  @cursor_ai Needed this bc GitHub is broken

• 
  gaurav 🫆 (@gauravmandall) reported 6 minutes ago

  @noobdeveshjha Please don’t say that if that happens I’ll lose over 300 repos, all deployments, github action workflows and all websites i use login with github. isn’t this scary 😭

• 
  RY-GOD (@Moneybag_Fin) reported 7 minutes ago

  The clever part: There's no server and no database. A GitHub Action runs bam-net snapshot every 6h and commits the result straight back into the repo as JSONL. Because it's append-only and lives in *** history, anyone can replay the commit log and verify the dataset themselves.

• 
  Meteor.js (@meteorjs) reported 7 minutes ago

  @CloudByGalaxy The goal: every push to your main branch automatically triggers the same sequence. GitHub pulls your code, installs Meteor, authenticates with Galaxy, injects your settings, and ships the build. No terminal, no human error, same result every time.

• 
  Prashanth Koppula (@koppula) reported 11 minutes ago

  4/6 ReproRepo sidesteps that by treating GitHub issues as a proxy signal across 1,149 recent ML papers from major conferences. The trick: instead of expert-curated labels, the framework matches agent-reported issues to human-raised GitHub issues using semantic similarity.

• 
  Carlos Rodríguez (@carlosrr004) reported 13 minutes ago

  Just when GitHub was having huge performance issues...

• 
  Alex Nguyen (@alexcooldev) reported 14 minutes ago

  I remember when Cursor first launched, many people mocked it as “just a VS Code fork” that could never compete with VS Code + GitHub Copilot. I switched to Cursor early simply because its code suggestions were better and the "Tab" experience felt smoother this was before agents even existed. I’ve used it ever since and never felt the need to switch back. A great reminder: focus on solving real user problems, not on people saying, “This already exists.” Ship. Test the market. Iterate. Let the results speak. Congrats to the Cursor team, you proved them wrong. 👏

• 
  Jared Tate ©️ (@jaredctate) reported 14 minutes ago

  I'm a blockchain developer. North Korean hackers tried to steal my crypto & hack my computer by pretending to recruit me on LinkedIn for a crypto consulting gig. Here's the entire attack: PHASE 1 — THE LURE A "recruiter" (a polished, good looking blonde "British woman in London") messages you on LinkedIn. Real-looking profile, perfect English. She books a Google Meet. On the call it's a different person — a bald Chinese looking guy, who quickly turns his camera off complaining of a bad connection, broken English — who asks two telling questions: "What crypto wallets do you use?" and "What code editor do you use?" That's not an interview. That's target profiling. PHASE 2 — THE DELIVERY He sends a GitHub repo (a "Web3 game" project) and says: clone it, run `npm install`, and open it in Cursor so we can see you know what your doing. It looks like a normal codebase. It's bait — with malware hidden in 3 separate files, each rigged to run automatically. PHASE 3 — PAYLOAD #1: package.json (the trip wire) They added one line: "prepare": "node server/server.js" npm runs the "prepare" script automatically right after `npm install`. So just installing the dependencies launches their code. No button. No warning. PHASE 4 — PAYLOAD #2: auth.js (the backdoor) In one file, the real code ends at line 18. On line 19 — shoved far off-screen behind ~600 blank spaces so you'd never scroll to it — sits obfuscated code that: • collects your hostname, OS, and MAC address • sends your entire environment (process.env) to a North Korean server: 147.124.212.180:1224 • runs whatever JavaScript that server sends back, via eval() = full remote control • repeats every 5 seconds That's a backdoor. The eval() is the doorway they use to push the actual wallet/password stealer. PHASE 5 — PAYLOAD #3: .vscode/tasks.json (the silent one) A second hidden file set to "runOn": "folderOpen" — it executes the instant you open the folder in your editor, with no window and no output: Translation: download a script from their server and run it immediately. THIS is why they demanded Cursor — they were betting it would auto-run the task. VS Code stops and asks "do you trust the authors of this folder?" first. I never said yes, so it never fired. DO NOT USE CURSOR (for many reasons) PHASE 6 — THE FALLBACK When the repo "wouldn't run," he sent a slick website with a "Connect Wallet" button — a straight-up wallet drainer — and said "just connect MetaMask." THE GOAL Drain your crypto and steal your credentials — money that funds the regime. It's a documented operation: the "Contagious Interview" campaign (aka Famous Chollima). HOW TO NOT GET HIT • A "job interview" that requires running their repo = malware until proven otherwise. • Never `npm install` a stranger's code on your real machine. Use a throwaway VM. • Keep serious crypto in cold storage — never a hot wallet on your daily driver. • If a recruiter's story falls apart the second you get on a video call, walk.

• 
  ✚ Oz ✚ (@oz_a13banger) reported 16 minutes ago

  @jediahkatz Im super interested in this. Im especially hopeful they have something better than GitHub Issues for tracking things. We use Issues heavily but have always been unhappy with it.