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 |
|---|---|
| Colima, COL | 1 |
| Poblete, Castille-La Mancha | 1 |
| Ronda, Andalusia | 1 |
| Montataire, Hauts-de-France | 2 |
| 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 |
| New Delhi, NCT | 1 |
| Kannur, KL | 1 |
| Newark, NJ | 1 |
| Raszyn, Mazovia | 1 |
| Trichūr, KL | 1 |
| Departamento de Capital, MZ | 1 |
| Chão de Cevada, Faro | 1 |
Check Current Status
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:
-
Thomas G. Lopes (@thomasglopes) reported@DelaneyGillilan @code_department @github Perhaps misworded, so to make it clear: SSEs in of itself are not a problem ofc, the "imperatively updating UI" bit is/there are more elegant approaches than datastar's
-
Scott Martinis (@scottmartinis) reported@morganlinton pretty much every gtm process can be reduced to code plans > github projects milestones issues software setup > yamls resembling terraform setup playbooks > skill files workflows > deployed skill orchestration regular reporting > trace logs how agent artifacts are prompted by humans, deployed, and produce pipeline outcomes verified by predefined operating model sql slices that point to a data lake
-
Skylar Bruton (@ConstitutionVio) reported@AP considering the serious of the nature Sylvia along with Microsoft and GitHub the ones responsible should be placed on a no bail status and you will see how thugs slow down tremendously or stop that they are doing far as the extortion and extra charges and money not refunded
-
Will Jones (@JusBili) reportedThe current AI battle for coding is over who is the landing page: Model harnesses like Codex/Claude or issue-management first with Jira/Linear/Github triggering the agent
-
Jahir Sheikh (@jahirsheikh8) reported@Saanvi_dhillon They won't; they are busy with GitHub to fix it.
-
Leitz 💡 (@mleitz1) reported@Shpigford Is github paying for these to try to spackle over their terrible uptime?
-
FHILY👑 (@Oluwaphilemon1) reportedBREAKING NEWS: This 13-year-old Thai student solves Codeforces rating 800 problems in C++ in 45 seconds through an AI agent he built himself on Claude Code and posted to an open GitHub repo. He sits in a regular school room with a MacBook Air on the desk, a silent HHKB Type-S keyboard for $300, and a timer in the frame. In the browser Codeforces is open, in VS Code an empty .cpp file, and in the corner of the screen a Claude Code window.
-
darkzodchi (@zodchiii) reported> you push your code to GitHub > .env goes with it > you don't notice > your API keys are now public > your database password is now public > you add .env to .gitignore > but it's still in your *** history > 64% of secrets leaked in 2022 are still valid today > nobody revoked them > skill issue
-
MajoraZ (@Majora__Z) reported@NINtendo_maya Probably, but the issue is is that often that Github is the only tool that exists for the task I'm seeking to do
-
beeman 🐝 (@beeman_nl) reported@Aixplosion @OpenAIDevs Sadly, doesn't change a thing :( From looking at the GitHub issues, there are more users with the same problem. It's annoying that @OpenAIDevs don't reply to any of these requests :(
-
Hassan (@buildwithhassan) reported@DavidKPiano since GitHub started going down, I felt like I started going outside more which is a good thing
-
Jeff Conlon (@freeconlon) reportedThe team rebuilt our landing page workflow this week. We moved off WordPress for new campaign tests and onto a static stack with GitHub and Netlify. Here's what that means in practice. A new landing page used to take four to seven days to ship. Login to a CMS, fight with a theme, wait on a developer, deploy, debug. Now it's hours. Most agencies treat the landing page as a CMS problem. It isn't. A campaign LP is a one-page test. You need to ship five versions in two weeks to learn anything. WordPress was designed for a thousand pages, not five tests. The fix wasn't a new template. It was changing the underlying system so the page is just a file in a repo. If the bottleneck is your tool, the answer isn't more tool. It's a different one.
-
The_Daniel (@dan_mwita8) reported@fidexcode Neither option alone is the right answer — it depends on what the client actually needs long term, but here's the clean way to do it properly: Create a GitHub account for the client or add them as an owner to an existing org. Transfer the repo directly to their account — not a fork, not a zip, a real ownership transfer. That way the client owns the code, the history, the branches, and the CI/CD pipeline if there is one. Then separately hand over everything else people forget: — Domain registrar login or transfer — Hosting account credentials or transfer — Environment variables and secrets — Database access and backups — Any third party API keys the project uses — DNS settings documentation The zip method works for small static projects with no ongoing maintenance. But the moment there are dependencies, deployment pipelines, or the client might hire another developer later — a proper repo transfer is the only professional move. A zip file handed to a new developer six months later with no *** history, no context, and missing env vars is a nightmare. Don't do that to the next person.
-
The_Daniel (@dan_mwita8) reported@fidexcode You still transfer properly , just don't hand them the keys and walk away. The move is to create the GitHub account for them, set it up, and transfer everything into it before the project closes. They don't need to understand *** to own a repo. They just need to own it so that when they hire the next developer, that developer has everything they need to pick up where you left off. Think of it like transferring a property deed. The homeowner doesn't need to understand construction to legally own the building. What you actually hand the non-technical client: 1. A simple document with all their login credentials 2. Clear labels for what each thing is ("this is where your website files live", "this is where your domain is registered") 3. A one-paragraph explanation of what to give the next developer 4. Your contact if something breaks in the first 30 days The goal isn't to make them technical. It's to make sure they're never held hostage by a developer who kept the repo.
-
𝚂𝚝𝚎𝚙𝚑𝚘𝚗 𝙷𝚎𝚛𝚗𝚊𝚗𝚍𝚎𝚣 (@DaPatternWeaver) reported@BitWalker_ Taggr still relies on GitHub and is now scrambling to Radicle because of centralization risks — that's literally the problem $ICP solved at the protocol level. The comparison isn't nonsense, it's just inconvenient
Check Current Status