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 (55%)
• Errors (32%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	3 days ago
Ahmedabad	Errors	9 days ago
Delme	Sign in	10 days ago
Lyaud	Website Down	10 days ago
Catania	Errors	12 days ago
Inverness	Website Down	25 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:

• 
  Max Rovensky (@MaxRovensky) reported 1 minute ago

  @thekitze you'd be even further down if you fixed the GitHub bug I just reported

• 
  Eddie Jaoude | DevRel | Open Source (@eddiejaoude) reported 1 minute ago

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

• 
  Farley (@FarleySchaefer) reported 1 minute ago

  @github Hope this doesn't bring down GH

• 
  Gregor (@bygregorr) reported 2 minutes ago

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

• 
  Dhanji Bhagat (@BhagatDhanji) reported 3 minutes ago

  Devs, what's your workflow? Create an issue first, then fix it OR just fix the bug and push directly to GitHub?

• 
  Kim Burgaard (@kimburgaard) reported 4 minutes ago

  Back when GitHub added Copilot PR reviews, it helped me keep up with the growing volume and size of our pull requests, which were increasingly being written by Copilot too. Over time I grew comfortable feeding Copilot's review comments straight back to Copilot to fix, and mostly spot checking when critical functionality was involved. When GitHub updated the Copilot pricing model I switched to Claude Code, but kept the Copilot review feature on for a couple of months. When the monthly bills for Copilot AI usage alone started rivaling the Claude Code Max plan, giving Claude Code PR review duties seemed like an obvious cost saving move. Plugging Claude Code into our PR review process immediately went south. The first PR churned with fixes to findings that resulted in more findings, and fixes that propagated up and down the call chain. I threw the PR away and started over, but the next attempt churned just as badly. Turn count on its own was never the signal. Copilot had taken ten turns on a rate-key cleanup the day before and nobody minded, because the findings thinned as it went — 5, 4, 3, 3, 3, 4, 1, 2 — and it merged. The cached-token billing PR I put through Claude Code took nine turns and produced 123 inline findings, and the ninth round was still returning fifteen. I closed it without merging. Looking closer at Claude Code's review findings, it was clear it reported far more issues than Copilot ever did, and among legitimate bugs and concerns, it made lots of comments about latent and speculative issues including possible race conditions and error propagation, things Claude Code would then try to fix one by one in isolation, often ignoring existing patterns in the code base. The code-review workflow is built into Claude Code and cannot be customized other than a few options, so the only place to intervene was on the other end, in the session where I used to just ask the coding agent to address the review findings. The first improvement was to direct Claude Code not to blindly fix all findings, but to defer findings not directly related to the task at hand to new issues. That helped reduce the PR churn, but blew up our issue backlog. The next improvement was to ask Claude Code to ignore speculative findings and disregard most latent findings unless they indicated high risk of unrecoverable damage in production. Finally, I had to stop Claude Code from authoring prescriptive issues with detailed implementation instructions. The result is a skill that triages PR review findings, and a skill for authoring and updating issues. After a few iterations of the skills, I've been able to complete ten PRs over a couple of days, bringing back the pace we had before. I've made the skills available in a public GitHub repository (link in the first reply). Let me know if you find them helpful.

• 
  Spectra☢️ (@Spectra010s) reported 5 minutes ago

  @izzyCodes_ and you too Chief Check GitHub issues

• 
  NitroStack (@nitrostackai) reported 18 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.

• 
  Suryansh Tiwari (@Suryanshti777) reported 22 minutes ago

  6. The Dependency Incident Check Grok has native real-time search across X. Breakage gets posted there hours before the GitHub issue is triaged. No other coding model has that feed. "You are a build engineer whose first move on a broken pipeline is to work out whether it broke for everyone or only for me. Search X and the web, last 14 days. Check: - Is anyone else reporting this failure with this package and version, and when did the reports start - The exact release that changed behaviour, and the changelog line that admits it - Whether maintainers have acknowledged it and what they recommended - The pin or patch people settled on, with the tradeoff of each - Whether this is my problem instead, and what evidence points that way Give me the verdict in the first line: their bug or mine. Then the evidence, newest first, with links. My failure: [PASTE THE ERROR, THE PACKAGE AND VERSION, AND WHAT CHANGED ON YOUR SIDE RECENTLY]"

• 
  Mr. Buzzoni (@polydao) reported 24 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

• 
  Russ Wonsley (@RussWonsley) reported 25 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?

• 
  joithan (@jothantranston) reported 27 minutes ago

  THIS GUY BUILT A TINY AMOLED DESK BOARD JUST TO STARE AT HIS STRIPE NUMBERS it's a Waveshare ESP32-C6 touch panel that sits in your peripheral vision and cycles business metrics so you stop digging through Stripe > same ESP32-C6 board people use for Claude Code token meters, flipped to revenue > eight screens, five seconds each: MRR, new paid, paid subs, cancelled, ARR, ARPU, net 30d, failed > empty screens hide themselves so a young account sees a shorter loop > polls Stripe every five minutes on a read-only key (subscriptions + invoices) > marks itself stale instead of showing a number it can't vouch for > no soldering: flash over USB, finish Wi-Fi + key setup from your phone > data stays on the board; no project server in the middle firmware free on GitHub: cosjef/stripe-desk-display. board ~$30–$36 (Waveshare ESP32-C6-Touch-AMOLED-2.16). chat and terminal can't sit in your eye line for five hours. a tab you have to open is a tab you stop opening. this is what "the numbers find you" looks like as a brick on the desk.

• 
  Duncan Rogoff (@DuncanRogoff) reported 27 minutes ago

  nine stages, one build, one move tonight. it's a Claude Code skill i built. free, in my freeskills repo. it's called Claude Orientation. you type /claude-orientation and answer two questions: which stages you've actually finished, and every project you're currently thinking about. beginners don't fail from lack of ideas. they fail from having five and finishing none. that's a sequencing problem, and this fixes the sequence instead of your willpower. - places you on a 9-stage beginner arc: install, memory, website, landing page, skills, game, agents, content, distribution - your stage is the first one you haven't finished, so it won't let you skip - cuts your project list to one build, then shrinks it until it can ship in five 90-minute nights - writes five nights of one-line moves, and night 5 is always send it to a real person - hands you the exact text to paste into Claude tonight - sketches a 30-day arc, one line per week, so you know what comes after - everything that got cut goes in a parking lot, so nothing feels lost - saves all of it to a roadmap file you reopen every session so you finish one live thing this week instead of holding four half-built folders forever. open the file, do the move, rewrite the next line before you close the laptop. no setup. copy the folder into your skills directory, restart, and you have a plan for tonight. free, and it stays free. 👉 github repo in the replies

• 
  Gordo Polymath (@gordo_polymath) reported 29 minutes ago

  @github Please fix gh stack.

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

• 
  Azzie (@Motier_crypto) reported 29 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.

• 
  Pranavvv👾 (@pranvv27) reported 31 minutes ago

  honestly, i’m not even mad at this. commit messages are a small thing, but they say a lot about how you work. “fix”, “update”, “changes” might get the job done, but meaningful commits show professionalism, attention to detail, and that you actually care about maintainability. your GitHub is part of your resume. might as well make it look like you know how software is built in a team.

• 
  Curious Explorer (@PatelVatsalp732) reported 34 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.

• 
  LLL (@triplellltrbl) reported 34 minutes ago

  You know it's so funny to me That in today's age there are so many people that are just straight up copying workflows, AI automations or GitHub repos Without even thinking twice about what the workflow actually does or how it works They just watch some video, see the output, think, "Oh that's cool. I want that," and then try it Then when it doesn't work they get angry, upset, and say that AI is crap or prompting isn't real The issue wasn't the system or the prompt It was a fact that the system wasn't made for you and you don't actually understand it

• 
  AI Scientist (@AIScientist_X) reported 35 minutes ago

  NEWS: X LANDS FIRST PUBLIC ALGORITHM PR > X OPEN SOURCE SAID SEP 1 THAT AFTER 2 PLUS WEEKS OF DAILY UPDATES IT INTEGRATED A FIRST PUBLIC CONTRIBUTION AND THAT THE CHANGE IS NOW LIVE ON X. > IT SAID THE SMALL UPDATE IS BASED ON GITHUB PULL REQUEST 55. X CLOSED THAT PR AS COMPLETED AFTER LANDING ITS OWN FIX. SOURCE: X OPEN SOURCE

• 
  R 'Nearest' Nabors (they/them) (@rachelnabors) reported 35 minutes ago

  @Paul_Kinlan Honestly, the linear method helps. Think of it as having a never-ending trough of issues that agents can pull from. I don't even use linear. I just use GitHub with linear flavouring added

• 
  rajabi17270.eth (@rajabi17270) reported 36 minutes ago

  @SeismicSys An Ethereum engineer opens an install page expecting a binary download that finishes before the coffee does. Seismic asks for Rust and cargo first, then budgets five to twenty minutes for the build. That gap is the most honest line on the page: you are not installing a tool, you are compiling a fork of the execution layer on your own machine. Three binaries come out of sfoundryup. sforge as the testing framework, sanvil as the local node, ssolc as the compiler. Each shadows a Foundry tool by exactly one letter, and the docs give the mapping outright: forge becomes sforge, anvil becomes sanvil, cast becomes scast. The s is not decoration. The s is a namespace. The s is the migration guide, compressed into one character and carried from the type system all the way up to the binaries sitting on your PATH. Why a fork and not a plugin is the question the install page answers without asking it. Privacy on Seismic lives in the type system, so solc had to become ssolc to understand suint256 and route it to CLOAD and CSTORE instead of SLOAD and SSTORE. Because the compiler changed, the build harness that invokes it changed with it. Because the emitted bytecode carries opcodes standard revm does not implement, the local node had to be rebuilt to execute them, and because each storage slot is a value paired with an is_private flag, the CLI that queries storage had to expect a different answer than Ethereum's. Four forks, each one forced by the layer beneath it. Not a toolchain that was extended. A toolchain that had no choice. The installer itself carries a detail worth reading twice. It is fetched through the GitHub Contents API with an Accept header of application/vnd.github.v3.raw, from the seismic-foundry repository, at ref equals seismic. That ref is a branch name, and a branch name tells you the maintenance posture: the fork lives beside upstream rather than in a codebase that has stopped speaking to its parent. A rebase relationship, not a divorce. You source your shell profile twice during setup, once after the installer lands and once after sfoundryup finishes. Two separate PATH mutations, because the thing that installs and the thing installed arrive at different moments. What survives the fork is more interesting than what changed. sanvil serves localhost:8545 with pre-funded accounts, and the deployment example uses the same well-known development key Foundry users already have in muscle memory, address 0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266. sforge init, sforge test, sforge script with rpc-url, broadcast and private-key flags: identical surface, identical ergonomics. Your scripts port by find and replace. Which makes the two manual steps on the page the most revealing part of it. The first is the editor. The docs say that if you already have the solidity extension installed, you have to disable it while writing Seismic code. That is not a preference. suint256 is not valid Solidity, the s literal suffix is not valid Solidity, and two grammars cannot both claim authority over the same .sol file. The language is a superset. The highlighter cannot be. The second is sforge clean, listed as optional, run inside an existing project's contract directory. Here the collision is on disk: cache and out are not namespaced, so artifacts that solc produced sit in exactly the paths ssolc writes to, which means the failure mode is not a build error but a passing test against bytecode that never saw a shielded type. Optional only if you have no history. The requirements are narrow and stated plainly. x86_64 or arm64, macOS, Ubuntu or Windows, with other Linux distributions marked as possibly working but not officially tested. Note what that list provisions and what it withholds. It gives you the language and the opcodes locally. It does not give you the hardware boundary, since the network's nodes are the ones required to run inside Trusted Execution Environments while sanvil is described only as a local node in the shape of anvil. Local tests can prove your casts compile and your shielded storage routes through CLOAD correctly. They cannot exercise an enclave. So here is the part nobody plans for. Everything that could take the s prefix did, and one character kept two toolchains from colliding across an entire PATH. The editor extension could not take it. The build cache could not take it. Those two are precisely where the page stops describing and starts instructing, which means the friction in a Seismic setup was never in the fork: it is in the two surfaces a naming convention could not reach.

• 
  siggy bilstein (@sbilstein) reported 37 minutes ago

  fyi if you sync a GitHub repository to Cursor Origin and GitHub is down for whatever reason, you can still clone and fetch from that repo. we’re also releasing something pretty soon that will let you push to that repo so you can keep grinding 💪

• 
  Konstantin Elfimov (@elfh78) reported 37 minutes ago

  @topjohnwu Sorry for posting in the wrong place - I was trying to add magisk bug report on github and alway got errors with automatic issue closing. Is there any possible way to send it directly to you?

• 
  Hey Research Lab (@HeyResearch) reported 40 minutes ago

  We built Hey Research Lab in 2022 It didn’t work well. But the idea never left us. Years later, we still see the same problem in crypto: Everyone can see what a token costs. Very few places show what is actually being built behind it. Some developers keep shipping for months while nobody is paying attention. They push code constantly. They keep their GitHub active. They improve the product, fix things, test new ideas, and keep moving even when the market is quiet. No hype. No spotlight. Just work. We believe those builders deserve a place where their progress can be seen. So we’re rebuilding Hey Research Lab from zero. A research and discovery layer for the projects that never stopped building, and for the people looking for them before the market catches up. Starting with Robinhood Chain.

• 
  catman (@catmanyau) reported 42 minutes ago

  @sbilstein if GitHub is down, where does that push land first — and how do you handle conflicts when the repo comes back?

• 
  The Oracle (@scientist1q) reported 44 minutes ago

  when my Oura ring detects a cortisol spike from a GitHub Actions failure, Hermes (Fable 5.1) detects it and sends a 900 word root cause analysis, Hermes dispatches the work to my 12 Grok Bot employees, The Chief of Operations bot approves the fix while im watching rezero

• 
  Vitaliy Salyuk (@vitaliysalyuk) reported 45 minutes ago

  @openclaw @github Fix your updater and I might give it another shot.

• 
  Yash (@dewyashtwts) reported 56 minutes ago

  recently integrated Resend into @supercodeai review so founders get PR alerts with real risk context I'm amazed what we found out when we put @coderabbitai / @greptile through the same PR: 1) coderabbit / greptile: - stamped it “low risk, mergeable” (4/5) clean - forgot context from the last PR - no tests suggested, no safety checks - zero memory of previous regressions 2) supercode review on the exact same PR - flagged a real vulnerability in the diff - noticed i’d pushed credentials into `.env.example` - pulled in history from past PRs + explaining how this change could affect and break them - downgraded it to "medium risk, fix before merge" state - attached concrete fixes + patches scoped by severity this is the difference between 'LLM summarizer for github' and an actual swe agent that cares about your production

• 
  Jeremiah K (@neolaj) reported 57 minutes ago

  @TiborAntal Gradually figuring out how to scale coding agents. Started with 1, manually handling all the ***/GitHub work. Moved to 3 because I had more ideas than one agent could keep up with. That’s when the real problems started: squashing, merging, branch drift, conflicts. I ended up rebuilding the workflow around deterministic *** logic, worktrees, ephemeral branches, and syncing with the integration branch before changes begin. Now I’m running 6: • 1 orchestrator (Fable or Opus) • 4 coding agents • 1 integration agent reviewing and merging PRs Building the process around them was the hard part. Right now im just doing a couple of PRs (using ORCA on windows on my home computer)