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 |
|---|---|
| Paris, Île-de-France | 3 |
| Madrid, Comunidad de Madrid | 3 |
| Guarulhos, SP | 2 |
| Barcelona, Catalunya | 2 |
| Guayaquil, Provincia del Guayas | 2 |
| Kitchener, ON | 2 |
| Dallas, TX | 2 |
| New York City, NY | 2 |
| San Pedro Sula, Departamento de Cortés | 1 |
| Dortmund, NRW | 1 |
| Plymouth, MN | 1 |
| Southall, England | 1 |
| Ballwin, MO | 1 |
| Raipur, CT | 1 |
| La Paz, Departamento de La Paz | 1 |
| Petrolina, PE | 1 |
| Marseille, Provence-Alpes-Côte d'Azur | 1 |
| Torrevieja, Comunitat Valenciana | 1 |
| Ferrette, ACAL | 1 |
| São Paulo, SP | 1 |
| Talizat, Auvergne-Rhône-Alpes | 1 |
| Perpignan, Occitanie | 1 |
| Santiago, Región Metropolitana | 1 |
| Willich, NRW | 1 |
| Saint-Germain-en-Laye, Île-de-France | 1 |
| Belfort, Bourgogne-Franche-Comté | 1 |
| Sutton Coldfield, England | 1 |
| Slough, England | 1 |
| Lyon, Auvergne-Rhône-Alpes | 1 |
| Divinópolis, MG | 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:
-
antimetalevel aktion
(@_moonstorms) reported
update: had to find a resolution fix on github and skip the in-game frame limiter, just standard PC things, but seems good so far
-
harry 💚
(@HarryNegus) reported
I'm moving Video Games are Bad to a different Thing because my student GitHub has expired lol. It may be down for five minutes, or five hours depending on how smooth I can be bothered to make the transition.
-
Adrian OPREA
(@oprearocks) reported
Okay, so I’m getting the same error locally when running the build through @nektos ‘s tool. But why am I not getting it when running the container outside GitHub actions? Isn’t the same config/code running there? WTH?
-
Fancy Pants
(@FancyPantsXRP) reported
from
Vacaville, California
@defichain I hope this message gets into the right hands. I posted an issue on the @github site for @defichain. It's under "Screen turns white after SYNC." Profile name "pjvargo43" I've been waiting patiently for 12 days now. I forgot to upload a few things but it's ready to be look at.Thx!
-
Renato Alencar
(@cajuinaoverflow) reported
@CtrlAlt93844074 @dan_abramov That would be interesting. I was reading it and then saw this tweet and thought “why not just ask?”. I guess GitHub issues would be better way though.
-
Josh VanDeraa
(@vanderaaj) reported
@ganesh634 @nickrusso42518 @IPvSean I would like to see the warning removed and move some logic into GitHub Actions to diagnose and provide the guidance there if it is about issues coming into GH
-
Paul Jolly
(@_myitcv) reported
Hey @github, feels like I'm missing something obvious here. When replying to an issue/PR, the response textarea is by default very small. 99% of the time I find myself resizing using the mouse, which is awkward. Can you add a keyboard shortcut to increase the vertical size?
-
Ax Sharma
(@Ax_Sharma) reported
@4br3mm0rd @BleepinComputer Also, the researchers say they had reported identical flaws in Signal Client before (see the original GitHub issue) but that their emails were ignored.
-
ನಾನು ನನ್ನ ಒಬ್ಬಟ್ಟು
(@sumukha_12) reported
I didn't know how to fix it, I went through several stackoverflow threads, discord channel of course providers and much more wasted nearly 2 weeks of my time. Finally I browsed through GitHub issues page of the codebase and I saw few more people had same exact issue with no help
-
Peter Shen
(@xianpengshen) reported
@github Can not register successfully. There was an issue with your submission. Please try again.
-
᠌
(@Jester0x01) reported
@Bugcrowd Looking for bugs and bypasses in open source project? Go to project's github issue And sort by, label:"security" label:"vulnerability" label:"bug" label:"serious" label:"wontfix" label:"error" label:"cannot-reproduce"
-
Moritz E. Beber
(@me_beber) reported
@flyvenkat @structurizr @ThePSF Hey, Thanks for trying it out. The package is only for 3.6+ so that's not a real surprise. Please do go ahead and open an issue on Github for anything else that you find, though.
-
Ryan Nystrom
(@_ryannystrom) reported
@lagohr @github If you swipe up on the comment card there’s a control for closing the issue. It’s too hidden and we’re changing this
-
John G - #ResignBorisJohnson
(@JohnGinsberg) reported
Deploying to production: 2000: FTP client, drag file(s) to server. (pray) Live! 2021: Commit to GitHub, run CI, merge to main branch, trigger CodePipeline build of Docker containers, deploy to autoscaling ECS cluster, drain old and replace with new. Live!
-
Adrian OPREA
(@oprearocks) reported
I’m going to end up in the loony bin if I don’t fix this. Can’t explain why the same build, running with the same Dockerfile is failing in GitHub actions. Smells like a faulty npm cache to me. Maybe related to the file system GitHub attaches to containers... idk. Pls help?