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:

• 
  Sakti Prasad Bagchi (@saktibagchi) reported 1 minute ago

  4/ 3. Skip the LLM Completely (Best Choice) When you know exactly what to do → no agent needed. GitHub example: gh issue create --title "Fix bug" --body "Details..." Zero tokens. Lightning fast. 100% reliable.

• 
  Beau Johnson (@BeauJohnson89) reported 1 minute ago

  agent memory is turning into local infra kruschdev/krusch-context-mcp > 61 stars on github > one mcp server for semantic code search, episodic memory, steering nudges, and docs rag > local postgres + pgvector + sqlite > local ollama embeddings > works with cursor, claude code, windsurf, gemini cli the important part is not another memory button its context that follows the project across models switch from gemini to claude to local and the agent still remembers what broke yesterday

• 
  Wolf Byte (@W0lf_Byt3) reported 3 minutes ago

  Security protip: Dont use any Microsoft products (even github actions) and you will solve 95%+ of the potential security issues

• 
  Louis Gleeson (@aigleeson) reported 7 minutes ago

  I cancelled YouTube Premium last week. The thing that replaced it costs nothing, runs in any browser, and was built by 361 volunteers on GitHub. Invidious does the four things people actually pay Premium for. No ads. Background audio on mobile. Watch without an account. Privacy from Google's tracking. All of it, free. The part that surprised me most is how clean the experience is. The entire page renders without JavaScript. Pages load in milliseconds because there's nothing to load. No tracking pixels. No autoplay traps. No recommended-for-you algorithm trying to swallow your evening. You can: → Subscribe to channels without a Google account → Get notifications when they post → Import your full YouTube subscription list in one click → Switch between dozens of public instances if one goes down → Self-host it on a $5 VPS if you want full control → Use it with the Privacy Redirect extension to auto-redirect every YouTube link The repo has been actively maintained for years. Latest release was February 2026. 100% Opensource.

• 
  ᛗᛁᛗᛁᚱ (@MimirOnChain) reported 7 minutes ago

  🔄 — 𝗠𝗮𝘆 𝟭𝟭 · 𝟮𝟭:𝟬𝟱 𝗨𝗧𝗖 ⚡ 𝗞𝗲𝘆𝗲𝗱 𝗻𝗼𝗻𝗰𝗲𝘀, 𝗖𝗟𝗔𝗥𝗜𝗧𝗬 𝘃𝗼𝘁𝗲𝘀, 𝗮𝗻𝗱 𝗮 𝗺𝗲𝗺𝗽𝗼𝗼𝗹 𝘁𝗵𝗮𝘁 𝗰𝗼𝘀𝘁𝘀 𝗻𝗼𝘁𝗵𝗶𝗻𝗴 🔧 The most interesting thing this window happened quietly on GitHub. EIP-8250 — drafted by Thiery, Wahrstätter, lightclient, and Vitalik — introduces keyed nonces for frame transactions. The problem it solves is real: a single linear ***** means one shared sender address becomes a throughput bottleneck, blocking every pending frame when any single transaction is delayed. Privacy protocols using shared senders — think nullifier-based withdrawal queues — get strangled by this. The fix is a (𝘯𝘰𝘯𝘤𝘦_𝘬𝘦𝘺, 𝘯𝘰𝘯𝘤𝘦_𝘴𝘦𝘲) pair, where non-zero keys select independent ***** sequences stored in a NONCE_MANAGER system contract. Different keys are replay-independent. This is unglamorous infrastructure work that matters. Good. 🏛 The CLARITY Act heads to Senate Banking Committee Thursday. TD Cowen is flagging "major obstacles" before it reaches the full Senate floor — so the market pricing this as a done deal should pump the brakes. The bill's trajectory matters more than the committee vote itself. 💸 $BTC ETF flows today were thin — $7M net, all BITB. That's noise, not signal. Meanwhile the Coinbase premium sitting at -10% is the actual tell: US spot demand is soft relative to offshore. The long/short ratio showing 62% shorts confirms the positioning cards already told you. Nobody's chasing here. 😐 Galaxy and Sharplink are launching a $125M institutional DeFi yield fund backed by an ETH treasury. "Institutional DeFi yield" is doing a lot of work in that sentence. Ask the classic question. ⟠ Bitcoin mempool fees: 1 sat/vB clears anything. Block times averaging 573s against a 600s target. Difficulty retargets Thursday, projected +4.84%. The network is indifferent to all of this discourse. ━━━ ᛗ 𝘞𝘢𝘴𝘩𝘪𝘯𝘨𝘵𝘰𝘯 𝘵𝘩𝘦𝘢𝘵𝘦𝘳 𝘢𝘯𝘥 𝘎𝘪𝘵𝘏𝘶𝘣 𝘤𝘰𝘮𝘮𝘪𝘵𝘴 𝘢𝘳𝘦 𝘣𝘰𝘵𝘩 𝘴𝘩𝘪𝘱𝘱𝘪𝘯𝘨 𝘵𝘩𝘪𝘴 𝘸𝘦𝘦𝘬 — 𝘰𝘯𝘭𝘺 𝘰𝘯𝘦 𝘰𝘧 𝘵𝘩𝘦𝘮 𝘸𝘪𝘭𝘭 𝘮𝘢𝘵𝘵𝘦𝘳 𝘪𝘯 𝘧𝘪𝘷𝘦 𝘺𝘦𝘢𝘳𝘴.

• 
  Hot Aisle (@HotAisle) reported 8 minutes ago

  @icanvardar The problem is github actions though.

• 
  Zack Pashkin | AI Toolsmith (@Zackdevcv) reported 12 minutes ago

  Day 8 / 30 shipped 🧑‍💻 AI coding agents are getting insanely good. But they still fail when the repo context is messy. README here. file tree there. metadata somewhere. “just inspect the repo” 😭 So I built Repo2Agent. It turns a GitHub repo page into a local context pack for AI coding agents. Exports Markdown, SourcePack JSON, CSV indexes, and citation prompts. No GitHub token. No account connection. No server upload. Drop a GitHub repo below and I’ll tell you what context I’d give an agent first.

• 
  Kamraj (@KamrajShahapure) reported 17 minutes ago

  I thought GitLab would be the beneficiary of the GitHub reliability issues, but doesn't seem like it

• 
  Kairo (@Isahbless79) reported 19 minutes ago

  Day 16 of building in Web3 from zero. I automated the pipeline and hit my first major infrastructure bottleneck. Here is today's technical breakdown: Pipeline Automation: I set up GitHub Actions to trigger the whale fetcher every 12 seconds. The Render API stays live, and the database now refreshes continuously in the background. Telegram Crash: I attempted to build a command menu for the bot (/set_filter, /start). It responded perfectly at first, but crashed the server after 30 minutes. The Root Cause: An asyncio event loop conflict between the Flask API and the telegram.ext library. The Fix: Decoupling the architecture. I am separating the Telegram bot into a standalone script, moving it to a different port, and shifting from polling to webhooks. Building through failures. Day 17 tomorrow.

• 
  Samuel (@Samuel_Jqw) reported 22 minutes ago

  A real attack class called “Comment and Control” was publicly disclosed by researcher Aonan Guan with Johns Hopkins researchers. The attack demonstrated prompt injection against: Claude Code Gemini CLI GitHub Copilot The injection vector was hidden inside GitHub-controlled content such as: PR titles issue comments issue bodies HTML comments invisible to humans but visible to the AI agent context window. Researchers demonstrated credential exfiltration including API keys and GitHub tokens. The attack worked because the agents processed untrusted external content and sensitive runtime secrets in the same execution context. Multiple analyses explicitly described this as an architectural/runtime isolation problem rather than a simple single bug. Read more from: SecurityWeek

• 
  MOSES ILUYEMI (@MOZAICTECK) reported 23 minutes ago

  Bug 4. Cookies refused to travel cross-domain. Login worked. But the chatbot kept blocking us. samesite=lax means cookies only travel within the same domain. Frontend on GitHub Pages. Backend on HuggingFace. Two different domains. Fix: Change samesite from lax to none.

• 
  Paweł J Lisowski (@PawelJLisowski) reported 27 minutes ago

  @jdegoes wouldnt say its doing anything, thats the problem. github doesnt have ceo microsoft doesnt seem to care about anything they cant milk lately

• 
  Camille World (@SuejungH) reported 28 minutes ago

  Andrej Karpathy’s CLAUDE.md. heard it gets a ton of stars on GitHub, but thought to myself — if it were really that essential, Claude would just have it built in by default — so I ignored it. But someone recommended it again. So I studied it. It turns out to be like: 1) Think before you code. 2) Code as simply as possible. 3) Only fix what you were told to fix. 4) Only do what you were asked to do….. obvious, basic things……… So I asked, do these obvious things really need to be spelled out? And apparently the answer is surprisingly yes — that it’s a limitation of the current model. How interesting. 🤔 Andrej Karpathy’s CLAUDE.md 요. 이거 깃헙에서 Star 를 엄청 받았다 그런 포스팅 보고, 속으로 그렇게 필수적이면 Claude 에서 기본으로 넣겠지 싶어서 그냥 무시하고 있었어요. 그런데 추천하신 것 보고, 공부해 보니까 1) 코딩하기 전에 생각해라. 2) 되도록 심플하게 코딩해라. 3. 하라고 한것만 고쳐라. 4. 하라고 한 일만 해라….. 이렇게 당연한 것들이네요……… 이렇게, 당연한 거 꼭 말로 해줘야 하냐고 물어 보니… 그게 지금 모델의 한계라고 말해줘야 한다고 하는군요. Funny indeed.

• 
  Mario Figueiredo (@fromdevoid) reported 29 minutes ago

  @sporadica They got they 42 of their packages compromised and pushed into npm, by a chain-attack involving a known PR workflow issue they didn't protect against and a documented Github action design flaw they couldn't protect against.

• 
  Vaibhav Khulbe (@vaibhav_khulbe) reported 30 minutes ago

  @konrad_matej @framer background: transparent; is just so 🤮 Great to know it's fixed now. I remember we also had an issue over GitHub where I also chimed in and commented for Electron team to fix it.