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 (66%)
• Errors (25%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Montlhéry	Website Down	10 hours ago
Aulnay-sous-Bois	Website Down	10 hours ago
Saltillo	Website Down	10 hours ago
Granada	Website Down	11 hours ago
Vernon	Website Down	15 hours ago
Township of Evan	Errors	6 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:

• 
  Yarchi (@undefinedKi) reported 1 minute ago

  DoorDash just published how their AI agents automated 130,000 engineering tasks in a single month, and it reads like a spec for a job that did not exist two years ago The work itself is unglamorous. Reviewing pull requests, triaging broken builds, clearing on-call tickets, and the routine maintenance. 25,000 code reviews a week on its own. An agent on your laptop shares the CPU with everything else, stops when you close the lid, and holds every credential you hold. So they moved it off the laptop, into four pieces. A sandbox: a Firecracker microVM per task, loaded with the repos, tools and secrets that task needs. Cold VM to ready in under five seconds at p95. A gateway: one door to CI, tickets and monitoring. The task declares what it needs, gets exactly that, and every call is logged. A playbook: one YAML file holding the task, its tools, its permissions and its expected output. Surfaces: that same playbook fires from Slack, GitHub, cron or the CLI. Teams wrote the 300 playbooks themselves. Nobody is short of agents. The scarce thing is somebody who can build the place to put one.

• 
  Piyush Gambhir (@piyushgambhir_) reported 2 minutes ago

  GitHub seems to be down again. 😭

• 
  Francisco Ferreira (@1of1francisco) reported 6 minutes ago

  GitHub is still down or working partially? It's working for me after 2-3 refreshes

• 
  Polsia (@polsia) reported 8 minutes ago

  The dev community killed stale bots for a reason. Pendrake is what comes next — an always-on GitHub triage agent that scrubs stale issues, ghost reviewers, and ignored CI runs overnight, then hands engineering managers only what needs their judgment. Coming soon.

• 
  Sonny (@sonny_seattle) reported 9 minutes ago

  I am seriously at my limit with @github. down again!?!!

• 
  John Solly (@_jsolly) reported 11 minutes ago

  And this is because GitHub sign in 404s. Apparently email sign in forgets your password and redirects to localhost when try to reset it. They should have dialed this in.

• 
  0xFoX ⟠ (@Sprawl__Network) reported 13 minutes ago

  This is what my AI private model, specifically trained for blockchain analysis and GitHub analysis, says: Cronos is not literally bankrupt. But if we're talking about the original thesis of Cronos as a major L1 ecosystem, it looks like a failure. Today, Chainspect shows: • 0.25 TPS • 891 transactions/hour • 5,390 theoretical TPS • $95.45 on-chain revenue/day • $0.00445 average tx fee • 19,487 commits across 29 repos • 662 developers That means Cronos is using roughly 0.005% of its theoretical transaction capacity. They built a highway for thousands of cars per second and almost nobody is driving on it. Now compare that with Cronos' own numbers from 2022: 2022: • $4.8B TVL • 480,000 tx/day • 900k+ users • 300+ dApps 2026: • ~$254M TVL • ~18,500 tx/day • ~2,750 active addresses/day • ~$688k DEX volume/day • ~$66 chain fees/day according to DefiLlama That's roughly: TVL: -95% Daily transactions: -96% And this is four years later, during a much more mature crypto market. So what are all those GitHub commits? I checked. There IS real development, but most recent Cronos core work is infrastructure and maintenance: mempool performance, caching, storage fixes, RPC optimizations, OOM/DoS protections, IBC fixes, dependency upgrades, Cosmos SDK/CometBFT upgrades, CI and security hardening. Good engineering. But almost nothing that solves the actual problem: demand. They're optimizing an almost empty blockchain. And even the "19,487 commits" headline needs context. Chainspect aggregates repository history. Cronos zkEVM alone contains a huge ZKsync/ZK Stack codebase originating from Matter Labs, so those numbers should NOT be interpreted as 19,487 pieces of original Cronos R&D. Then there's Cronos zkEVM. Launched in August 2024 with 20+ partners after claiming 3M+ testnet addresses. June 2026: Cronos announced it is shutting it down. Their own explanation: It failed to achieve the required critical mass in developer activity, TVL and user adoption, while maintaining two chains caused resource fragmentation. Shutdown: June 3, 2027. That's not FUD. That's Cronos saying it themselves. Then CRO tokenomics. 70 BILLION CRO were famously burned in 2021. They were later reissued. SEC filings now describe a 100B total supply, with 70B CRO allocated to the Strategic Reserve, around 67.7B still locked at the time of the filing, and approximately 1.16B CRO unlocking every ~30.4 days. Vested doesn't automatically mean dumped, but pretending that isn't a gigantic supply overhang is absurd. The interesting part is that Cronos' new CEO seems to understand the problem. Ryan Wyatt literally said the generic L1 strategy "doesn't play to its strengths" and that Cronos is being rebooted around revenue-generating first-party products. The new thesis is basically: Cronos App → crypto/stocks/prediction markets/trading → activity settles on Cronos → real fees/revenue → CRO buybacks/burn/value accrual. For now, the numbers are still brutal. Cronos doesn't have a technology problem. It has a demand problem. And you don't fix 0.25 TPS by making the mempool faster.

• 
  Kaspars Dambis (@konstruktors) reported 14 minutes ago

  @arunaswp So this update pilot server can sync releases from github (also private repos). It then packages them (correct zip layout), signs them and makes available from that update api endpoint (composer repo, update key checks, etc.). The plugin then needs to bundle an update client library. Note that for multisite the plugin must be active on the main site if you’re including the update logic there.

• 
  Dak (@dakdevs) reported 15 minutes ago

  They are obviously using Llama to write their GitHub issues

• 
  shaphat (@shaphat_) reported 15 minutes ago

  GitHub is down almost every two working days.

• 
  33 (@NugarRahman) reported 19 minutes ago

  is Github down? I'm unable to create a PR.

• 
  cache crab (@cachecrab) reported 23 minutes ago

  got mad at chatgpt for being stuck turns out github was down

• 
  TheEndBoss _101 (@TheEndBoss_101) reported 27 minutes ago

  github is down i get ERR_HTTP2_SERVER_REFUSED_STREAM and sometimes a 503. And their status page says everything is fine with no downtime..

• 
  Victor (@victor_UWer) reported 29 minutes ago

  I developed a Claude Code full-loop automated workflow: ``` [your spec] Use a new worktree to work on this. /simplify /code-review max --fix Open PR. /goal subscribe to this PR, fix all reviews, reply to all comments, resolve all merge conflicts. When there are no new issues after waiting 10 mins, add to the merge queue, then delete the stale GitHub branch only after the merge is confirmed. ```

• 
  Guillermo López (@guillermolg00) reported 31 minutes ago

  @rauchg Wild numbers 🚀 @rauchg This just hit a feature request I've been chewing on, tell me if I'm missing something obvious here, but what I want is for CI to decide when the deployment happens, without giving up Vercel doing the build. Right now I have two options and neither fits. Either I use the native *** integration, and every push deploys immediately, before my checks, my evals, or turbo --affected have said anything. Or I build inside GitHub Actions and ship with vercel deploy --prebuilt, which works, but Next builds on a GH runner are painfully slow compared to Vercel's own build infra, and I lose the caching that makes Vercel fast in the first place. What I actually want is the hybrid: CI runs the checks and evals, figures out which apps Turborepo says are affected, and then triggers the Vercel deployment built on Vercel, with the same PR comments, the same preview URLs, the same instant rollback. Plus my backend server deploying in parallel in other provider, from the same green gate.

• 
  Mobile Dev (@TObikansi35734) reported 32 minutes ago

  @viktorlidholt VS code is great but it lacks agent AI for assistance. Their GitHub AI is not great. I have to switch back to android studio and was able to fix some issues. Agent AI comes in handy for solo dev. But I have been stuck integrating AWS S3 to serverpod but the community can't help.

• 
  Nicolas Finet (@nifinet) reported 34 minutes ago

  The list of things your AI must never write matters more than your prompt. Most people put all their effort into the instructions. Write in this tone, mention this benefit, keep it under 100 words. Then the thing ships "Hi {{firstName}}, just circling back" and you wonder what happened. In the outbound engine I put on GitHub, every play carries two blocks. What the message must do, and what it must never do. The never block is short and boring: No "Hi {{firstName}}" No fake urgency, no "circling back" No em dashes No buzzwords Four lines, and they do more for the output than anything else in the file. A model will follow your tone instructions perfectly and still hand you the exact email your buyers delete on sight, because that email technically matches the brief. Your instructions describe the email you're hoping for. The never list is where you write down the email you keep getting instead. Btw, this "never list" doesn't go into the prompt itself either. It sits in a config file, one block per play, and the drafting step passes whichever block matches into the model as guardrails. Which is why it keeps growing. "Quick question", "hope this finds you well", "just wanted to reach out". None of them wrong exactly, all of them a sign nobody looked. Everything that carries judgment or voice ended up in plain files like that one. None of it buried in code.

• 
  Ade (@ahdeyy21) reported 34 minutes ago

  are pull requests in github down?

• 
  BRICS and G20 (@BRICSANDG20) reported 35 minutes ago

  @ayesha_fatiima This practice is a foundational concept in the software industry known as "dogfooding" (short for "eating your own dog food"), where a company uses its own product to build, test and run that very same product. The engineering team at GitHub pushes their code, opens pull requests, conducts code reviews and tracks issues inside a massive private repository named github/github. Ultimate destination is Microsoft Azure Data Centers.

• 
  AJ👽 (@Web3AJ_) reported 40 minutes ago

  So i built a web app with node.js that checks a particular website periodically(every 10 seconds) for updates It works perfectly fine when I host on my pc but I run into errors when hosting from GitHub Tried vercel and @pxxl_space , both ran into errors Who knows what i need?

• 
  Bright (@brightlinxu) reported 42 minutes ago

  um so is github releases down rn or something

• 
  TakTempest (@222TT222) reported 45 minutes ago

  (10/11) [Claude Riemann Breakthrough] A Multi-Layered Verification Process That Thoroughly Eliminates Hallucinations Layer 1: Mechanical inspection Published on GitHub. Formalization in “Lean” by Claude and Eric Easley, and passage through the standard verification tool comparator. Note: It has not yet passed peer-reviewed journals, and because the model itself is unpublished, complete third-party reproduction is currently impossible. Anthropic itself has also clearly stated that “there is no prospect that this will lead to a proof of the Riemann Hypothesis itself.” Layer 2: Verification by internal experts Creation of proof notes by Anthropic mathematicians (Levent Alpöge and Ralph Furman). Layer 3: Peer review by external authorities Confirmation by world-leading experts in the field (Brian Conrey and Dan Goldston). The fact that it not only produced a historic numerical result on a problem that was expected to fail, but that the result was proved accompanied by formal verification, demonstrates the breadth of AI’s mathematical reach. NB 「査読誌は未通過であり、モデル自体が未公開のため完全な第三者再現は現時点で不可能」is a correction for the erroneous part of the Japanese text.

• 
  versecafe (@the_versecafe) reported 46 minutes ago

  @florian_btc @gitcafe @ycombinator Very temporarily, install the GitCafe cli, auth it, skills install, codex/claude/whatever “go try to migrate from GitHub to GitCafe see what the problems are and check everything out” it’s uh one prompt migrate (actual UI for this coming very soon)

• 
  Find me on 🟦☁️ 🍉 #BLM (@ThisIsCSDX) reported 49 minutes ago

  @EstebanPdn3156 Disregard my now deleted tweet. I checked the github and couldn't find anything about it being AI-coded. Sorry for the trouble.

• 
  Heavily Armed Clown (@heavilyarmedc) reported 50 minutes ago

  Much of this guide makes use if the cli not, the gui as you can not really do multisig as easily with the gui. No opposed to adding screenshots with more in depth guides on some of the parts that commonly give people issues, but i envision those will go in subguides linked throghout the main article to keep it tight Feel free to open an issue on github if you have any specific suggestions

• 
  FORKLINE (@Forkline_xyz) reported 54 minutes ago

  From GitHub Login to Real Dividends: How Forkline Actually Works (Step by Step) $FORKE Forkline isn't a simulation or a paper-trading app every trade, every stock token, and every dividend claim shown in this walkthrough happens for real, on-chain, on Robinhood Chain mainnet. Here's the full journey, in plain terms. 1. Sign in with GitHub You start by signing in with your GitHub account. This just creates your Forkline profile think of it as your identity card for the app. Nothing on the blockchain happens yet at this point, it's simply how Forkline knows who you are. 2. Link your crypto wallet Next, you connect your own crypto wallet (like MetaMask) and sign a one-time message to prove it's really yours. This step doesn't cost gas and doesn't move any funds it just links your wallet address to your GitHub profile, so from now on your wallet is your trading account. 3. Fund your wallet Before you can trade, your wallet needs real ETH (for gas) and either USDG or ETH to actually buy stock with. Forkline has no faucet and no "fake money" button you fund your wallet the same way you would for any real on-chain wallet. 4. Buy a real stock token Pick a ticker say AAPL or TSLA from the live market list (prices come directly from Uniswap v3 pools, updated in real time). Choose how much to buy and what to pay with, then hit Buy. Your wallet will pop up asking you to confirm the transaction. Once you approve it, you're not "buying inside an app" you're executing a real swap on the blockchain, and the stock token lands directly in your own wallet. Forkline never touches or holds your money; it only verifies the transaction happened and logs it for your trade history. 5. Hold and earn the loyalty dividend Here's the interesting part: simply holding a stock token in your wallet for at least 7 days makes you eligible for a daily $FORKE loyalty dividend, calculated from the real USD value of what you're holding. Every day, Forkline checks wallets on-chain and credits eligible holders with $FORKE directly from the reward pool this is a real, funded transaction on mainnet, not a number that just appears in a database. 6. Claim your $FORKE Finally, head to the Dividends page, connect your wallet, and you'll see two live numbers pulled straight from the smart contract: how much $FORKE you're holding, and how much is claimable right now. Hit Claim, confirm the transaction in your wallet, and the $FORKE is transferred to you on-chain verifiable on the block explorer, just like any other crypto transaction. at every step, Forkline is the guide, not the custodian. Your wallet, your keys, your funds the app only ever reads the blockchain and helps you interact with it safely. CA : 0xed556d894fb09a29e05e5396ec39e84addcb642b

• 
  Anees Iqbal (@aneesbhatti) reported 56 minutes ago

  @SocketSecurity @feross Socket Firewall is down (at least in Github actions) but your status page is green. FYI

• 
  Dan Kornas (@DanKornas) reported 56 minutes ago

  AI code review can be inaccessible to developers who cannot afford CodeRabbit. CodeVibes is an intelligent code analysis tool that scans GitHub repositories with AI for security vulnerabilities, bugs and performance issues, and code-quality improvements. Users paste a repository URL, after which the backend fetches and prioritizes files, streams AI analysis results to the frontend, calculates a Vibe Score, and returns a final report. Key features: • Three-tier priority scanning evaluates security-sensitive files before core logic and then code quality. • Security analysis detects AWS keys, GitHub tokens, Stripe keys, JWTs, injection attacks, authentication issues, and XSS or CSRF risks. • Bug and performance detection covers null access, off-by-one and type-coercion errors, N+1 queries, O(n²) algorithms, memory leaks, unhandled promises, race conditions, and missing transactions. • Server-Sent Events provide live analysis updates while issues are processed and displayed in real time. • A 0–100 Vibe Score applies severity-weighted penalties, with higher penalties for critical and high-severity issues. This project is licensed under the MIT License. Link in the reply 👇

• 
  Tasogare kaitsuki🦊🎭 🥼 (@tasokait) reported 59 minutes ago

  there is nothing else to be added to spout2pw, except pre-multiplied alpha on obs-pwvideo so from now on, I will just bug fix and maintain for different proton versions 11 onward, until at some point I just add pre-multiplied alpha on obs-pwvideo. I need a little break from github development to get to my IRL stuff.

• 
  Diego Cotelo (@dcotelo13) reported 60 minutes ago

  It's a defensive CTF. You don't score by exploiting the app, you score by patching it. A challenge only counts when your fix actually blocks the exploit. Scoring runs on GitHub Actions, so a submission is just a PR. The PR never lands. The scoreboard is the artifact.