GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (53%)
• Errors (32%)
• Sign in (15%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Paris	Website Down	5 hours ago
Ahmedabad	Errors	6 days ago
Delme	Sign in	7 days ago
Lyaud	Website Down	7 days ago
Catania	Errors	9 days ago
Inverness	Website Down	21 days ago

Full 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:

• 
  Bruno (@BrunoRJ33) reported 3 minutes ago

  @openclaw @github Endless codex and claude code tokens to fix it from time to time… and to improve its harness. I currently run around 10 claws 🦞. 24/7 for several purposes.

• 
  Kun Chen (@kunchenguid) reported 4 minutes ago

  @petergyang yo @myfirstmate peter just told me his skills are all at user level. backpass currently only runs things at project level i want a proposal for making backpass support a user level run. put that into a github issue use fable for peter

• 
  Azzie (@Motier_crypto) reported 4 minutes ago

  $Looprat 473K 0x642d30c84211ade7768fe557fbaed7224e2068c7 How do you get a coding agent to keep working while you sleep—without letting it randomly rewrite code, blow through the budget, or grade itself a perfect score? Loop Rat breaks an unattended task into: preflight → act → verify → guard → grade → receipt. The agent is woken up on a schedule to execute tasks. The code results first go through deterministic verification. Then it checks the denylist, the number of modified files, and secrets. Finally, a second independent agent regrades the work, with checkpoints, traces, and receipts left throughout the entire process. More importantly, this isn't a PPT. The project only had v0.1 on August 27. Then it added guard, kill switch, and spend ledger on August 29. On September 1, it added second-agent grading. On September 2, it continuously fixed scheduling, budget caps, timeouts, and concurrent ledgers. Today, September 3, it's already updated to v0.3.3. Shipping multiple versions in under a week—that's exactly what I want to see in a small-cap play like this: code is running, and the narrative is following the product, rather than launching a token first and filling in the story afterward. It currently defaults to Claude, but it doesn't lock the model down. As long as the CLI can consume a prompt and return JSON, it can be swapped. And the whole thing runs locally—no SaaS, no database, no extra accounts required. The project has even already run 50 smoke checks covering key areas like scheduling, guard, budget, kill switch, and timeout. So my trading logic for $Looprat is simple: The next phase of the agent race isn't about "can it work autonomously." It's about "can it work continuously while still being constrained, audited, and stopped." Loop Rat happens to be building exactly that layer of infrastructure. The project is still very early. The catalyst truly worth watching isn't shilling—it's whether the GitHub keeps up this iteration speed, and whether developers actually start plugging it into their own repos. Once those two things happen, $Looprat stops being just a ticker riding the agent hype, and starts having its own fundamental anchor.

• 
  Kahris (@chrissotraidis) reported 9 minutes ago

  @NickogSo I haven't tested on LiveContainer. Feel free to submit logs via GitHub issues and I'll check it out. I haven't had any other reports of that happening for either build.

• 
  Gregor (@bygregorr) reported 10 minutes ago

  @dopabees ngl the broken wrist is the only github metric that's ever made me believe a commit history

• 
  Russ Wonsley (@RussWonsley) reported 11 minutes ago

  My @bot tells me that the official GitHub login for bot is still broken. Has this been addressed already, or did I miss it?

• 
  Nas (@TheNasFi) reported 12 minutes ago

  $MSFT changed its reporting structure today. Starting in FY27, Microsoft will report just two segments: Agents & Infra Devices & Consumer Agents & Infra includes Azure, Microsoft 365, GitHub, server products and industry solutions. For context, those businesses generated $268B in revenue last year, compared with $64B for Devices & Consumer. Microsoft also recast its Q1 guidance under the new structure: Agents & Infra: $75.15B to $75.75B Devices & Consumer: $14.7B to $15.2B There is no change to total revenue guidance. These are the same numbers Microsoft gave in July, reorganized under the new segments. Mostly a reporting change, but an interesting look at how Microsoft now groups the majority of its business internally.

• 
  Rafael Audibert (@RafaAudibert) reported 15 minutes ago

  @madebygps @github Tried using it with my agents (the main benefitor from this) but it doesnt really work because you cant use it with GitHub app user tokens (ghu_). Can that be changed somehow? All cloud agents will have that problem, and most of our coding happens trough cloud agents now

• 
  radhika (@RaadhikaThacker) reported 15 minutes ago

  YAML’s more like a rule book/recipe that builds the form for you. Then I figured YAML was a forms thing. Nope. It’s just a way of writing information down in a structured way. GitHub uses it for a form. Kubernetes uses the same thing to describe a server.

• 
  Swish (@swish_salt) reported 17 minutes ago

  The technology is not the problem. Distribution is. I have a solution sitting in my GitHub account. All we need is the funding to build the distribution team.

• 
  NitroStack (@nitrostackai) reported 21 minutes ago

  The missing primitive might be capability contracts. A Skill shouldn’t say “call Jira.” It should say “I need issue.write.” Then MCP can bind that capability to Jira, Linear, GitHub… whatever exists. That’s basically dependency injection for agents.

• 
  GitHubGPT (@GitHubGPT) reported 28 minutes ago

  📛 chrome-devtools-mcp 🧠 An MCP server that allows AI coding agents to control, debug, and automate a live Chrome browser using Chrome DevTools. 💻 TypeScript ⭐ 50605 🍴 3551 🔎 ChromeDevTools/chrome-devtools-mcp on GitHub

• 
  Yeemio (@yeemio) reported 32 minutes ago

  owlrunkit is on github now. public corresponding source for the npm package. issues go here.

• 
  Rituraj (@RituWithAI) reported 33 minutes ago

  🚨 Someone built the complete playbook for running frontier AI models on consumer GPUs at home. Not a tutorial. Not a YouTube video. A production-grade serving stack with measured benchmarks, working configs, and battle-tested recipes — for RTX 3090 owners who want real performance. It's called club-3090. And the numbers it delivers should not be possible on consumer hardware. 127 tokens per second. Qwen3.6-27B. Two RTX 3090s. 262K context window. Vision. Tool calling. At home. Here's what's actually inside. Two serving routes — pick based on what your workload breaks on. vLLM dual: maximum throughput. 89-127 TPS on code tasks. 4 concurrent streams at 262K context. Full feature stack — vision, tools, speculative decoding, streaming. This is the path if speed matters. llama.cpp single: maximum robustness. Full 200K context on one 3090. No prefill cliffs. 25K-token tool returns work correctly. 91K needle ladder passes. ~51-60 TPS — slower than dual, but doesn't crash on real-world agentic workloads. Both routes ship as validated Docker Compose configs. Drop-in OpenAI-compatible API on localhost:8020. Your Claude Code, Cursor, or any OpenAI-compatible client connects immediately. Here's the model support that makes this practical. Qwen3.6-27B — production ready. Works on 1 or 2 cards. vLLM, llama.cpp, ik_llama. Up to 262K context. Gemma 4 31B — production ready. Vision, tools, up to 106-141 TPS on dual cards. Qwen3.6 35B-A3B MoE — production ready. 103-149 TPS single card. 178 TPS dual. Here's the wildest part. The terminal UI. c3 is a lazydocker-style cockpit that wraps discovery, serving, and operations in one keyboard-driven interface. Browse the model catalog, serve a variant with Enter, watch live GPU stats, run health checks — all without touching the CLI. Here's why this is different from just installing Ollama. Ollama gets you running. club-3090 gets you benchmarked, stress-tested, and production-hardened. Every config ships with a verified TPS measurement. The bench script runs 3 warmup + 5 measured passes. The stress test catches the specific prefill cliff that Ollama silently fails on at long contexts. When your agent starts doing 25K-token tool calls at 3am and something crashes — club-3090 already found that failure mode and documented the workaround. One command to start. Your RTX 3090 just became a frontier AI inference server. Apache 2.0 License. 100% Open Source. GitHub link in the comments 👇

• 
  Jeremy Scott (@listwithjeremy) reported 34 minutes ago

  @Coexisteven @Atropa_414 @atropa_pls Github is down I see......anywhere else we can read...I've been digging in it when I can since I was kindly introduced.

• 
  Slade 🛡️ LLM Hacker (@llm_redteam) reported 34 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

• 
  Martin Tobias (Pre-Seed VC) (@MartinGTobias) reported 38 minutes ago

  if you know any founders who are winding down, I may have a buyer of their github repos. DMs open.

• 
  Rachael LaGoth (@androidsheeep) reported 41 minutes ago

  @bcherny Please fix the desktop app it's very buggy it keeps disconnecting me for no reason everyday while im working on stuff, i submitted a report but nothing happened and someone else is having the same issue, an issue is open on github for more than 6 months with no solutions help

• 
  Uptimus (@UptimusApp) reported 42 minutes ago

  Sep 02, 2026 at 13:29 UTC: Semaphore reports that periodic authentication failures with GitHub repositories are linked to a wider issue affecting HTTPS operations.

• 
  Charles McDowell (@charlesmcdowell) reported 43 minutes ago

  @openclaw @github I still just want to know why there was even a new release of OpenClaw with nothing new that could compete with Hermes Agent? I was really excited for the release. Then, just like what seems like everybody else, incredibly let down.

• 
  Chris Gilbert (@0xgilbert) reported 44 minutes ago

  Damn, GitHub has gone to ****. Features that have been cornerstones of solo devs and small businesses have been gutted or broken for months. How the mighty have fallen…

• 
  Ares (@neko23423) reported 48 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.

• 
  David Abram 🐊 (@devabram) reported 48 minutes ago

  Discord is down. X is down. GitHub is down. Software is solved.

• 
  Anders (@AndersReiche) reported 48 minutes ago

  @bjmtweets Would love to hear your thesis on gitlab. I’m a software engineer, and in my experience, gitlab has been slow to everything and generally is the red headed stepchild next to GitHub. It suffers from lack of network effects, there are solutions to everything on GH, but not GL.

• 
  Bash (@bashirbuilds) reported 48 minutes ago

  Your Stripe account can be healthy while your checkout is broken. OpenAI can be operational while your AI feature is failing. GitHub can be up while your deployment workflow is stuck. That’s the problem I’m building Reeno around. Dependency uptime is not the same as product health. Your monitoring should tell you when the thing your customers actually use stops working.

• 
  Lily (@lobstermindset) reported 49 minutes ago

  @nnnnicholas i just setup a github issues board, will probs try out linear if it's not sufficient

• 
  dug_vt (@dug_vt) reported 50 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

• 
  Curious Explorer (@PatelVatsalp732) reported 50 minutes ago

  I burned 14B Codex tokens. The official usage UI still cannot tell me what actually ate the weekly cap. So I shipped a Codex-only board: GitHub login, local-first sync, private by default, optional public rank + shipping proof. Roast the metric or join it.

• 
  Bash (@bashirbuilds) reported 50 minutes ago

  One of the hardest things about building a SaaS product today: You don't control most of the systems your product depends on. Stripe. OpenAI. AWS. GitHub. Resend. Clerk. Your code can be perfectly fine and your product can still break because something outside your code changed. The more dependencies you add, the harder this becomes. That's the problem I'm building Reeno to solve.

• 
  OverlyPositivePatriot (@JBrowsing2023) reported 52 minutes ago

  As a IT professional, I have a recommendation @github should take seriosuly. We should only get a notifican from Github when it is up rather than when it is down. Reliability is a disaster for this product.