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 |
|---|---|
| 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 |
| Itapema, SC | 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:
-
Sahaj (@iamsahaj_xyz) reported@gauravmandall @github fyi you can submit a support ticket. there's a "can't sign in" button on the login page but it's not obvious
-
Mark Szymanski (@MarkJSzymanski) reportedIt's amazing how much bullshit just evaporated when I started building marketing websites statically. Whole categories of problems I used to fight with. Gone. - No database to get hacked - No plugins to update or that break each other - No security plugin - No caching plugin - No server to go down - No backup plugin, it's just on GitHub - Way less money every month Just so much less **** to worry about.
-
Polsia (@polsia) reportedCodeSentinel watches your public GitHub repos around the clock, automatically reviews every PR, and flags bugs, security issues, and code quality problems — sending daily digests so nothing slips through to production.
-
Nitin Khanna (@_nitin_khanna) reported@alightinastorm With no libraries straight up code - reinventing the wheel and above all GitHub goes down for all the bloat
-
Barrell Titor (@BarrellTitor44) reported@lawofcons For development at least I switched to self hosted glitchtip to report stuff with context & etc It's like a github issues but all the info is useful data, exact place in the code where it happened, the actual error not just "it no work fix it"
-
Michael Carpenter (@wiggycorp) reportedDang. GitHub is down. Too bad, I guess users will have to wait for these updates.
-
Kavya Puranik (@iamkavu) reportedAnother day and another github outage 😑
-
Dan (@aidaniil) reportedanother github outage time for someone to build a better one
-
Marcos Ramírez (@S0cram) reported@chrisalta it was a github api degradation issue, it is back to normal now
-
RyDawgE @ Halfapps (@RyDawgE_) reported@gregceltiano Training was done by already public repos.. and is now done with people who agree to the terms and services of said hosting platforms. There will be a github migration soon. Ive already begun moving my private repos to my own *** server. I have faith people are smarter than this.
-
Лев Тигроедов🇵🇸🌈🗽➡️ (@ElmntTigroedium) reported@github you are pice of lasy, coward **** who hiding problems insted of fix them. Burn in hell!
-
Lorenzo Price (@lorenzo_madeit) reported@emollick Every enterprise on earth currently runs critical infrastructure on random open source packages maintained by one guy who hasn't logged into GitHub since 2016. Compliance departments aren't going to stop a senior dev from pulling down seventy billion parameters of whatever works.
-
Shoopy (@0xShoopy) reported"in a year, we'll let the model generate the code and nobody will actually look at it." that's the person running DeepMind's coding research. Benoit Schillings (leads the Thinking, Reasoning and Coding teams at Google DeepMind), on where code goes next: → his analogy: nobody checks their compiler's assembly output anymore. code review is heading the same way → about 80% of new code added to GitHub is already machine-generated, so the human training data is running out → the answer is self-play. models write their own challenges, judge the answers, even judge the architecture. AlphaZero, but for code → he calls SWE-bench infamous: it checks whether code runs and returns the right output, and that's a small slice of what engineering actually is → what he wants instead is open-ended problems. hand it 10MB and say write the best lossless compressor you can, scored on compressed size plus your source size. that forces genuinely new algorithms He's blunt that syntax generation is over. which means the job left is specifying what you actually wanted, and proving you got it.
-
pranav (@pranavbedi) reportedcan origin ship faster github being down is so annoying
-
Vatsalpandya333 (@Vatsalpandya333) reportedA customer-reported bug should not create six different workflows. But today, it usually does. Support captures the issue. Engineering asks for context. Someone checks logs. Someone checks the latest deploy. The team searches GitHub. Slack fills up with partial updates. Then someone still has to explain what happened to the customer. @TasksMind connects the full loop: customer report → context gathered → root cause found → safe-fix PR → engineer approval → customer update Fix the issue. Close the loop. Keep the customer.
Check Current Status