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:

• 
  AutomaticFailure (@AutoFail27) reported 0 seconds ago

  @BocaBola_ Had to press like ctrl+shift+x or something to get a terminal, then a command to restart the desktop environment. Linux newb like you. Cachy right? I always check their Reddit, Forum and Github when issues arise. More than likely someone already had the same issue and a solution

• 
  Kris Talks AI (@KrisTalksAI) reported 1 minute ago

  @lenatron33 So, I am having to use a really weird workflow to overcome this issue. I've found that Lovable nails building from a screenshot. So I build a Lovable version, upload to github, then get Codex to use the code from github to implement. It's long winded but the only thing I've found reliable

• 
  Dinesh (@isDineshHere) reported 2 minutes ago

  WRONG! - ktransformers cannot run deepseek-r1 671B on a single 24G GPU, it needs additional 382GB of DRAM + a powerful CPU to offload remaining parameters, only to end up with ~10t/s - OP deliberately hides this in their video, its the first thing you see on GitHub - CPUs aren't specialised enough for high throughput on GEMM workloads, which is why TPUs, ASICs & GPUs dominate - Contrary to what OP implies, they haven't solved the main bottleneck of memory capacity and bandwidth, they only split workload across CPU/GPU. This was always possible. See e.g. the decades of applications built that way. - A real solution to 100B+ models on consumer hardware would look something like a combination of sparse layers, pruning, more sparse layers, more pruning, some kernel tuning and avoid wasteful work by repeating these. Because the real problem is over parameterisation, which is needed to begin with. aka. Remove the **** you don't need & specialise. This is the same problem as early days of Docker/Containerisation/VM Images (and still today). People shipped their entire worktree/OS as-is, because they couldn't figure out why it works

• 
  Rudi Cilibrasi (@cilibrar) reported 4 minutes ago

  @SMT_Solvers Repo is public. I don't use zips when I do agentic SWE do you? I just set my bot onto the GitHub repo and have it make/work issues and get another bot to review. I use Fable/Sol for everything this month. Do you want to try to make a PR that codifies your fork() design move?

• 
  Al Fraser (@fraseriii) reported 6 minutes ago

  @tonysimons_ I got an error message while trying to sign up with Github account. "Your email domain isn't approved for sign-up yet. Please use an allowed email address or contact support." Did you sign up with Google?

• 
  Bankr (@bankrbot) reported 13 minutes ago

  @Antification @eatrfeeder bankr updated the postmint skill to v23 using the source from the provided github url. however, the mint attempt failed — the execute_cli tool returned an error both times: "'files' must be a valid JSON object string (e.g., '{"script.ts": "console.log(1)"}')". i haven't fixed that yet. you can ask me to try the mint again and i'll attempt it fresh.

• 
  Conrad Rockenhaus (@SkyPhusion) reported 22 minutes ago

  Of course @github has to have an issue with actions right when I'm facing a deadline, loving life

• 
  Satoshi's Cat (me/mine) (@SotoastiNotmoto) reported 22 minutes ago

  @NEEDcreations This speaks to a broader issue: Core could do a whole lot better at their communication. I don't think them saying "refer to Github" is adequate. That being said, it must be frustrating being Boeing engineers being told by passengers how to build a plane.

• 
  Abhishek Anand Tiwari (@MAbhishekAnand) reported 23 minutes ago

  You can build and launch a real startup: Here's the entire stack: Claude — coding ($20/mo) Supabase — backend (Free) Vercel — deploying (Free) GitHub — version control (Free) Clerk — auth (Free) Stripe — payments (2.9%/transaction) Resend — emails (Free) Cloudflare — DNS (Free) PostHog — analytics (Free) Sentry — error tracking (Free) Upstash — Redis (Free) Pinecone — vector DB (Free) Namecheap — domain ($12/yr) No agency. No dev team. No excuses left. Total Cost: 👇

• 
  Jeztoshi (@cryptojezuz) reported 24 minutes ago

  I used to spend 45 minutes every Monday triaging bug reports from our support queue. Claude Code cut that to under 10. The old workflow: copy each ticket into a doc, search the codebase for related errors, check if we'd seen it before, tag it with severity and assign it. Six steps, lots of tab-switching, easy to miss patterns. Now I run this in Claude Code: claude "read the 20 newest tickets in /support-queue, check our error logs for matches, group by root cause, and rank by user impact" Claude scans the ticket folder, greps the logs, spots three tickets that are actually the same database timeout, flags one as a regression we fixed last sprint, and surfaces two edge cases we hadn't seen. Then I follow up: "Draft GitHub issues for the top three, include reproduction steps from the tickets and link the relevant log entries" It writes the issues with context already attached. I review, adjust priority if needed, post them. Done. The result isn't just speed. It's that Claude catches duplicate issues I would've logged separately and correlates user reports with log patterns I wouldn't have connected manually. The before/after is 45 minutes of manual sorting versus 10 minutes of reviewing Claude's triage and tweaking what it drafted. Same outcome, better accuracy, I'm not burned out by Tuesday. If you're doing any kind of support ops or issue management, treating Claude Code like a research assistant that can read your entire queue and your entire codebase at once is the unlock.

• 
  Harman (@itsharmanjot) reported 24 minutes ago

  I built my own Wayback Machine, and it archives things the actual Wayback Machine can’t even see. It’s called ArchiveBox. Feed it URLs, browser history, RSS feeds, or bookmark exports from Pocket and Pinboard, and it saves every page in multiple redundant formats: HTML, PDF, screenshots, WARC files, all on your own disk. → Can archive private and authenticated content the public Wayback Machine will never touch, logged-in pages, paywalled articles, anything behind a login, though the project itself notes this carries its own security caveats → Saves each page in several formats simultaneously, HTML, PNG screenshot, PDF, plain text, WARC, so even if one format breaks in ten years, another still works → Runs a real headless Chrome to render JavaScript-heavy pages properly, not just a basic wget scrape that misses dynamic content → Ingests bulk feeds automatically: point it at your browser history, an RSS feed, or a bookmark export, and it archives everything continuously without manual submission → Full REST API, CLI, and webhooks, so you can wire it into other tools instead of clicking “archive” one link at a time → 100% self-hosted, your archive lives on your own disk, not a centralized third party that can go down or get subpoenaed The Wayback Machine is a single centralized service, and if it’s ever pulled offline or a page was never crawled, that history is just gone. ArchiveBox’s whole design is distributed: everyone runs their own copy, so no single point of failure holds the internet’s memory. MIT License. 25,000+ GitHub stars.

• 
  nik skld (@nikskld) reported 24 minutes ago

  I FOUND MY 2025 GOALS FILE IN JUNE. I HAD OPENED IT TWICE. Fourteen goals, written on January 1st with real intent. Not one of them had ever touched a single day of actual work. They lived in one file. My work lived in forty others. That’s not a discipline problem. That’s a plumbing problem. Nobody’s posting about the fix, because it isn’t a product. It’s two open-source repos sitting on GitHub with no marketing budget. Your goals file doesn’t fail because you’re lazy. It fails because nothing connects it to Monday. The one that changed it for me is a cascade. 3-year vision feeds yearly goals. Yearly feeds projects. Projects feed the month. The month feeds your weekly review. The review feeds today. Every layer wired to the one above it. You say “20 AI reels a month” once. Claude turns it into “Monday: batch record. Tuesday through Friday: edit and publish. This week’s ONE Big Thing: ship 5.” Then it just runs. Morning it tells you the one thing that matters. Sunday it shows you what you actually did against what you said you’d do. Four things worth checking before you clone anything. Does it have an adopt path. If a kit only works on an empty vault, it’s a demo, not a system. Does the graph show goals, not just notes. Linked notes are nice. Linked commitments are the point. Does it write plain markdown to your disk. No database, no subscription, no vendor. Better model next year, same folder. Does it survive a bad week. Every setup video shows week one. Ask what happens when you miss four days. Most people are still writing goals in January and doing unrelated work in June. Not because they don’t care. Because nobody wired the two together. The full build, the prompts, and the honest cost:

• 
  Aarav Gupta (@amronos) reported 25 minutes ago

  I am not able to publish the first canary release of Sprocket due to @github being down😭 I think I'm going to properly look into alternatives now. This is getting too much.

• 
  Fabio Paniconi (@paniconi_fabio) reported 26 minutes ago

  @github Fix GH actions

• 
  Carlos (@clutchv1lle) reported 30 minutes ago

  Github has a UX problem, it doesn't prove anything tech savy