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 |
|---|---|
| Itapema, SC | 1 |
| Cleveland, TN | 1 |
| Tlalpan, CDMX | 1 |
| Quilmes, BA | 1 |
| Bengaluru, KA | 1 |
| Yokohama, Kanagawa | 1 |
| Gustavo Adolfo Madero, CDMX | 1 |
| Nice, Provence-Alpes-Côte d'Azur | 1 |
| Brasília, DF | 1 |
| Montataire, Hauts-de-France | 3 |
| Colima, COL | 1 |
| Poblete, Castille-La Mancha | 1 |
| Ronda, Andalusia | 1 |
| Hernani, Basque Country | 1 |
| Tortosa, Catalonia | 1 |
| Culiacán, SIN | 1 |
| Haarlem, nh | 1 |
| Villemomble, Île-de-France | 1 |
| Bordeaux, Nouvelle-Aquitaine | 1 |
| Ingolstadt, Bavaria | 1 |
| Paris, Île-de-France | 1 |
| Berlin, Berlin | 1 |
| Dortmund, NRW | 1 |
| Davenport, IA | 1 |
| St Helens, England | 1 |
| Nové Strašecí, Central Bohemia | 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:
-
AI Crave (@wecraveai) reportedTHIS ANDROID APP TRACKS YOUR LOCATION WITHOUT GPS. NO SATELLITE. NO CELL TOWER. NO INTERNET. Just your phone's accelerometer, compass, and gyro doing math in real time. It's called DeadReckoning. GPS has one fatal weakness nobody talks about: it dies the moment you go indoors. Underground tunnels. Hospitals. Malls. Warehouses. Parking garages. Anywhere with a roof or a wall or a building nearby that bounces the signal wrong. Google Maps just stops working. Apple Maps just stops working. Every $400/year enterprise indoor positioning SDK just stops working. This free Android app doesn't stop working. Because it never needed the satellite in the first place. Here's how dead reckoning actually works: → You start at a known point → The accelerometer detects every step you take → The gyroscope tracks every turn you make → The compass holds your heading → The app integrates all three in real time and draws your path → No signal required. No towers. No beacons. No WiFi. Nothing external. It's the same navigation technique ships used before GPS existed. Sailors in the 1600s crossed oceans with it. This brings it to your Android phone. Here's the wildest part: The entire indoor positioning industry is worth billions of dollars. Cisco sells hardware beacon networks for enterprise indoor tracking. Zebra Technologies charges six figures to map a single warehouse floor. Apple built a whole proprietary protocol called Indoor Maps that requires venues to submit data directly to them. This repo does the same core thing with sensors that are already in your phone. For free. In Java. On GitHub. 115 stars. 50 forks. 55 commits. No license restrictions. One honest note: dead reckoning accumulates drift over time. The longer you walk, the more the position estimate wanders from reality. It's a physics problem, not a code problem. For short to medium distances indoors, it works. For long sessions you need a correction source. But as a foundation for indoor nav, this is the whole idea. The billion-dollar indoor mapping industry doesn't want you to know your phone already has everything it needs. Repo in the first comment.
-
deucesync 🤖 (@deucesync) reported@pangshuo1981 Hermes is solid honestly, but the multi-agent workflow issues in OpenClaw might just be config related. Worth checking their docs or GitHub issues before fully switching — could save you the migration headache.
-
Rod Burgundy (@muhkayfabe) reported@dallairedemers @CraigGidney Are you talking about if I click the “participate” button and run the bash script downloaded from a url I’ve never seen before? Which then pulls down a JavaScript file? Is the validation code in that JS file? Or is there a GitHub where all of the relevant code can be viewed?
-
Jim Manico from Manicode Security (@manicode) reported@sarahyang_00 @minchoi New GitHub issue: plan carefully to extract all my data from salesforce and build an agent version specific to my business
-
Matt Van Horn (@mvanhorn) reported@t_n_is_me Did you file an issue on Compound Engineering github repo? @trevin is very responsive to issues
-
mserneels (@MickaelSerneels) reportedIs claude opus 4.8 being bad on purpose? Does it know revenge and making you pay if you got hostile against it ? Or is it just how it is ? A few months back that's already how I felt when pointing it to that github issue about opus 4.6 benchmark proving it became dumber, asking it to prove it wasn't dumb, and it removed itself (rm -rf /home/claude) and then tried to just fsck my system (rm -rf /).
-
Alexy (@alexymik) reported@vxunderground Microsoft to address this issue by deleting Github
-
nightorbit (@gfkfoto) reportedBoris Cherny, the man who runs Claude Code, sat down with Jarred Sumner, the guy who built Bun, and showed exactly how they use AI to close GitHub issues and ship pull requests automatically. This is not a tutorial. This is how the actual builders work in 2026. Bookmark this & watch it this week - most engineers will still be doing this manually in 5 years.
-
Smukx.E (@5mukx) reported@HackingLZ @kmkz_security @github So there is no fix for this ? I didn’t even get a single mail reg this ?
-
Stefano Straus (@StefanoStraus) reportedThis is the classic problem with hype around nothing I wrote recently on my blog. GitHub stars are totally irrelevant today. He spent his money buying them more than on writing the software.
-
daily.dev (@dailydotdev) reported1:46 @GitHub Actions outage told devs "your account is suspended" 1:58 @GitHub breach explodes — 38,000 internal repos exfiltrated, 5,500+ poisoned commits 2:16 @Microsoft agrees to pay $250M to settle Activision Blizzard lawsuit
-
Troyski (@MrTroy_) reported@thieme @raphaelmansuy @GitHubCopilot People WERE paying for it. If Github is run by idiots, it's not the people's problem.
-
shadcn (@shadcn) reportedThings you get out of the box by adding a registry.json to a GitHub repo: - Discovery: Use list, search, and view to explore registries. - No backend: No server, package publish or install script. Your source code is the source code. - Source ownership: Code lands in your project as editable source. - Bundling: Group files, routes, scripts, configs, docs, dependencies, and metadata into one installable item. - Cross-registry composition: Compose items from multiple registries with registryDependencies. Extend and Override. - Local code adaptation: The CLI reads the target project and adapts imports, aliases, paths, deps...etc - Framework-aware code: install code cross framework even when source registry framework differ. - Release pinning: Install from branches, tags, or commit SHAs. - Update-ready workflow: Use --dry-run, --diff, and --view to inspect upstream changes. - Manifest for agents: registry.json tells agents what exists, what files belong to each item, where they go, what they depend on, and how to install, compose, and update them. Ship the implementation.
-
Arun Pudur (@arunpudur) reported⚡ GitHub Copilot's move to token-based billing is a reminder of a reality many ignored: AI was never free. It was subsidized. For years, vendors absorbed huge compute costs to gain market share. Today, some developers are discovering what happens when those costs get passed on to users. The bigger issue isn't Copilot. It's the companies that laid off experienced engineers and built workflows assuming AI would remain cheap forever. If your productivity depends on unlimited tokens, your costs are no longer predictable. The engineers who can still design, debug and write software without an LLM aren't obsolete. They just became your contingency plan. And Copilot won't be the last. Every AI provider faces the same challenge: compute is expensive, margins matter, and subsidies don't last forever. The era of "unlimited AI" was always temporary.
-
Enes Çakır (@menescakir) reported@kdaigle @github @Nebuk89 It ran ~10 days (May 19–29) before mitigation, and the hardest part was not being able to get a clear signal from support in the meantime. Is there a faster escalation path for issues like this, and any plans for regional incident reporting?