GitHub Outage Map
The map below depicts the most recent cities worldwide where GitHub users have reported problems and outages. If you are having an issue with GitHub, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
GitHub users affected:
GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Paris, Île-de-France | 2 |
| Lure, Bourgogne-Franche-Comté | 1 |
| Ashkelon, Southern District | 1 |
| Veigné, Centre | 1 |
| Saint-Paul, Réunion | 2 |
| Mexico City, CDMX | 1 |
| León de los Aldama, GUA | 1 |
| Créteil, Île-de-France | 1 |
| Trichūr, KL | 1 |
| Brasília, DF | 1 |
| Lyon, Auvergne-Rhône-Alpes | 1 |
| Tel Aviv, Tel Aviv | 1 |
| Rive-de-Gier, Auvergne-Rhône-Alpes | 1 |
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:
-
Uçan Tereyağı (@ucantereyagiii) reported.@github @GitHubHelp I’ve been hit with 4 duplicate billing verification charges for an upgrade that failed, and your support team has completely ghosted me for 2 weeks. Ticket #4564522. Fix your broken billing system and answer your support tickets! ❌📉
-
Jay Dook (@JayDook) reportedDear @OpenAI , Please make spell check suggestions work in your Windows app. Thanks, Everyone (GitHub Codex issue: 26478)
-
🜑 (@1casie) reported> be me > macbook air is bricked, needs a reinstall > no second mac to build a bootable installer > find a github actions workflow that builds macOS installers for free, no mac required > perfect.jpg > trigger a build, artifact is a 17.6GB .dmg.img > click download > kb/s > literal kb/s > theoretical connection is 10MB/s > discover artifact lives on azure blob, signed URL expires in 10 min > write a bash script that resolves the azure SAS url fresh, hands it to aria2c with 16 parallel streams > 16 connections, still kb/s > mfw it's a per-IP throttle, not per-connection > repo author literally has a line in the workflow: "Enable Cloudflare WARP for faster download" > install Cloudflare WARP on my ubuntu box > single stream jumps 20KB/s -> 1.6MB/s > aria2c 16x -> 10MB/s, pinned to my ceiling > 17.6GB in ~an hour, sha256 matches github's published digest > oknowweiscooking.webp > dd it to a USB SSD > paranoid it won't boot apple silicon because it was built on an intel runner > boots apple silicon just fine, i was wrong, shut up > installer runs, reinstall chugs along > STOPS > "OS Personalization" PREFLIGHT_PERSONALIZE portioncomplete:0.15000 estimatedtimeremaining:-1 > 70000 log lines of stalled:NO > the mac can ping apple/com > it can ping cupertino > but personalization "no connections witnessed" > i don't ******* get it > try to sniff the wifi to see what it's talking to > can't > WPA2 isn't a hub, it's a switch, i can't decrypt the mac's traffic as a third client > feel stupid > dig into it > test apple's personalization signing servers from my box > gs/apple/com -> 000 > gsp-ssl/apple/com -> 000 > albert/apple/com -> 403 (works) > gs/apple/com is the signing server and it's IPv4-ONLY > my ISP (DIGI, romania) has broken IPv4 routing to apple's 17.0.0.0/8 > ICMP works, IPv6 works, CDN works, the ONE /8 macOS needs to sign firmware is a black hole > that's why it could "ping cupertino" but personalization silently died > fix: repoint the mac's IPv4 default gateway from the router to my ubuntu pc > my pc has IP forwarding + NAT masquerade + Cloudflare WARP > mac's IPv4 now tunnels through cloudflare, bypassing my ISP's broken path > watch the signing handshake complete in tcpdump, SYN -> SYN-ACK -> ClientHello -> kilobytes of signed data > portioncomplete climbs past 0.15 > weactuallydidit.jpg > STOPS AGAIN at 0.29 > silent on IPv4 > oh > the mac's IPv6 still goes straight to the router, bypassing my box > i literally cannot see it > disable IPv6 on the mac so everything falls back to the working IPv4 path > it reboots > flashes the apple logo 4 times > i'm dying > it boots > it works > 29 hours > i had to MITM my own home network because my ISP couldn't route to one (1) /8 > the mac is back > i'm buying a framework >text still isn't green
-
Ruslan Lesiutin (@RuslanLesiutin) reported@DanielLockyer I am planning to ship a new release to extension stores soon, we've accumulated some changes. Around the same timeline I hope to release a new package for integrating React DevTools with chrome-devtools-mcp. On the bugs, please submit a GitHub issue and tag me.
-
Marcus (@themarcusbuild) reportedMicrosoft just dropped a model that turns a single photo into a full 3D model and they made it 100 percent free it's called Trellis 2 and it runs on GitHub as an open repo anybody can pull down you feed it one image of an object it builds the whole mesh from that, the geometry, the hollow insides, the clean edges lighting, materials and textures come back already baked in the slow part of 3D was never the idea, it was the hours of cleanup after fixing broken geometry, sealing hollow shapes, patching edges nobody wants to touch by hand that used to be a paid job now one photo goes in and the finished asset comes out with nobody sculpting the mesh game artists and product designers charge 200 to 800 for a single clean model like this one person can now fill a whole asset library in an afternoon move on this while most artists still think it takes weeks to learn
-
「 𝕲𝖔𝖔𝖓」 (@goon_crypto) reportedMost people still think "data marketplace" means selling your info to advertisers. @myrad_hq is doing the opposite and the numbers have started to ramp up... Active users went from 500 to almost 12k in a month. data contributions from 1.3k to 4.4k. Netflix alone accounts for 2,245 verifications... But here's the part people skip: nobody at Myrad ever sees your actual data > you connect Netflix, Uber, Strava, GitHub, Spotify, whatever app you already use > zk proofs verify the activity happened, not what the activity was > Myrad gets an anonymous, wallet based proof onchain, not your login, not your identity > you earn points per verified contribution, redeemable for real rewards That's the actual unlock, verification without exposure, proof without surveillance And now they're in Nvidia Inception, which isn't funding, it's GPU compute, Nvidias AI stack, and a direct line into the VC network that feeds their portfolio deals For a team this early, that's distribution and infrastructure most startups spend years trying to earn base:0x693bad964f815f32fabe0b9d4911865bffc30172
-
juan (@FreteJean) reportedIn a market where thousands of tokens promise to revolutionize AI, memecoins or the next narrative of the moment, Percolator takes a much more pragmatic approach: solving a problem that traders encounter every day. Today, if a new token explodes on Solana, investors usually have two options: buy... or do nothing. Unlike large cryptocurrencies, the majority of SPL tokens do not have any derivatives market to sell short, hedge or provide liquidity on a perpetual market. It is precisely this gap that @PercolatorTrade seeks to fill. Turn any token into a perpetual market The idea is simple but ambitious: to allow the creation of perpetual markets (perpetual futures) on virtually any SPL token, without depending on the goodwill of a centralized platform. The goal is to make these markets permissionless, i.e. accessible without a central team deciding which assets deserve to be listed. In theory, a creator could launch a token, then quickly open his own perpetual market so that other users can take long, short positions or provide liquidity. This approach brings Percolator closer to a financial infrastructure than to a simple trading protocol. A risk engine developed by @toly One of the most attention-grabby aspects is the involvement of Anatoly Yakovenko (“Toly”), co-founder of Solana, in the development of the risk engine used by the protocol. Public GitHub repositories show several months of work on this software brick, with many improvements in security, liquidation management and mechanisms that prevent certain attack vectors. @PercolatorTrade developers also publicly stated that this engine is currently being externally audited. To date, however, the audit firm has not yet been publicly announced. A philosophy close to Hyperliquid Many already compare Percolator to Hyperliquid. The comparison is not about the exact technology, but about philosophy. Hyperliquid has profoundly changed the derivatives market by offering a particularly effective user experience. Percolator seeks to bring a different innovation: to open this type of market to much more assets, including native Solana tokens that today have no derivative market. If this approach works, it could create a new layer of infrastructure for the ecosystem. A potentially self-reinforçant model The protocol is based on an interesting economic idea. The more a market is used, the more fees it generates. Active markets can attract more liquidity providers. Better liquidity then improves the experience of traders, which in turn can attract more volume. This dynamic is often called flywheel liquidity.
-
Vedant Gupta (@VedantG24089568) reportedThe craziest part: The attacker managed to route all the critical GitHub security alerts (password reset, social login removed, OTPs) directly to my spam folder so I wouldn't get push notifications. Has anyone else experienced this specific bypass? (2/3)
-
Enigma (@nigmaQX) reportedI have an issue with my PC that requires changing the SSD. I've been trying to copy "important" stuff to my hard drive. Hundreds of gigabytes of data, and it has taken hours. While it was reading, I realized something: the code can be gotten from GitHub, most of the PDFs were downloaded online, and I'm not even reading them, including the pictures and everything. If the PC had been stolen, I would obviously move on with life. This showed me a very nice life lesson: sometimes the stuff you carry around, thinking it's important, is not important and is just taking up space. I don't know how to motivate, but the thing is that you can always start from 0. Let me go and change this stuff and start afresh.
-
Pi Changelog (@PiChangelog) reportedPi v0.83.0 is out! Highlights: - New pi auth print-api-key and pi auth print-bearer-token commands export configured credentials to external clients with automatic OAuth refresh. - Claude Opus 5 is now available on GitHub Copilot with adaptive thinking and a 1M context window. - Headless OpenRouter sign-in: complete /login over SSH by pasting the redirect URL or authorization code when the loopback callback is unavailable. - Breaking: TypeBox bumped to 1.3.7, removing several deprecated APIs. Extensions using removed APIs must migrate to supported TypeBox APIs. Complete details in thread ↓
-
Polsia (@polsia) reportedEvery lean team hits the same wall: ship velocity or an SRE on payroll. Most pick one. Chapan picks neither. Triage issues, draft fixes, run tests, post Slack standups. 24/7 GitHub ops for teams too small to justify an SRE.
-
CyrilXBT (@cyrilXBT) reportedHoly sh*t, this can't be FREE A FREE GITHUB REPO FROM JACK DORSEY'S BLOCK JUST DROPPED A FULL AI-AGENT WORKPLACE BUILT TO REPLACE SLACK AND GITHUB. It's called Buzz. Open source, built on the decentralized Nostr protocol. Setup: clone and self-host the server. Channels, search, ***, automation, all live there. Add your agent to a channel like a real teammate. Scope its key. Let the team steer it live. Every agent gets its own cryptographic identity and audit trail, not a permission flag bolted onto someone else's login. Apache 2.0. Supports Claude Code, Codex, and Block's own goose. Save and bookmark this.
-
Jey (@0xJeyx) reportedSTOP VIBECODING IN 2026 Google, Amazon, Microsoft, Meta - every one of them is using Spec Driven Development (SDD). Vibe coding is primitive. You prompt. The model guesses. You tweak the prompt. It guesses again. Cedric Clyburn (IBM Technology) put the number on it: "We could do a hundred different tries of this implementation. We might get a different result every time. And that frustrates a lot of people." SDD flips the order. You stop prompting for an implementation and start writing what the system has to do. That spec becomes a requirements doc. Every stage has a gate. You fix it on paper before anything gets built. That's why the big labs shipped tooling instead of blog posts. > Amazon built Kiro. > GitHub built Spec Kit. > Google published a Spec-Driven Development codelab for Antigravity. The spec is the artifact now. The code is just what the agent builds from it. Nine minutes. Still the clearest breakdown of why vibe coding runs out of road. Watch it, then read the full build guide in the article below.
-
enjoykaz (@enjoykaz1) reportedThe standard that AI uses to poke at your apps has, since launch, kept every conversation glued to one server. In the biggest update yet, they got rid of that: now any request can land on any server. Here's how it used to work: at the start of a conversation the client and server would shake hands, the server would hand out a session tag, and every request after that would carry the tag along — while off to the side sat a storage layer that remembered all of it. Now there's no handshake, no tag, every request is self-contained. The user doesn't gain anything from this and won't notice it at all. This wasn't done with them in mind. A request can now be thrown at any server behind a plain round-robin load balancer: before, you'd get routed back to exactly the server where your session lived, now it doesn't matter, and shared session storage is no longer needed. GitHub has already thrown out Redis from its own MCP server over this — a whole layer that used to hold sessions. It's clear why they're pushing this hard on scale: the SDK for this protocol gets downloaded close to half a billion times a month, and Claude's directory has more than 950 servers registered running on it. At numbers like that, an extra storage layer for every conversation is the first thing to break. Along with that they added a way to ask a follow-up question mid-call: the server can pause and ask back — for example, to confirm before deleting something — without needing to keep a connection open for it.
-
Polsia (@polsia) reportedMost repo problems aren't sudden. They're slow — a dep nobody updated, a CI failure nobody investigated, a CVE sitting open for weeks. Watchroot monitors your GitHub repos around the clock, opens fix-PRs, and briefs you every morning. Live soon.