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

Live Outage Map

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

City	Problem Type	Report Time
Saltillo	Website Down	5 hours ago
Montlhéry	Website Down	23 hours ago
Aulnay-sous-Bois	Website Down	23 hours ago
Saltillo	Website Down	24 hours ago
Granada	Website Down	1 day ago
Vernon	Website Down	1 day 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:

• 
  Xeno1 (@Xeno6l1) reported 3 minutes ago

  GITHUB PAYS $978K/MO ON AGENT MINIMALISM. YURI LAUNCHED PONYTAIL MINIMALIST CODING ENGINE. MAKES $8,123K/MO Pause at 0:12 — neon illustration. Girl with glasses. Text: "Ponytail. He says nothing. He writes one line. It works." Logo like AI philosopher. This is minimalism. This is revolution. Yuri, 42, Ukraine. Was code-minimalist developer, $7,200/month. When he saw principle "one line = all solution", he knew: this is future of coding. Launched Ponytail Minimalist Coding Engine. How it works: PRINCIPLE 1: SIMPLICITY — ~54% less code (up to 94% savings) — Keeps maximum economy — Philosophy: less code = fewer bugs = more quality — Result: code that works first try PRINCIPLE 2: EFFICIENCY — ~20% cheaper (vs Claude Opus 4.8) — Fewer tokens = lower cost — One line of code instead of 10 — Result: 20% AI cost savings PRINCIPLE 3: SPEED — ~27% faster (vs traditional approach) — One line = quick generation — Fast processing = fast deploy — Result: 27% faster development cycle PRINCIPLE 4: SAFETY — 100% safe out of box — Every line has built-in security guards — Doesn't need additional checks — Result: no security issues PRINCIPLE 5: RELIABILITY — Built-in quality check — If something wrong = refuses to write — Runs tests automatically — Result: 100% code confidence STATISTICS: — 40k stars on GitHub — v4.7.0 — stable version — Works with 14 agents — ecosystem — MIT license — full freedom — Measured on real Claude Code sessions — 12 feature tasks (Haiku 4.5, n=4) — Reaches 94% where agent over-builds Users say: "Ponytail writes less but does more". Statistics: 94% cases where Ponytail generates code, it works 100% first try. 534 teams pay $19,456/month each. They say: "Like having philosopher-genius in your code. Writes minimum, result maximum". GitHub offered $94,100,000. Yuri said: "All agents write code. Ponytail writes one line. That line = entire code. This is philosophy of minimalism. This is future." Why — in video.

• 
  John Broadway (@JEBroadway) reported 3 minutes ago

  Look at where the real money in AI is going: infrastructure and hardware. Software is becoming cheap to generate. Hell, AI can even help layout silicon, but that code still has to execute on physical machines. That’s why NVIDIA and hardware vendors hold all the cards right now. The era of the "pure" syntax coder is ending. We don't need people typing out loops; we need hardware engineers and systems folks who understand physical compute and how big systems fit together. I’ve been in tech 36 years, from bench PC repairs to global rollouts and managing dev/hardware teams through every shift since the 90s. To me, AI hasn't made us all coders. It’s made us builders. I’m not a developer. I’ve looked at COBOL, Pascal, Python, C++, Rust, you name it. I see patterns and images, not syntax. When I use AI, I describe mechanical systems: "Picture plumbing in a ten-story building" to map how data moves between agents and apps. That's the difference: A coder connects one pipe. A builder knows what concrete goes into the foundation to support forty floors, where electrical runs, how HVAC ties in, and what the final layout looks like. Calling this "vibecoding" as an insult misses the point. AI handles syntax so I can focus on how the engine runs. It also exposes how broken software licensing is. Selling clunky subscriptions, charging for bugs, and charging again for patches is dead. Value is shifting back to open source, real support, and experience. Open-source tech like Proxmox and ERPNext are primed for this, and I build right on top of them. So when you see me arguing with traditional devs in forums, it isn't Dunning-Kruger. It's just the pattern laying itself out before you see it. I build governance into everything. In my world, I see a farm with a barn housing bare-metal servers running Proxmox while my ERPNext hums along generating mailbox money. ;) Some of my GitHub Projects so far: Maude for Claude: A dedicated partner environment operating right inside Claude. Proximo: A lean infrastructure and governance tool built to streamline local workflows. Pacioli: An open-source accounting and operational framework built for real execution. AI can write all the code it wants. It still can't bolt a rack into a datacenter or manufacture the chips it needs to run on.

• 
  DFIR Radar (@DFIR_Radar) reported 5 minutes ago

  AmnesiaStealer is a multi-stage Rust-based macOS infostealer distributed via a fake GitHub page, targeting login credentials, browser sessions, and system data through a stealthy, patched-bypass chain. Key findings: - Initial access via a counterfeit GitHub download page delivering a malicious disk image or package. The installer prompts the victim for their login password under a false pretext, capturing macOS credentials at first run (T1056.002). - Written in Rust, the stealer runs across multiple stages to harvest browser data from Chromium-based browsers, including cookies, saved passwords, and autofill data stored in profile directories under ~/Library/Application Support. - The malware attempts macOS-specific TCC and Gatekeeper bypasses that Apple has since patched, making OS patch level a critical triage data point when assessing exposure. - A standout capability: the operator can take live, hidden control of the victim's Chromium browser to hijack authenticated sessions, enabling account takeover without needing to decrypt stolen cookies. Triage focus: check for unsigned or ad-hoc signed binaries in /Applications and ~/Downloads, review macOS Unified Log for osascript or security prompts tied to unfamiliar processes, and inspect Chromium profile directories for unexpected access by non-browser processes. Patch level matters here. Full IOC list available in the Jamf Threat Labs report. #DFIR_Radar

• 
  FORKLINE (@Forkline_xyz) reported 7 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

• 
  Bárbaro Javier (@cubancodepath) reported 7 minutes ago

  GitHub SSH is down, one more time. Another day, the world is getting worse since the IA.

• 
  wunk (@Wunkolo) reported 8 minutes ago

  @NaesoLeBeau @rubynesoberi All of these AI-recomp/decomp projects are just the latest scene that AI-grifting behavior has infected. They capture a pre-existing fanbase for Twitter-engagement or GitHub-stars or whatever and then move on to the next grift once the response slows down.

• 
  noun1825 🦇🔊 (@cart_collector) reported 8 minutes ago

  @tobi I looked up the german tank problem and it seems it is about estimating the total number of items from a sample of numbered items picked from the set. Perhaps I am not understanding you completely but how is having an early github account related to the total number of accounts?

• 
  AFRICA IS HOME GLOBAL (@AfricaisHOME2) reported 10 minutes ago

  Nvidia-backed AI code review startup CodeRabbit just raised a big new round that values it at $1.5 billion, marking a major step up for the 2-year-old company. The deal highlights how investors are betting on the next bottleneck in AI coding: not generating code, but reviewing it. With tools like GitHub Copilot, Cursor, and Claude Code letting developers ship code much faster, teams have hit a wall in pull requests and quality checks. CodeRabbit positions itself as the governance layer in between, a context-aware AI reviewer that understands a company’s codebase, flags bugs, security issues, and style problems, and drops feedback directly in IDEs, CLI, and *** platforms. The company, founded in early 2023 by Harjot Gill after he sold Netsil to Nutanix, has grown fast on that thesis. It announced a $60 million Series B led by Scale Venture Partners with participation from NVentures, Nvidia’s venture arm, plus CRV, Harmony Partners and others, bringing total funding to $88 million. At the time that round valued CodeRabbit at $550 million. Revenue is growing about 20% month-over-month and ARR has topped $15 million. More than 8,000 companies including Chegg, Groupon, Life360 and Mercury now use it, and over 100,000 open-source projects run it on GitHub Marketplace. Customers report big speedups, Groupon cut review-to-production time from 86 hours to 39 minutes. CodeRabbit says teams using it can cut human reviewers in half, and it’s doubling headcount to keep up with demand as vibe coding pushes more AI-generated code into production. - World Business News.

• 
  0logn (@0logn) reported 17 minutes ago

  Remote coding-agents (aka software factories) are really a dev-ops (not AI) problem. Some security problems to solve but mainly it's a high-performance caching problem. The CI providers (e.g,. Github Actions, Blacksmith) were (are?) the best positioned to solve this.

• 
  rusa (@rusabuilds) reported 18 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.

• 
  Lethalmon (@Lethalmon) reported 19 minutes ago

  @briccenjoyer I think that, even if your connection is stable, GitHub doesn't like slow connection. It might be GitHub that force stops your download

• 
  Brabalawuka (@brabalawuka) reported 19 minutes ago

  @thdxr Does the desktop beta support v2 server alr? I tried search with ChatGPT but give very vague answers based on github commit history / lissue log

• 
  Mark yu (@Markymarco34) reported 19 minutes ago

  Yes, the network is currently running and the signer set is healthy. But current operational health does not mean the Aug. 12 stall has been permanently resolved. The related GitHub fix is still open and unmerged.

• 
  Harshit Mathur (@spiderboyis) reported 21 minutes ago

  the biggest lie i tell myself as a dev is that i’m making "massive progress" just because my github graph is full of green squares. ​writing clean code feels incredibly productive, but right now, it’s literally just the baseline. ​if you spend 90% of your week obsessing over the perfect backend architecture and 10% actually figuring out how to get users, you don’t have a startup. you just have a really stressful, unpaid hobby. ​i forced myself to close the IDE today and just do pure outbound outreach. getting ignored by 20 people hurts way more than a compiler error. ​technical founders -> what is the one marketing task you have been actively avoiding this week?

• 
  The obonigwe (@ogbonigwe1) reported 21 minutes ago

  blacksmith and github are down again. i don tire

• 
  naufaldi athallah (@nopaljin) reported 24 minutes ago

  wtf github down

• 
  shao (@randomor) reported 24 minutes ago

  Had the same thought few months back when canvas LMS was down. So I vibed a prototype and had to stop after all my token depleted. Would be nice to get sponsored by others who are interested in an OSS LMS with a modern stack. The next GitHub alternative should solve this.

• 
  Abi (@abh3i3) reported 25 minutes ago

  While trying to fix it, I checked old GitHub workflow actions from a year ago. Seeing those 1-year-old actions actually made me smile—it’s officially been a year! But I was still stuck trying every way to solve the issue without a clue what was wrong. (3/5)

• 
  FL∆CKØ (@Asapteejo) reported 26 minutes ago

  there should be a button in github called “this was working yesterday” it doesn’t fix anything it just adds important historical context

• 
  marc 🦀 (@mkenzo_8) reported 28 minutes ago

  @github please fix yourself

• 
  BRICS and G20 (@BRICSANDG20) reported 34 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.

• 
  Joshua Riley (@JoshuaRileyDev) reported 35 minutes ago

  @bil0090 GitHub Issues is gonna be cool, next should be linear issues then maybe have a way to auto poll and start threads when a new ticket is opened, been wanting this for a while as it would be like OpenAI’s Symphony concept

• 
  Narayan Babu (@nyn) reported 40 minutes ago

  My cursor ( linked via my github email) and x ( linked to gmail ) are not 'mergeable' because they've different emails. There's no way to add an additional email either to cursor to fix this. What's the solve? @cursor_ai

• 
  Charlie Hills (@charliejhills) reported 48 minutes ago

  Most people are using AI to code backwards. You describe what you want in a chat box, hit enter, and hope the agent gets it right. Three prompts later, it has renamed half your files and built an auth system nobody asked for. GitHub's fix? Spec Kit. It already has 126K+ stars. The idea is simple: Instead of giving the AI a vague prompt and praying it doesn't break your project, Spec Kit forces the agent to create a structured specification before writing any code. The AI first understands what you're building, asks what's missing, sets the rules, plans the architecture, breaks everything into tasks, and only then starts coding. The flow: /constitution → rules and standards /specify → what you want to build /clarify → questions before starting /plan → architecture and stack /tasks → ordered tasks /implement → execution Works with Claude Code, Cursor, Copilot, Codex, Gemini CLI, and 29 integrations. More planning upfront. Way less time undoing what the AI did while you weren't looking. Open source. MIT licensed. Built by GitHub.

• 
  pseudo 🇺🇦 (@pseudotheos) reported 48 minutes ago

  GitHub goes down more than solana at this point

• 
  Moist Burro (@BefuddledBuddle) reported 48 minutes ago

  @zephyr_z9 Link is broken for me on GitHub, do you have a diff one?

• 
  0xFoX ⟠ (@Sprawl__Network) reported 49 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.

• 
  Chase McDougall (@ChaseMcDou) reported 52 minutes ago

  @KaustubhTrived6 @ayesha_fatiima But if I can't push to GitHub because GitHub is down - then how can they push to GitHub to fix GitHub

• 
  Jamie Baek (@jamie_baek_) reported 55 minutes ago

  We lack volume. I need to start enacting my advice, of that we need to scale the denominator. Why don’t we do more? Why don’t we apply to 10,000 jobs with the awful university, the terrible GPA and the bad credentials that we have right now? We can cook up a resume with the experience that we have, not that much, but TMUA9's open source materials of written workings would be a good profile boost, alongside some credentials on LinkedIn/Github to show the work that you are doing. Why not apply to the top 50 startup accelerators in every single country? You applied to one startup accelerator(YC), how ******** do you expect to be successful with your venture? You did not fail enough. You don’t have the right to iterate if you did not fail. You did not get enough rejection mails for you to say that there is a reason why you got rejected. Did you start 500 SaaS businesses, did you learn all the coding languages… There is no volume for you right now. You did not read 10,000 books.

• 
  teewelk (@teewelk) reported 60 minutes ago

  @jpschroeder @0xBOYD apparently it decided my pgTAP wasn't important, and now i'm stuck at my office trying to fix whatever the hell it did to my migrations order so it will pass my github checks. Back to Sol I go.