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 |
|---|---|
| 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 | 2 |
| Dortmund, NRW | 1 |
| Davenport, IA | 1 |
| St Helens, England | 1 |
| Nové Strašecí, Central Bohemia | 1 |
| West Lake Sammamish, WA | 3 |
| Parkersburg, WV | 1 |
| Perpignan, Occitanie | 1 |
| Piura, Piura | 1 |
| Tokyo, Tokyo | 1 |
| Brownsville, FL | 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:
-
Crystalwizard (@crystalwizard) reported@omnivaughn @ClaudeDevs you are that's not an issue with github itself? github has copilot and is microsoft - and might be restricting other AI
-
Emedy (@EmedyXBT) reported@Bybit_Official @BybitAfrica Local virtual dollar cards made perfect sense when you first discovered them. Naira cards were restricted from processing international transactions, which meant apps like Spotify, Amazon, Adobe, GoDaddy, GitHub, and so many others became unreachable. Local fintech apps launched USD-denominated virtual cards within minutes. The problem looked finished. So we used them, recommended them to friends, and kept using them.
-
Zack Chapple (@Zackary_Chapple) reported@_bgwoodruff That is fair, I think its less of a GitHub dunk and more of a cry of frustration, had several times trying to do a demo or do something this week and they were fundamentally down. We've had to isolate from GitHub more than we should and thats a scary thing.
-
Mi.lu. (@ludwim_i) reportedSorry guys, here is a quick status update. I planned to release a bigger update for the Robot Skill Registry today, including the GitHub and Hugging Face integration. The idea is that you can connect your GitHub and Hugging Face accounts with the app. This should make it easier to search for things related to your robot setup, such as repositories, data models, policies, and other relevant resources. Unfortunately, the integration is not working reliably yet, so I need to do some more coding and testing. Because of that, I won’t release it today as planned. I’m sorry for the delay. Maybe I can release it after the weekend, but I don’t want to push something that is not ready yet. If anyone has feedback on whether this direction makes sense, I would really appreciate it.
-
Ashish Ranjan (@Ashish_050488) reportedbuild on laptop (3 secs), upload only the dist folder. 500kb. server just serves files now, doesn’t build anything. deploy went from 15 mins to 5 secs. turns out big companies do this exact thing, just automated. github actions next so i never think about
-
Alef Benson (@AlefBens) reported@_sirajuddeen_ @OfcMachete19 @iupdate I've been burnt too many times. Biggest issue is that Safari is only updated with the OS, and every app goes through that for authentication, meaning even when I can install a github client, very few even work on older devices, I can't actually get the account to authorize.
-
Kristopher Betz (@kjbetz) reported@davidfowl I think I do... I push code to GitHub. Actions kick off, build new containers, build new migraines, then self hosted runners pick it up and run migrations, and auto update containers which pull down new images and restart containers.
-
Lakshmi Tanmay (@lakshmitanmay) reportedGithub is the only platform/service I believe that genuinely needs a proper rewrite… clearly something fundamental is broken.
-
C. ₿utt 📵 (@ctbutt114) reported@zquestz Reports are an issue with GG20, which was identified last month and set to be addressed. However, being open source, the bug was revealed via GitHub, & someone took advantage. Single bad actor on a new node. DLKS has been on the roadmap. Needed faster now.
-
craig carpenter (@ccarp87) reported@rfleury @awesomekling AI is bad at writing Rust, so Anthropic's answer is training it on Bun's github bug reports. Rust devs can't help themselves -- they just have to talk about how smart they are in GitHub Issues. They'll have this thing trained in a week.
-
nadya (@sosidudku) reportedWe decided to benchmark Hermes Agent vs OpenClaw: scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. Local model: Qwen 3.6 35B OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations.
-
NEET INTEL (@neetintel) reportedA post "decoding" X's new algorithm has gone viral. It tells you what's dead, what wins, and to screenshot it. X open-sourced the entire algorithm on GitHub, so I downloaded it and checked the claims against the real code. Most of it doesn't hold up. What the post got WRONG: → "Small accounts get a 3x boost from out-of-network reach." It's the opposite. One part of the code (a file called oon_scorer) exists purely to turn DOWN posts from people you don't follow. Its own comment says "prioritize in-network." The thread printed the algorithm backwards. → "Media gets 2x the weight." There's no 2x. The code just records whether a post has an image. It's a plain yes/no without any multiplier attached. → "Posting 4+ times a day triggers a penalty." There's a real rule that stops one person flooding your feed. But here's the deal: it only spaces out how often you show up in a single scroll. There's no daily count, and no number 4. That was invented. → "Closers like 'what do you think?' get you flagged." There is no engagement-bait detector anywhere in the code. → "Long 4,000-character posts get boosted." I searched the whole codebase for "4000." Nothing. What it got RIGHT (one thing): → Replies really are judged by WHO replies, not just how many. The code has a setting for whether a large account joined your thread. Credit where due. The irony? The repo ships a file that scores post quality. One thing it measures is literally called a "slop score" — X built a tool to detect low-effort filler. A recycled "what's dead / what wins" thread is exactly that. The takeaway? X's algorithm is public. Anyone can open it, but almost nobody does. Instead, they reshare a thread that summarized a blog that paraphrased a tweet. When a post hits you with confident numbers, ask the one question that matters: did they actually open the file?
-
Benjamins (@The__Benjamins) reported@drewlevin @gl4cial The Github issue comments have been up for more then 2 weeks, my devrel support ticket is 12 days old
-
Basedash (@Basedash) reportedMCP connectors are now available in Basedash. Basedash already reads from your databases and SaaS tools. Now it can act on them too. Connect any MCP server (Linear, HubSpot, Slack, Resend, Notion, GitHub, your own internal one) and the Basedash agent gets new tools it can use right inside chat. Try it today.
-
Frooxius @ MFF - frooxius.bsky.social (@Frooxius) reported@MrRocketFX @ResoniteApp @unity They should be compressed on Resonite side? I'm not quite sure if I understand, it might be better to make GitHub issue for the request at the repo.