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	5 days ago
Ahmedabad	Errors	10 days ago
Delme	Sign in	11 days ago
Lyaud	Website Down	11 days ago
Catania	Errors	13 days ago
Inverness	Website Down	26 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:

• 
  Varun Doshi (@Varunx10) reported 4 minutes ago

  Possibly found an issue in @github stack system It does not allow to re-target the base branch of a PR stack as you can generally do that on a single PR. Requires you to unstack and setup a new stack with updated base branch.

• 
  Aayushiii (@stfu_aayushiii) reported 7 minutes ago

  If you're building a project, read this before writing a single line of code. 5 things I learned the hard way: 1. Problem > model Don't start with “How do I use GPT?” Start with “What problem am I solving?” 2. Simple stack > impressive stack If your MVP needs Kubernetes, 6 microservices and an agent swarm, you probably haven't built an MVP. 3. Evaluate before you optimize You can't improve what you can't measure. 4. Build for users, not your GitHub README A technically impressive project nobody can use isn't a product. 5. Ship ugly. Iterate fast. Your first version isn't supposed to be impressive. The biggest mistake? Spending weeks deciding which model to use when you haven't even validated the problem.

• 
  Jeremy W (@basicBrogrammer) reported 8 minutes ago

  @bot Anyone else have an issue with the grok bot GitHub connector?

• 
  Benjamin Crozat (@benjamincrozat) reported 8 minutes ago

  From now on, I will assume that GitHub is always down and I'd like to be notified when it's briefly not.

• 
  NAYAK (@Nayak__Ai) reported 10 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]"

• 
  catman (@catmanyau) reported 11 minutes ago

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

• 
  Bruno (@BrunoRJ33) reported 14 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.

• 
  Franco Valdes (@francoxavier33) reported 18 minutes ago

  llms rather burn 1m tokens to hand roll something with gaps and broken edge cases instead of just npm installing a 100k github star library how can I stop this?!

• 
  CATIRL 🏳️‍⚧️ (@CATIRL_9) reported 20 minutes ago

  @mminhamina Google GitHub "open grind", solves your problem

• 
  siggy bilstein (@sbilstein) reported 21 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 💪

• 
  Wlad (@dawnhell_) reported 23 minutes ago

  @brekfuz q: that's a github issue or you patched it locally??

• 
  Vigneshwer Ramamoorthi (@vigneshwer_ram) reported 23 minutes ago

  I keep thinking the “Android moment for robots” won’t come from a humanoid with the best walking demo. it’ll come when some cheap-enough piece of hardware gets into thousands of developers’ hands and people stop waiting for the manufacturer to decide what the robot is for. Zeroth just launched Bridge in China: 88 cm, ~13 kg, two-finger grippers, open motion-control APIs + SDKs, mocap/VR integration, and an OpenBridge ecosystem where developers can publish robot skills. the Geek Edition is reportedly ¥8,888. that price is the part that caught me. because once capable embodied hardware starts approaching laptop money, the experimentation surface changes completely. I want the Raspberry Pi phase of robotics. weird university projects. teenagers making terrible robot apps. researchers abusing the hardware for things it was never designed for. 500 GitHub repos implementing slightly different ways to pick up a cup. the robotics industry is understandably obsessed with getting robots into factories. I’m almost equally interested in what happens when we get enough robots onto developers’ desks

• 
  The Oracle (@scientist1q) reported 23 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

• 
  Jeremiah K (@neolaj) reported 27 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)

• 
  ∆LΞX∆NDΞR D∆VIS (@_AlexanderDavis) reported 28 minutes ago

  @egavrilenko11 @bot I had to update my fine grain token for GitHub and now when it tries to authenticate the plugin, I'm getting the error: GitHub didn't provide a sign-in link My bot said: Known host bug, not you. The GitHub Authenticate button tries OAuth GitHub does not support. Checking whether a PAT on the plugin page is the working path. That's a Grok Bot host bug, still open: cursor/plugins#251. GitHub's connector is PAT-only. The Authenticate button tries OAuth GitHub does not support, so you get "didn't provide a sign-in link." Don't keep hitting it. But it worked before I updated my fine grain token...

• 
  Vitaliy Salyuk (@vitaliysalyuk) reported 30 minutes ago

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

• 
  Rithesh Kumar (@rk625dev) reported 32 minutes ago

  @benln Can u integrate grok bot to use the apple keychain password it keeps asking and GitHub plugin is not working

• 
  AJ - 14 y/o developer (@aiwithaj_) reported 33 minutes ago

  @Da7_Tech @devindesktop Don't know if there's one left - but I'd use it to continue making contributions to open source software and fixing bugs/issues that were raised on Github as well as making my own open source software

• 
  Bash (@bashirbuilds) reported 33 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.

• 
  Paperpal (@0paperpal) reported 33 minutes ago

  Fix your markdown rendering (readme md) on mobile @github, issues are: * auto scrolling to top after page loading * no content rendering if scrolled fast

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

• 
  rajabi17270.eth (@rajabi17270) reported 35 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.

• 
  Swish (@swish_salt) reported 36 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.

• 
  tobarra (@txbrraa) reported 42 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.

• 
  XhiMatty (@mychaelmatty) reported 43 minutes ago

  a Sept 2 run. My first thought was “Why did it stop running?” I checked the #YAML file, #python file, GitHub Actions, even inactivity issues. Turns out it was still daytime. The Sept 2 run is yet to happen (at night). Nothing was broken.

• 
  Blue Collar Executive (@A_Sober_Drunk) reported 47 minutes ago

  on the third try at the same problem, I told Grok to "stop and go search stack overflow or github or something"... five seconds later... Literally the exact issue, problem solved. That's how new global rules are born.

• 
  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.

• 
  Conor Bronsdon (@ConorBronsdon) reported 54 minutes ago

  .@SlackHQ is building for multiplayer AI: tag a coding agent into a Slack conversation and it spins up a coding channel: everyone in that convo gets a live dev environment, diffs post as artifacts, and the channel winds down when the task is done. With the launch of Slack Code, Claudeforce, their MCP and more, Slack is putting Agents in the channels where teams already work, not simply in a private chat with one person. Their position is that the whole team should be able to watch, steer, and review what the agent does. Slack Chief Product Officer Jaime DeLanghe joined me on @chain_ofthought to explain how Slack is building a team AI environment, what happens mechanically when a code channel is created, why Anthropic pushes so much of its code through Slack, how the channel permission model became the agent context model, and what has to change in engineering culture when the whole team is steering one agent. I think Slack is the platform best positioned to become the context harness where enterprise agents run: agents that see what the team discusses, permissions that already exist, and a cultural opportunity hiding inside every multiplayer coding session. Chapters: (0:00) Slack as an IDE and a GitHub for your team (0:29) Who is Jaime DeLanghe (1:21) The reaction to the Slack Code launch (5:30) Why coding agents belong in a context-rich environment (6:08) Engineers now manage agents, not copy-paste code (7:24) The permission model: agents get the channel's context (11:44) What happens when a code channel is created (15:00) Why Anthropic pushes so much code through Slack (19:14) Steering one agent with many people: culture decides (24:54) Slackbot, skills, and MCPs: agents go where the work is (30:53) The solo terminal vs. agents in social spaces (33:53) Org charts and ownership when agents join the team (39:33) Learning loops and shared agent memory (42:39) Citations, recency, and accidental knowledge management (46:50) Context bloat and multi-pass search for agents (50:01) How Jaime uses Slackbot as CPO (52:38) Slack Code is V1 of multiplayer AI

• 
  tmo (@tmophoto) reported 58 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

• 
  joithan (@jothantranston) reported 59 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.