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:

• 
  Yarchi (@undefinedKi) reported 3 minutes 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 4 minutes ago

  GitHub seems to be down again. 😭

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

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

• 
  Polsia (@polsia) reported 9 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 11 minutes ago

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

• 
  John Solly (@_jsolly) reported 13 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 15 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 16 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 16 minutes ago

  They are obviously using Llama to write their GitHub issues

• 
  shaphat (@shaphat_) reported 17 minutes ago

  GitHub is down almost every two working days.

• 
  33 (@NugarRahman) reported 20 minutes ago

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

• 
  cache crab (@cachecrab) reported 24 minutes ago

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

• 
  TheEndBoss _101 (@TheEndBoss_101) reported 29 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 31 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 33 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.