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:

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

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

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

• 
  Max Rovensky (@MaxRovensky) reported 3 minutes ago

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

• 
  Shawn Yeager (@shawnyeager) reported 7 minutes ago

  My @bot keeps reaching for the browser and `gh` instead of using the GitHub plugin. Known problem?

• 
  lifestep.io (@Dragon_limchae) reported 8 minutes ago

  @cursor_ai the sandbox boundary is where i lose the most time. today my workers had network blocked at the sandbox level and reported it as "github auth failed" — i chased credentials for an hour before checking dns. once agents run on your infra, make the boundary throw one unmistakable error instead of one each tool invents.

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

• 
  Kevin Minnelli (@minnelli) reported 9 minutes ago

  WTF - Grok Bot can't fire on schedule to save it's life. The scheduled routines are just broken and at best unreliable. I want to love this product. When you set the cron job it doesn't work. It tells you try Cloudflare, sure let's set that up and burn tokens, then that doesn't fire to wake them. Oh, let's try GitHub now and use that....all failed. I had to wake it again this morning before the market opened. Anyone else feeling frustration in this regard?

• 
  Vitaliy Salyuk (@vitaliysalyuk) reported 10 minutes ago

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

• 
  Suryansh Tiwari (@Suryanshti777) reported 12 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]"

• 
  Blue Collar Executive (@A_Sober_Drunk) reported 15 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.

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

• 
  John Crickett (@johncrickett) reported 22 minutes ago

  @Mike_Preston17 I don't think they water them down, why would they when they're competing on having AGI? I don't mind using GitHub actions to run tests and builds against a branch before merge. I don't want it triggering production schedules. Do you list all the things it shouldn't do in the prompt?

• 
  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

• 
  Fofer (@foferxxx) reported 23 minutes ago

  @AmigamagazineGA Has there been any public explanation as to why this GitHub repo was taken down? It’s been 404 for days. Is there a story there?

• 
  Farley (@FarleySchaefer) reported 24 minutes ago

  @github Hope this doesn't bring down GH