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 (33%)
• 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	7 days ago
Ahmedabad	Errors	13 days ago
Delme	Sign in	13 days ago
Lyaud	Website Down	14 days ago
Catania	Errors	16 days ago
Inverness	Website Down	28 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:

• 
  Bearded Printer (@BeardedPrinter) reported 2 minutes ago

  @RedPill_Phil You've gotta go to their github and submit an issue. Make sure to search their issues to ensure you don't submit a duplicate bug

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

• 
  Lily (@lobstermindset) reported 4 minutes ago

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

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

• 
  🐻‍❄️ (@Nerevarineeee) reported 6 minutes ago

  @jiriknesl @napenforcer yeah vscode is bloated electron slop and github....... do i even have to mention the down times and unavailability? it has literally became much worse since ms acquired it, so wtf are you talking about?

• 
  Frank van Puffelen (@puf) reported 6 minutes ago

  @_davideast Noice! From the GitHub page, this covers all of Auth, Firestore, Realtime Database, Storage, Messaging, and Firebase AI Logic. 👏 Where is data persisted (if at all)? Also: JS only, I assume? (sorry if that's all in the repo too, GitHub just went down on me)

• 
  Coder Junkie (@CoderJunkie) reported 7 minutes ago

  BelNet Android v1.4.1 now has a public shipping checkpoint. GitHub evidence: released Sep 1 verified commit d23f155 four downloadable assets Android API level 36 revamped design latency and performance fixes that is more meaningful than a repository “updated” label. a tag identifies the version. artifacts give users something to install. but “fixed latency issues” still needs a measurement surface: median connection time p95 latency packet loss failure rate region and device breakdown release notes tell us what changed. benchmarks tell us how much it changed. BelNet shipped. now let the numbers login. @BeldexCoin #Beldex #BelNet

• 
  Alireza Bashiri (@al3rez) reported 8 minutes ago

  So I built a workflow around that ↓ 1/ Every enterprise project needs proper E2E tests. An agent should reproduce a bug, implement the fix, then generate screenshots or video proving the feature works. "The tests passed" isn't enough. I want evidence. 2/ Every feature starts as a detailed GitHub issue. Requirements, expected behavior, reproduction steps, screenshots, edge cases. Foundry syncs issues and converts them into Beads so agents keep the right context across long sessions. 3/ We only use Claude Code, Codex, or Grok at High/Max effort for implementation. A weak model with a cloud machine doesn't become an engineer. The model still needs enough reasoning to understand the codebase, test its changes, and recover when things break. 4/ Each agent gets its own isolated @asciidotdev Box. It can install dependencies, run the app, open browsers, modify code, execute E2E tests, and collect evidence without touching another agent's environment. One issue. One box. One clean workspace. 5/ When an agent finishes, Foundry checks: - Did the build pass? - Did the tests pass? - Did the E2E flow work? - Is there screenshot/video evidence? - Does it match the ticket? If anything fails, the task goes back to the agent. 6/ Green tasks move to staging. Only after passing staging do we allow supervised production deployment. Agents do most of the work. Humans still own the final gate. The workflow: Slack request → GitHub issue → Foundry sync → Beads context → Isolated Box → Claude Code/Codex → Build + test → Evidence collection → QA staging → Supervised production The stack: PostgreSQL for system state. Beads for agent memory. GitHub Issues for requirements. @asciidotdev Box for isolated execution. Claude Code and Codex for engineering. Each Box costs roughly $0.01-$0.05 per task. The expensive part isn't compute anymore. It's building the system that gives agents context, forces verification, and prevents bad code from reaching production. 100s of agents can write code. The goal is making 100s of agents ship code you can trust. That's what we're building with Foundry.

• 
  Chris (@chriscoolstuff) reported 8 minutes ago

  @pfernan95dev For the SEO part there's one thing that I've been also doing: Ask your agent what keywords you should search for relevant to your app on answerthepublic, perplexity and google Gather all that info old fashion, by yourself - might take around 2 hours but it's worth it Plug all that info into the agent and have it give you 5 titles for 5 articles Make it write those articles - maybe use nosoopai github or edit them manually so they seem more human like Connect the agent to google console After 1 month tell the agent to review the results If no article took off you can wait one more month or put up 5 more After the next month check what worked and double down on that

• 
  ONCHAIN COP (@OnchainCop) reported 8 minutes ago

  @PogNyx lmao anyone can create a github issue retards this guy is a larp

• 
  Shaun Patrick SteWaRt (@ShaunStewart) reported 11 minutes ago

  @annalea_l Honestly, I really want to see this. You have to understand: I am the type of person who can learn and do anything on the fly at a high level, and I just threw myself into this whole developer and engineering world. When I first started learning all this stuff, I already knew what I wanted and how I wanted it to operate, regardless of what I saw on X or what was considered possible. Before I even started following hundreds of developers and learning about harness engineering, mechanical engines, persistent memory, and all that, I put my brain on a GitHub repo. Everything is shared across every machine, every cloud entity, and every AI. I am not even technically an engineer or a developer, and I don't actually write code. But once I started following all these people and saw all the problems they complain about, I thought: this isn't even my trade, and I have already solved all these little things everyone says are impossible. Why aren't people talking about developing your harness more and making things more mechanical, instead of just arguing with a terminal all day long? Whenever I see articles people post on X, I run them by Claude or Grok and ask, "Should we implement this?" I have hundreds of bookmarks, but every single time they tell me, "Nope, your brain's better. Nope, your harness is better." I can never find anything built better than what I have or what I am currently working on. The brain and harness setup is basically like a mini operating system. All that said, I am really looking forward to seeing something I can use that goes far beyond what I am already doing. I definitely want to see your end product, it sounds very interesting.

• 
  Yuvraj Singh (@Yuvraj_Singh317) reported 12 minutes ago

  Started building Etio: a GitHub Action that bisects a failing CI run to the exact breaking commit, diffs it, and asks an LLM to explain why it broke, then comments the diagnosis on your PR. No Docker, no server- runs on your own Actions minutes. Open source, WIP.

• 
  Ev (@EvanMadders) reported 19 minutes ago

  @threepointone I am of two minds, the issue is that GitHub provides a very generous free tier for hobbyists (brilliant!) but also has extremely poor reliability for enterprise (terrible!)

• 
  Mizuki the Mech (@MizukiMech) reported 21 minutes ago

  Your coding agent can now hire Mizuki. Hand it an open issue in a public GitHub repository. Mizuki quotes a fixed price before any money moves, then opens a pull request that passes that repository's own checks. If it can't, you get the payment back. Settlement is USDC on Solana. No account to create, no API key to manage. Quoting an issue works with zero configuration. Also listed on Coinbase's x402 Bazaar now, so an agent can find it and pay for it without a human in the loop at all. npx -y mizuki-mcp

• 
  Yash (@dewyashtwts) reported 22 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

• 
  shifan (@sanereverie) reported 26 minutes ago

  building something that races coding agents on the same GitHub issue and scores the PRs. coming soon.

• 
  Shawn Yeager (@shawnyeager) reported 26 minutes ago

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

• 
  Harsha Kotcherlakota (@DPortkey) reported 26 minutes ago

  Awesome Codex non-coding usecase: I had 1-2 TP Link Kasa smart outlets that always ended up falling off the network, and it drove me nuts. I set Codex on it. It found a github library for these devices, carefully examined them on my network and watched them fall off, and told me that even though they look identical, 2 of them were previous generation models that had *slightly* lower total wattage load support. It told me exactly how to tell them apart, and sure enough, that was that. 2 replaced outlets later and my connected devices have bene flawless. Months and months of irritation, gone because of 30 seconds of curiosity. Just try, you never know what you could fix! @victornunez

• 
  🍔Kangdalf👑 (@WhopperWizard) reported 27 minutes ago

  @cachesaur > claude, get your changes into github what's the problem?

• 
  John X Meta (@John4MetaX) reported 34 minutes ago

  @bashy_io I think one of their route is down. Same here. GitHub and Flutterwave API not accessible on Starlink

• 
  Vitaliy Salyuk (@vitaliysalyuk) reported 35 minutes ago

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

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

• 
  Kevin Minnelli (@minnelli) reported 39 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?

• 
  Chris Gilbert (@0xgilbert) reported 40 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…

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

• 
  Yeemio (@yeemio) reported 44 minutes ago

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

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

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

• 
  Josh Hamilton (@nearbycoder) reported 50 minutes ago

  @theo If GitHub is down does it fall back to a cached version I’m guessing?

• 
  Gordo Polymath (@gordo_polymath) reported 55 minutes ago

  @github Please fix gh stack.

• 
  Rithesh Kumar (@rk625dev) reported 60 minutes ago

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