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:

• 
  AISecHub (@AISecHub) reported 2 minutes ago

  Google's AI powered GitHub workflows that allowed any external attacker, with nothing more than a public GitHub issue, to a full supply chain compromise of the gemini-cli repository, Google's AI coding agent with 101,000+ stars. The attack worked in four steps: > The vector. An attacker opens a public Issue on a Google GitHub repository. > The mechanism. Google deployed a Gemini-powered AI agent to read and triage incoming public issues automatically. The attacker hides instructions inside the issue text. When the agent reads the issue, the prompt injection takes control of the agent. > The exploit. Under the attacker's instructions, the Gemini agent extracts the workflow internal secrets from the build environment and exfiltrates them to an attacker-controlled server. From those credentials, the attacker pivots to a token with full write access on the repository. > The impact. Full supply-chain compromise. The attacker can push arbitrary code to the main branch of gemini-cli’s repository, which then ships to every downstream user.

• 
  Seth For Privacy (@sethforprivacy) reported 12 minutes ago

  @Graysatoshi @RadarChat Still pending approval there, Google have been extremely slow, taking over a week to even start the review process! Pushing them hard, in the meantime can install manually from Github or via Obtainium.

• 
  Anicet (@AniC_dev) reported 14 minutes ago

  we made box because we weren't satisfied with other AI sandboxes most were overengineered, selling you their internals or specific isolation primitive, like you need to be an expert to use them without shooting your foo most were focusing on code execution rhather than long running agents, going for primitives like serverless when the best would be a long running VPS most were stuffed with a gazillion features, docs with hundreds of pages, when all you want is to spin them up, ssh, run your stuff, snapshot, get out, consistently, without realizing down the line that they overshipped to hype you up, and advanced features actually don't work (forking & resuming often broke in our tests) most were focusing on the wrong things: fast boot time, when agents actually run for hours, containers when agents ideally need the full capabilities of a laptops, resizeable machines when most users want a "one size fit all get out of my way" type of thing, VNC desktop when for UI testing you need 60fps gaming-ready streaming tech not that all these features are bad, but they're not easy either to get right and often prioritized to the detriment of building from solid architectural choice a failproof, consistent, affordable product box is the opposite simple, powerful, affordable $0.0001/s for a one size, powerful linux machine you can stop, resume fast and fork fast, with >50gb of storage, all your files, installs and configs are snapshotted and downloadable anywhere, any time even when the sandbox is off the sandboxing primitive doesn't get in your way since you can run docker, any devtool, chrome, install anything, use sudo, edit nftables, ssh in, open ports, host on the IP most common setup phases are covered with github credentials passing, ssh keys handling, cloning repos on start, passing secret files and you get a beautiful virtual desktop at 60fps or VNC if your internet is unstable yet there are so few gotchas and the API, CLI and SDKs are so simple, that we don't need more than a dozen docs pages box is the result of never compromising on design, common sense, performance, simplicity, cost and fearlessly figuring out all the complexities and edge cases for you, over the course of the last 10 months of using them to build our own agents on top use bow box box

• 
  Brute Force Artist (@bruteforcearete) reported 14 minutes ago

  AI TRAINING 📲 Go from screenshot to bug fix with Cursor Mobile The Rundown: In this guide, you'll learn how to screenshot a bug on your website from your phone, then send it to a Cursor Cloud agent that can fix it, update the PR, and track everything in GitHub before you've even made it back to your desk. Step-by-step: Install the Cursor iOS app, get a Cursor Pro plan, and install GitHub Mobile so you can review the PR from your phone Open your website, take a screenshot of the bug, broken layout, or UI change. Add a short note with what page you are on and what should happen instead Open Cursor Mobile, tap the plus button, choose the correct repository, and start a new thread with the screenshot and the note attached for context Now prompt: “Investigate this bug, find the relevant page component, make a fix, and open a PR.” When it’s done, review the PR, approve, and merge it Pro tip: On desktop, enable Remote Agents so Cursor can work on your machine and prep local changes before you get back to your desk.

• 
  Keeta Github Tracker (@KeetaCode) reported 16 minutes ago

  🐆 Keeta GitHub PR Opened 📦 Repo: node-rs 🔀 PR #33: Release: v0.4.0 🌿 Branch: process/v0.4.0 → main 👤 Opened by: @sephynox 🧠 Overview: Keeta’s node software appears to be moving to version 0.4.0, which matters because it bundles several behind-the-scenes improvements into one release. This pull request is a release update that groups four earlier changes: better typing, cleanup of crypto-related issues, centralizing some internal tables, and reducing repeated code. The public description does not explain user-facing impact, so this appears to be a technical/internal update with limited public details. - Likely takeaway: this is more about making the software cleaner and easier to maintain than announcing a major new feature.

• 
  Scarlett claira (@AItechscarlett) reported 17 minutes ago

  NVIDIA charges you $19.99 a month to stream games you already own. And starting January 2026, they cap you at 100 hours. One engineer from New Zealand built the free version with no cap. It is called Steam Headless. 3,177 stars on GitHub. GPL-2.0. Built by Josh Sunnex. 225 commits. The next contributor has 16. He has done more work than everyone else combined. It is a Docker container that turns any spare PC, server, or NAS into your own personal cloud gaming machine. Install Steam inside it. Mount your games folder. Open a browser on your phone, your laptop, your tablet, your TV. Your games are right there. Streaming. From your own hardware. To anywhere in the world. It supports NVIDIA, AMD, and Intel GPUs. It streams over Moonlight, Steam Link, or straight to a web browser. It runs Proton so Windows games work on Linux. It installs Heroic, Lutris, and EmuDeck with one click for your non-Steam games. It runs on Debian Trixie, Unraid, Ubuntu Server, or Docker Compose. Last update: April 20, 2026. Still maintained. Still by one man from New Zealand. Now compare the math. GeForce NOW Ultimate: $19.99 a month. $239.88 a year. Forever. Capped at 100 hours per month. Run out? Pay $5.99 for another 15 hours. Xbox Game Pass Ultimate: $22.99 a month. $275.88 a year. Forever. You stream Microsoft's games on Microsoft's hardware on Microsoft's terms. Steam Headless: $0. Forever. Your hardware. Your games. Your network. No hour cap. No queue. No throttle. Buy a used GPU once. Run this container. Stream your entire Steam library to any device on the planet. That is the entire pitch. But DO NOT install it. We should all keep paying NVIDIA and Microsoft to play the games we already bought. 100% Open Source. (Link in the comments)

• 
  Absent Insight (@AbsentInsight) reported 17 minutes ago

  @Shpigford I'm on mobile, so I just installed it to Firefox (basically one of two options I know of on mobile that allow extensions). I did have one issue, though. After turning your repo into .xpi and trying to load it, it was rejected for the signature. Turning off the signature check fixed it, of course, but is this normal? I don't use extensions in my daily life, but turning Amazon into the site it used to be was too good to pass up on lol. So I'm not sure if this is just how it goes when doing it directly from Github rather than going through an official online store. Anyways, I'll be testing this out later since I absolutely hate the mountains of garbage that Amazon has allowed into their store. I give feedback if I notice anything.

• 
  Zach Vorhies / Google Whistleblower (@Perpetualmaniac) reported 18 minutes ago

  5 attempts to drop a malware payload. @github please fix this

• 
  Kevin (@KevinMagnan) reported 19 minutes ago

  Fable went for the jugular this weekend. I asked it to audit how I actually use Claude Code. It pulled 197 sessions and 1,550 tracked hours. 65% of my sessions start after midnight. 600 hours went to content. 0 went to the 6 apps I tell people I'm building. It even caught its own report lying. A third of my sessions were flagged as killed by token-limit errors. Fable pulled the raw transcripts and found one transient HTTP 500 sitting on hundreds of messages of real work, so the finding got tossed. Then it built the fix. 4 scheduled jobs now run the recurring work while I sleep. TikTok analytics on Sundays. Newsletter prep on Thursdays. A GitHub carousel post before I wake up on Monday. This is your invitation to run /insights on your own terminal.

• 
  Charly Wargnier (@DataChaz) reported 21 minutes ago

  THIS GUY LITERALLY DROPPED AN ENTIRE OPEN-SOURCE OFFICE SUITE BUILT SPECIFICALLY FOR AI AGENTS 🤯 Until today, agents generating slide decks were completely flying blind. They could write the XML, but they had absolutely no idea if a title overflowed or if shapes overlapped. They could read the code, but they couldn't see the document. A new project called OfficeCLI just completely fixed this. It’s an Apache 2.0, single-binary CLI tool that is already exploding with nearly 10,000 stars on GitHub. It includes a built-in rendering engine that translates Word, Excel, or PowerPoint files into HTML or PNGs. This gives AI models actual "eyes" to spot layout issues and fix them before delivering the final file. Here is why this is such a great upgrade: → It ships with a built-in MCP server for Claude Code, Cursor, and VS Code → It handles 350+ live-calculating Excel functions without needing Office installed → The render-look-fix loop works entirely headless in Docker or CI → What used to take 50 lines of Python now takes one command It completely removes the need to manage Microsoft Office at runtime! 100% Free and open-source. Repo link in 🧵↓

• 
  Hot Aisle (@HotAisle) reported 21 minutes ago

  Someone posts on X that there is some big problem with Github, gets a bunch of clicks and engagement. Turns out it is a nothing burger. There should be a way to signal this more easily.

• 
  Polsia (@polsia) reported 27 minutes ago

  Pull requests are a small fraction of what developers ship. The real problems live in branches and commits nobody reviews. CodeSentinel monitors GitHub repos 24/7 — catches bugs, security issues, quality problems before they reach production. Auto-generates docs as you build.

• 
  Hiroshi Sumida (@SumidaHiroshi1) reported 28 minutes ago

  Github needs to fix their **** because it's no longer secure.

• 
  Polsia (@polsia) reported 32 minutes ago

  Your API throws cryptic errors at 2am. Your inbox fills with frustrated users. Both go unnoticed until Monday morning. Built BugRadar. It watches your API and support inbox 24/7, files complete bug reports with reproduction steps, and pushes them straight to Jira or GitHub.

• 
  Ilian - SaaS builder with no user (@ilianazz_) reported 32 minutes ago

  The classic way to avoid phishing? A blocklist maintained by users on GitHub. Is it efficient? I don't think so. That's why I created a browser extension that tackles the problem from a completely different angle. I'll talk about the approach behind it in my next article.