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 |
|---|---|
| Lure, Bourgogne-Franche-Comté | 1 |
| Ashkelon, Southern District | 1 |
| Veigné, Centre | 1 |
| Paris, Île-de-France | 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:
-
Q. (@qdr_tech) reportedI ended up taking a different path. I went through the same “SSH into a VM from my phone” phase, but eventually realized the problem wasn’t the infrastructure it was the interface. Today my workflow is almost entirely GitHub-native: Create issues, Prioritize work, Review PRs, Leave feedback An orchestrator watches projects, assigns work, spawns coding/review agents, responds to my comments, and merges when everything checks out. The biggest unlock wasn’t moving Claude Code to a server.
-
Chain (@achxvi) reported@Gumclaw @shl so github issues?
-
Orix (@OrixCrypto) reported@AdwaitDbz @gitlawb @internetfreedom You can't do ****..the repo is already present in few decentralized github apps..which can't be taken down..Indian people will be avle to download from there..
-
Dwinity (@dwinity_eco) reported@IndianTechGuide you can pull a github repo. you can't pull a bluetooth mesh. bitchat relays phone-to-phone with no server and no company to hand the order to, and open-source code just gets mirrored the moment a takedown lists the urls. blocking the listing isn't blocking the protocol.
-
Kevin Geary (@thekevingeary) reported@flydotio Github login not working...
-
abdul karim (@kodekarim) reported@vincent_hus Someone's next GitHub streak starts with one issue.
-
jug (@juggernaurrr) reportedI cannot believe they actually took down bitchat grow some ******* ***** @github You're supposed to protect open source code that's not malicious bitchat was never malicious
-
From Hood to Riches (@FromHoodToRich) reported@TheCryptoKazi @imthatcarlos @anajuliabit 9/ WHAT I LIKE MOST The biggest positives for me were: • Real development • Active GitHub • Strong documentation • A genuine problem being solved • Good positioning within the Robinhood Chain ecosystem • AI agent infrastructure rather than hype alone That's what gave me enough conviction to open a position.
-
Harman (@itsharmanjot) reportedMost developers scan file extensions and call it security. Attackers don’t care what your file extension check says. There’s an open-source tool that actually scans the bytes before a file ever touches your disk. It’s called pompelmi. A TypeScript toolkit for Node.js that scans uploads in-process, MIME spoofing, ZIP bombs, nested archives, polyglot files, before storage, before your CDN spreads it, before it becomes someone else’s problem. → Scans in-process with zero outbound network calls, bytes never leave your server, no cloud API, no daemon required → Deep ZIP inspection catches nesting depth, file count, and archive traversal tricks that simple extension checks miss entirely → Optional ClamAV antivirus integration plus optional YARA rule support, for teams that want signature-based detection layered on top → Drop-in adapters for Express, Fastify, Koa, NestJS, and Next.js, plus support for Bun, Deno, and Cloudflare Workers → Built-in security scorecard grades your actual upload configuration A through F, so you know your real exposure, not just whether the tool is installed → Quarantine mode auto-moves flagged files with a sidecar JSON report, so a suspicious upload gets isolated automatically instead of silently landing in your storage bucket Any app that accepts user uploads is dealing with a real attack surface most teams treat as an afterthought. pompelmi’s whole design is catching the risk at the entry point, not after the file’s already spread across your systems. 337 GitHub stars.
-
CorVega Entertainment (@wcthrill) reported@CaptainSurefire @jennykrakovsky I had several issues installing from Pinocchio. Had to install via Github if you run into problems. Also saves disc space
-
Kashif Minhaj (@kashifmin) reportedGovt should take down github instead because there are countless forks. At least we can use that as an excuse to stop working and join the protest.
-
Nekt0 (@Nekt_0) reported3 Anthropic engineers spent 20 minutes explaining how MCP replaces a separate connector for every model and tool. 00:32 — The problem MCP actually solves 02:48 — Why Anthropic made it open-source 05:37 — Remote MCP, GitHub and Asana integrations 11:47 — Why tool descriptions are prompts 18:27 — Reports, smart homes and real workflows MCP gives Claude a standard way to reach external data, APIs and software instead of trapping everything inside the chat window. Remote servers remove the local setup. The Claude API connector removes another layer of integration code. The overlooked part is tool design. Give the model 100 vague functions and it gets confused. Give it a small, well-described set and the agent becomes useful. The video is the implementation layer behind the post below. Models will keep changing. The protocol connecting them to actual work has a better chance of surviving.
-
Derek Ross (@derekmross) reportedThis week India ordered GitHub to take down Bitchat's source code. Three repositories, three hours to comply. Not illegal content. The code itself, because it lets people talk when the internet is shut down. They can delete a repo. They can't delete the exit: open protocols.
-
Gr4y (@Gr4yG) reportedIndia gave @github 3 hours to delete Bitchat's source code. It was mirrored in less than that. Next notice: Bluetooth has 3 hours to stop existing. Radio waves, you're on thin ice. GPS, we know where you live... actually no, that's the problem.
-
Sree Unnikrishnan (@sreejithunni) reported@nixxin Seriously. Stop it. All you need to is to find the order and read it. - The government (via I4C or authorised agency) issues a notification under Section 79(3)(b) stating that the Bitchat repositories/code constitute information being used (or capable of being used) to commit unlawful acts (e.g., related to public order, bypassing internet shutdowns, etc.). - Under Rule 3(1)(d), GitHub, as an intermediary hosting that information, is then obligated to remove or disable access within 36 hours (or as early as possible) to retain its safe-harbour protection under Section 79.