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:

• 
  tmo (@tmophoto) reported 7 minutes ago

  @DabsMalone i had an old email account from like 15 years ago with bot in the name that i fired back up after 10 years and used for a hermes profile and it got immediately banned. i used it to sign in to x, github, everything. was a huge hassle

• 
  tobarra (@txbrraa) reported 7 minutes ago

  GitHub just fixed the biggest problem with vibe coding. They just released Spec Kit and it already has +126K stars in a short time. The idea? Instead of throwing out vague prompts and praying the agent doesn't break your project… Spec Kit forces the AI to create a structured specification BEFORE touching any code. The AI first understands what you want to build, asks about anything missing, organizes the project, and only then starts coding. That means less time fixing absurd bugs, less inconsistent code, and much more predictable results when working with agents. The flow is simple: /constitution → rules and standards /specify → what you want to build /clarify → open questions before starting /plan → architecture and stack /tasks → ordered tasks /implement → execution Compatible with Claude Code, Cursor, Copilot, Codex, Gemini CLI, and +25 agents. 95K stars. 8K forks. Open source. Published by GitHub.

• 
  ATP (@ATPinsights) reported 8 minutes ago

  GitHub CLI just added image and video attachments today. Here's what you need to know. The gh command line tool now supports a repeatable --attach flag. It uploads a local image or video file and references it inline in an issue, pull request, or comment body. The feature is live now for all users on GitHub. It's aimed squarely at developers and coding agents that need to show visual proof, like before-and-after screenshots, directly from the terminal instead of the web UI. Developers reacted fast. Many called it a long-overdue fix for a common workaround, since teams previously built custom tools or scripts just to upload images to PRs from the CLI. Key facts: - New flag: --attach - Supports: images and video - Repeatable: yes, use it multiple times per command - Works in: issues, pull requests, comments - Availability: all users, live now No separate app or upload API is needed, the flag handles it inside gh itself.

• 
  isha (@heeyyaaaaaaa) reported 17 minutes ago

  spent the entire day trying to reproduce a bug for a github issue 🥀🫩

• 
  Mr. Buzzoni (@polydao) reported 18 minutes ago

  LOOP RAT ROADMAP: WHAT'S NEXT, AND WHAT IT'LL NEVER BECOME v0.3.3 today. 3 loops, 55 checks, 0 services here's where it's headed: > 0.4 - read the night faster: rat watch live-tails a running shift, rat replay reruns one from its saved prompt, a weekly digest instead of seven separate pages > 0.5 - off the laptop: run-due moves into GitHub Actions, state lives on a branch, rat cron --launchd survives a closed lid > 0.6 - sharper graders: swappable rubric packs, two graders disagreeing becomes your queue for the day > 0.7 - the work itself: a worktree per shift, so a failed night never dirties your tree > 1.0 - trust: a hash-chained trace nobody can quietly rewrite what it will never have: > no web dashboard - the terminal already knows where the files are > no database - plain files outlive the tool that wrote them > no hosted service - nothing to sign up for, nothing to shut down > no auto-merge - the rat proposes, the morning decides every item ships behind a flag: dry run -> report only -> one repo -> a week of receipts -> default on a feature that can't run as a dry run doesn't get written the rat is boring on purpose. every version keeps it that way

• 
  Eddie Jaoude | DevRel | Open Source (@eddiejaoude) reported 18 minutes ago

  I have many tokens to burn before tomorrow after the Claude reset. Send me your GitHub issues with context 👇

• 
  Ares (@neko23423) reported 19 minutes ago

  I compared the latest OpenClaw vs Hermes Agent GitHub releases so you don’t have to. OpenClaw 2026.8.2 (Sep 1) vs Hermes Agent v0.21.0 (Aug 31). Not a feature-page remix. The actual repos. OpenClaw • 388,516 stars • 81,568 forks • ~86,300 commits • 6,070 open issues Hermes Agent • 239,503 stars • 48,930 forks • ~26,980 commits • 38,563 open issues Hermes is the smarter learner: skills from experience, cron that remembers, Bot Mode, hermes peer. OpenClaw is the personal-AI operating system: iMessage, iOS/Android, Linux companion, team Gateway, signed Foundation releases. The tell: Hermes ships `hermes claw migrate`. You only write a migrator for the incumbent. King in 2026: OpenClaw. Heir with the better mind: Hermes. If you’re picking a self-hosted AI agent this week, that’s the split. Bookmark this. The timeline is about to fill with takes from people who didn’t open either repo. OpenClaw vs Hermes Agent. Latest version. Real numbers.

• 
  dug_vt (@dug_vt) reported 19 minutes ago

  @sonemic rym users don’t use spotify they download flacs off soulseek and transfer them to a server connected to their pc and play them from a self hosted music player from github

• 
  Convequity (@convequity) reported 21 minutes ago

  Snyk is a clean postmortem for what happens when a security tool lives inside the coding agent’s loop. The product was mostly scan-and-warn. Find the issue, comment on the PR, suggest a fix. Blocking the merge usually sat in GitHub, not in Snyk. Bigger platforms smothered it. $PANW, $CRWD, and Wiz pulled AppSec into the bundle the CISO was already buying. GitHub was the main developer surface and put scanning where the code already lived. Then coding agents arrived and delivered the final blow. A lot of that scanning became something the agent could just do. Growth held up for a short while after the COVID/cloud tailwind. Then it decelerated hard. This is the same lens we use in Convequity’s SaaS Agentic Survival Evaluation Framework. The PANW, CRWD, and FTNT reviews go up on Convequity in a few days.

• 
  wiiiimm (@wiiiimm) reported 27 minutes ago

  @Umesh__digital stop doing it. we don't need another github outage.

• 
  Hua-**** Xiong (@HuaDongXiong) reported 28 minutes ago

  Codex for Windows stopped launching after an update. Multiple github issues opened for 2+ weeks. This affect users who set the MS store install location to a non-C: drive. Mac version is buggy too. ofc coding is solved! @thsottiaux

• 
  Dr Milan Milanović (@milan_milanovic) reported 30 minutes ago

  How Cursor made *** scalable The thing with *** is that it never was designed to be scalable. Your repo lives on the disk, and *** client expect every read to be consistent. This was a problem on GitHub, where shared filesystems and replicated storage failed before 2013. The GitHub built 𝗦𝗽𝗼𝗸𝗲𝘀, and it became the industry standard. This means that every repo is stored as three full copies on three servers, and every push runs a vote (three phase commit). A majority of servers must confirm before it exists. This works, but with high cost, because every push is slow as the slowest server. When we add new servers, it makes it even slower. Now Cursor took some opposite direction with 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗶𝘁𝘆. The repo history is now written as a log in S3, and this is only source of truth. Any push counts only if it is located in the log. The servers don't need to keep anything important, they are just cache. Any server can take a push, and idle repos are dropped from disk and rebuilt from the log when it is needed. This resulted in 120 pushes per second on standard S3, and over 300 on S3 Express. Their tests have shown that read capacity grew linearly up to 100 replicas. Why is this important now? Because of AI agents mostly. We now have more code, PRs, CI runs and many small repos. All of these repos would need three full copies in the old model. This means that we achieve scale by removing parts, not adding them.

• 
  Slade 🛡️ LLM Hacker (@llm_redteam) reported 31 minutes ago

  GitSpawn is the name Manifold Security gave to a bug class hitting 7 CLI coding agents at once: goose, Claude Code, Codex, Cursor, Hermes Agent, Qwen Code, Grok Build. I went through the disclosure because I run three of these tools daily on real repos. The mechanism is simple and that's what makes it bad. A repo's own .*** config can name a command. When your agent does something as routine as inspecting the repo (status, diff, log), *** itself spawns that command. On your machine. Outside the sandbox. No approval prompt, because the agent never sees it as "running code," it sees it as "running ***." 8 flaws total across those 7 tools. Fixes shipped for goose, Claude Code, Cursor. Retested Sept 1: Hermes Agent, Qwen Code, Grok Build still exploitable. Plus a second path in Claude Code that the first patch didn't close. Same day, OpenAI published 3 CVEs for Codex covering the identical bug class. The part that should worry builders more than the CVE count: this isn't a jailbreak or a clever prompt. It's a trust boundary nobody drew. The agent's sandbox model assumes "*** operations" are safe by definition. GitSpawn shows that assumption was the actual attack surface. If you're running any of these agents against repos you didn't write yourself (cloning a PR to review, pulling a dependency, opening a random GitHub project), you're one `*** status` away from arbitrary execution on tools that haven't patched. Check your agent's version against the fix list before you clone the next unfamiliar repo. Which of these do you have installed right now, and have you actually checked if it's patched? #AISecurity #GitSpawn #PromptInjection

• 
  Jason Sawyer (@foilmanhacks) reported 37 minutes ago

  There's a huge problem in InfoSec education: it’s way too course and tool focused. Instead of teaching the underlying methodologies and how to discover or invent, we feed people the latest "OSINT" slop script that’s been shat onto GitHub. OSINT isn’t about using scripts or services. It’s about understanding how they work, and being able to create your own.

• 
  Anime0t4ku (@Anime0t4ku) reported 41 minutes ago

  @c_hri_s Yeah this has been reported in previous github issues. Its out of my control. The app is unsigned and uses ssh, sftp, websocket and mutiple websources. A perfect recipe for false positives.