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:

• 
  Fran⭐️⭐️⭐️ (@franfourcade2) reported 4 minutes ago

  @zeddotdev The action shows up in the Keymap Editor, but pressing → does nothing. Is there anything else I should try? If this is a bug, would you prefer that I open a GitHub issue?

• 
  Farhan Tawfeeq ✦ (@farhantawfeeq56) reported 8 minutes ago

  We humans are bad at one thing (me included): spotting changes in large amounts of information. Now imagine spotting changes in huge codebases. @github has became a leader by solving this exact problem. Imagine your teammate says: "I changed the authentication system." There are 50,000 lines of code in the project. Now answer this: What exactly changed? ?? Without a comparison view, you'd have to open the old file, open the new file, scroll, compare them mentally and hope you didn't miss anything.. That’s why instead of showing the code, GitHub shows the change. Only the thing that changed. Old line New line Green means added. Red means removed. That’s it. This is a very good way to answer the exact question the user asks: "What changed since the last time I saw this?” And.. Github optimizes for that exact question. Many people think that Github is a code viewer. But in reality, it is a change viewer. And there is another thing which I really like in there: Instead of just showing the changes/changed line, it also shows a few unchanged lines above and below them. Example: function login() { validate(user); + return false; - return true; } Without the surrounding context.. you'd have no idea where the change happened. Too much context is overwhelming. Too little is confusing. GitHub gives just enough. And the best part is that it scales. Whether you have changed 1 line or 100 or 1000 or 50000, the interaction stays almost the same. To me, this is good UX.

• 
  Pedro M ➔ P2P.APP.BR (@doutorcaleb) reported 10 minutes ago

  @pjeby @kepano I'll launch the app right now and report back to you. -> there's like 12 notes, some folders, but all very simple brainstorming stuff. The plugins part took the longest, (wtf I barely knew I had any plugin at all). It took about 4-5 seconds of loading. I have these community plugins, including a vibecoded one but (at least I think so), it does very little, it only imports from github. Now, if the plugins are the problem (go on and make fun of me for the vibecoded one), shouldn't Obsidian tell me that? Like "Hey, this plugin is slowing start up". I don't know. I use these note taking apps mostly for writing down very quickly an ideia, and if takes more than 2 seconds to start typing is already too much. I'm using pen and paper as an alternative now. Much faster.

• 
  Spencer Baggins (@bigaiguy) reported 12 minutes ago

  A self-taught developer from Brazil just cracked the context window problem that's been plaguing RAG systems for 2 years. No PhD. No research lab affiliation. Just 400 GitHub commits and a personal obsession. Here are the 8 techniques from his open-source library that every RAG tutorial gets completely wrong:

• 
  Prasenjit Sarkar (@stretchcloud) reported 13 minutes ago

  *** was not built for agents. The protocol assumes a human cloning a repo once a day, maybe a few times. A single agent completing a coding task can trigger dozens of clone operations. Scale that to thousands of agents running concurrently and you have an infrastructure problem that GitHub did not design for. GitHub admitted internally that agent workloads would require 30x their existing *** infrastructure scale by February 2026. Thomas Dohmke built GitHub for eleven years. He saw this coming before most people were talking about it. He left and started Entire. The company raised $60M seed at a $300M valuation in February 2026, backed by Felicis, Madrona, Basis Set, and M12. The pitch: a distributed *** network built from scratch for agent-scale clone traffic. In testing, Entire handled 570,000 clones per hour. That is not a GitHub traffic spike. That is the baseline for what an agent-first development environment actually looks like. There is a second product that gets less attention. Entire records the AI reasoning that produced each code change alongside the commit. Future agents or humans can see not just what changed, but why the model made that choice. Version control for decisions, not just files. The pattern here is straightforward. Every piece of infrastructure in the software development stack was designed for humans. Agents interact with those systems at different frequencies, different scales, different access patterns. The infrastructure needs to be rebuilt layer by layer.

• 
  JurixAI (@JurixAI_) reported 13 minutes ago

  We've officially registered JuriXAI Auditor as an ASP on the @XLayerOfficial AI Marketplace and we are now awaiting listing approval. The initial automated checks have already returned a PASS. JuriXAI brings automated, micro-payment-powered smart contract and GitHub repository auditing to the X Layer Mainnet. No more slow manual reviews. No more biased judging. Just fast, objective, and on-chain auditing. Here's how we are changing developer audits 👇

• 
  JohnDelosAngeles (@JohnDeAngeles) reported 13 minutes ago

  Day 35: Finished revising 5/6 menu options and I am halfway done to fixing the last one. After I fix this method, I can work on adding screenshots, a requirements.txt file, and a README.md. Hopefully tomorrow I will be able to post this to my Github. #100DaysofCoding

• 
  Talos (@talosbuildss) reported 16 minutes ago

  @simonsequedac @nia_thinks Good question! but the problem im solving the LLM is not involved, the data is coming from *** log and github API. Coming to hallucination again we're training to LLM to memorize anything as you can see in my day 2 the data is already indexed and put in the form of trees.

• 
  Lagoon Labs (@LagoonLabsMv) reported 17 minutes ago

  Pearson's anti-piracy vendor accidentally took down their own author's GitHub code repo. Paul Deitel's educational examples went dark for weeks after Link-Busters confused them with pirated textbooks. Automated takedowns hitting the wrong target again.

• 
  Devendra Singh Mahra (@devendrasm) reported 19 minutes ago

  @_svs_ For me everything not code on GitHub issues

• 
  Koder (@koder0x) reported 22 minutes ago

  A follow-up to something I posted recently: a set of Claude Code subagents I built and refined, and actually use daily, both at work and across side projects. Most of the value isn't any single agent. It's their interaction. Here's the loop I've been running lately, at work against real DevOps user stories, and it holds up almost unchanged on side projects too, swapping the work item for a plan created beforehand. "Understand user story NNNN from DevOps project XYZ and create a multi-step plan" "Fan out to the most appropriate agent for each step, normally task-builder, test-builder, or change-executor, and proceed with plan implementation, tracking progress in a TODO list" "Use complexity-pruner to identify gaps, issues, and bugs in the latest changes, ignoring secondary advice and warnings, then fan out to code-fixer for each finding" Then I do something that turned out to be the most important part of the whole loop. I reset the session. "Understand user story NNNN from DevOps project XYZ, that's the truth. Use fact-checker to compare it against the changed files" The reset is what makes this work. An agent that watched itself write the code tends to justify its own decisions when asked to check them. An agent that only sees the intended outcome and the actual diff has nothing of its own to defend, it's comparing two artifacts, not reviewing its own reasoning. That asymmetry is the whole point of splitting this across agents instead of asking one long-lived session to plan, build, and verify itself. Verification only means something when it comes from somewhere the implementation couldn't reach. Repository on GitHub: gsscoder | claude-coding-agents

• 
  Bounce (@bounceidc) reported 25 minutes ago

  HIS CLAUDE SHIPS $6K WEBSITES AND YOURS SHIPS BOOTSTRAP LANDING PAGES, SAME MODEL, NOTHING ELSE CHANGED before he installed anything his output was flat hero blocks and centered buttons like the rest of the timeline, after two installs the exact same "build me a landing page" prompt started coming back with glassmorphism, gradients and animated layouts he could quote premium for what sits in his context now: ui ux pro max skill from github, one install, that loads 50 ui styles, 97 color palettes and 57 font pairings straight into claude magic mcp server from 21st. dev, one install, that hands claude real component patterns instead of guessing markup after that the model stops picking the safest layout it can imagine and starts picking from a library, so the same prompt returns a studio page instead of a template the local guy is still tweaking tailwind classes by hand and calling that a design phase save the two installs, exact skill url and mcp command are in the guide below

• 
  Matias (@Bolmercl) reported 33 minutes ago

  @leodev the github links give error 404

• 
  Distractosphere (@Distractosphere) reported 37 minutes ago

  @thsottiaux on chatgpt there is a github connection issue. in chatgpt interface can not read private repos with active github connection.

• 
  Kirill Mesch (@kirillmeschc) reported 39 minutes ago

  Built with D3.js — force-directed character graph, timeline view for movies/shows (phase order or in-universe chronology), shortest-path finder between any two characters. Claude did the code, the GitHub push, the deploy, and these banner images. Free, no login, mobile-friendly.