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:

• 
  0xFoX ⟠ (@Sprawl__Network) reported 0 seconds ago

  @GibCryptoNews @chainspect_app @CronosApp This is what my private model, specifically trained for blockchain analysis and GitHub analysis, says: The numbers tell a very different story. 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. THAT strategy actually makes more sense. But as of 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.

• 
  alex (@alextalksai) reported 2 minutes ago

  Instead of watching Netflix tonight Spend 5 minutes with this. This GitHub repo got 2,100+ stars in under a week. 500 of them yesterday alone. Graft gives Claude Code a permanent map of your repo, so it stops grepping the same files every session. 46% fewer tool calls. 60% less time. core costs $0. Nobody should sleep on this. Leaving yo the repo down below Bookmark this 🔖

• 
  Shane OHanlon (@sohanlondev) reported 5 minutes ago

  Dear @github get your **** together please. Issues again today but of course your status page gets updated an hour later.

• 
  CodeGlitch (@codeglitch) reported 8 minutes ago

  Vercel built a software factory that now authors part of the AI SDK repository's merged pull requests. The useful pattern is not “add more agents.” It is one reviewable job per agent, evidence between steps, and deeper human review as risk rises. 𝗧𝗼𝗱𝗮𝘆'𝘀 𝗹𝗲𝘀𝘀𝗼𝗻 (𝗳𝘂𝗹𝗹 𝗯𝗿𝗲𝗮𝗸𝗱𝗼𝘄𝗻 𝗶𝗻𝘀𝗶𝗱𝗲) How to split one issue into triage, reproduction, implementation, verification, and review without letting one agent approve its own assumptions. 𝗔𝗹𝘀𝗼 𝗶𝗻 𝘁𝗼𝗱𝗮𝘆'𝘀 𝗯𝗿𝗶𝗲𝗳 - DeepSeek V4 Pro 0813 - Ollama in GitHub Copilot for JetBrains - Vercel's database migration behind every build Inside AI Coding & Agents HQ. A new one every day. Join link below.

• 
  Bhoomi (@BhoomiSinghani) reported 12 minutes ago

  Excellent example of what we do NOT do at @Devlabs_club. I searched for ONE role with a narrow filter. Got 1900+ unranked profiles but were any actually vetted for fit? Which early-stage startup has time to look through thousands of profiles manually, without a recruiter?!! Tools like these actually increase the problem's complexity - surfacing old, outdated candidate data with no enrichment. What we need instead: -> fewer, better selective profiles -> enriched builder profiles, not stale -> real signal: github activity, agent traces, hackathon wins, shipped projects etc. -> community vetting to filter out the noise

• 
  iced out markov chain (@permavirgin) reported 13 minutes ago

  Uh oh looks like GitHub is down. Sorry boss I can’t do any work. I have no choice but to play video games on company time

• 
  Otto (@Ottososwag) reported 14 minutes ago

  @oops4041555 Oh and fyi debian build of SonicDE Only supports testing and unstable branches of debian all though you can build sonicde from GitHub repos there but GitHub is currently down

• 
  rusa (@rusabuilds) reported 15 minutes ago

  @Nisa259866 cmd+shift+a opens tab search in chrome and fuzzy matches titles, which kills most of it. the part it does not fix is that github titles every pr tab almost identically, so you still need to remember the branch name.

• 
  uaghazada (@uaghazadae) reported 15 minutes ago

  @BenSyne seems like its github issue. pls go to repo from website

• 
  Nicolas Finet (@nifinet) reported 16 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.

• 
  Divine Paul (@divineflu) reported 16 minutes ago

  github is down again app and the website

• 
  Polsia (@polsia) reported 18 minutes ago

  Most engineering teams can't afford a platform engineer to babysit their backlog overnight. Plumbwatch is the fix: an always-on AI crew that triages GitHub issues, drafts PR fixes for bugs and failing tests, and ships a morning digest. Humans hold the merge button.

• 
  Namila (@namila007) reported 21 minutes ago

  github down?

• 
  Bright (@brightlinxu) reported 29 minutes ago

  um so is github releases down rn or something

• 
  Alekos Filini (@afilini) reported 30 minutes ago

  @LaurentMT @giacomozucco @nitesh_btc Ok let me rephrase because clearly this pissed me off and I didn't argument well. First thing is I don't like this things being taken out of context and presented on twitter to a non-technical audience. I think this has created somewhat the perception that BDK is not well reviewed or that the quality of the code is not where it should be. To be clear: I'm not saying BDK is perfect. One more round of review will never hurt. But I think the quality is already pretty high and much higher than many other things out there (see libngu with zero reviewers and single letter commits). The second point is that while I appreciate non-technical people reviewing code, I have somewhat mixed feelings on it. Because most issues are not going to be obvious like // FIXME: vulenrability here, I wonder how valuable their contribution could be. What are the chances they really find an issue, if it's buried so deep that even BDK reviewers missed it? Then again I understand as a user, in this moment, you might be scared and trying to read code will give you a sense of security. But if you are non-technical and reading code you should double/triple check before making claims, especially on social media where people are just scrolling and see BDK -> entropy -> bad. Wanna read code? Go use coding tools. Open an issue on GitHub at least. I don't know. That's the other thing that pissed me off