GitHub

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

Loading map, please wait...

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:

Less
More

github Hero Image

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.

Map Check Current Status

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Madrid, Comunidad de Madrid 4
Paris, Île-de-France 2
Barcelona, Catalunya 2
Guayaquil, Provincia del Guayas 2
Kitchener, ON 2
Dallas, TX 2
New York City, NY 2
Belfort, Bourgogne-Franche-Comté 1
Sutton Coldfield, England 1
Slough, England 1
Lyon, Auvergne-Rhône-Alpes 1
Divinópolis, MG 1
Granada, Andalucía 1
Cagayan de Oro, Northern Mindanao 1
Dhaka, Dhaka Division 1
Colorado Springs, CO 1
Baharampur, WB 1
Mexico City, CDMX 1
Santa Fe de la Vera Cruz, SF 1
Bogotá, Distrito Capital de Bogotá 1
Warsaw, Województwo Mazowieckie 1
Saint Andrews, Scotland 1
Sumaré, SP 1
Racine, WI 1
Manizales, Departamento de Caldas 1
San José, Provincia de San José 1
Fresno, CA 1
Cali, Departamento del Valle del Cauca 1
Caen, Normandie 1
Kuala Lumpur, KUL 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:

  • Throwaway8373 Arthur Rehktman.eth (@Throwaway8373) reported

    @vinibarbosabr @cburniske I am saying github stars isn't a relevant indicator for activity to begin with. A dead project can outperform nano on the chart just by losing marketcap faster than nano, without any activity. You are showcasing a metric completely reliant on nano doing terrible PA wise

  • MandoArtstudios MandoArtstudios (@MandoArtstudios) reported

    @TresieFourPaws @ItsVextrum I could, but nit right now. You can find it on Replicate: stable diffusion AI And the sign in with github

  • haraldcg Harald Greve (@haraldcg) reported

    @sitecorerick We're using the Constellation 4 Sitecore Redirects module. Planning Sitecore upgrade from 9.3 to 10.2. Are there any compatibility issues/breaking changes we should be aware of? There are references to OOTB Sitecore assemblies. GitHub source code uses 10.1 pkgs.

  • kkostov Konstantin 🌈 (@kkostov) reported

    Building a Vapor app into a Docker container requires so much memory and compute and it's slow - it takes almost 10 minutes on a "normal" GitHub agent. Does anyone have tips to speed up server-side Swift builds?

  • kranurag7 Kumar Anurag (@kranurag7) reported

    @alexellisuk I think it's more of a GitHub issue rather than arkade. Somehow, codespaces are not executing the arkade installation script.

  • edgeofsometime agatha 🏳️‍⚧️ (@edgeofsometime) reported

    just bc it was super annoying to find these, the private server program can be found by looking for grasscutters on github they rly did a good job not mentioning the game name amdbwkdbwkdbwkdbe

  • martin_costello Martin Costello 🏳️‍🌈🇪🇺 (@martin_costello) reported

    The button to edit a file inline in the @github web editor has been broken for days now 😭

  • _baxuz Ivan Čurić (@_baxuz) reported

    @0x0FFFFFFF @SignpostMarv @github What does it mean for the reporter to update the issue? If it's been reported and well documented, the only thing left for them is to spam "bump" every 29 days. One could use the same "solution" as the stale-bot and write a bot that will reply with "bump" every 29 days.

  • diegohaz Haz (@diegohaz) reported

    @Nilstrieb @github No OSS maintainer should feel ashamed for doing voluntary free work. Besides, many issues people open on OSS projects aren't bug reports. It's helpful to close feature requests and other types of issues that haven't had any engagement for a certain period.

  • meijer_s Stephan Meijer (@meijer_s) reported

    @technikhil314 @aahoogendoorn Another workflow or step in an existing one is up to the implementation. But yeah, I do run eslint (which includes a prettier conf) via github actions, and let it fail on every error. The error blocks the PR, so those changes can't land on main till they're fixed.

  • vinibarbosabr vinibarbosa Ӿ (@vinibarbosabr) reported

    @Throwaway8373 @cburniske Many projects have fallen as hard as nano in MCap (or even more). Along with GitHub activity. These projects, if their development continued active, could pass nano in the ranking I shared, but they didn't. It is meaningful. But if you can't see it, it's your problem, not mine.

  • Ivon852 Ivon Huang@ivon852@fosstodon.org (@Ivon852) reported

    I install privacy badger by IFF becuase of privacy concern... now my blog built using hugo is broken due to blocked github api and cdn js....looks like I should choose a simpler and efficient theme.

  • awakecoding Marc-André Moreau (@awakecoding) reported

    @Steve_MSFT @NoUselessTech @JFredBeck2 Is there a way to make Move-Item very verbose so it could tell what the error is with more details? It looks benign because just adding -Force works. It's trivial to reproduce in GitHub Actions, just Move-Item anything to a directory on C:\ (regular drive is D:\)

  • samdavidoff Sam Davidoff (@samdavidoff) reported

    @AskGatsbyJS is there a fix for the"Error: MDB_PROBLEM: Unexpected problem - txn should abort" error? I'm trying to post this as an issue in Github, but I can't reproduce this one error that has started appearing in all my old builds

  • _baxuz Ivan Čurić (@_baxuz) reported

    @0x0FFFFFFF @SignpostMarv @github What does it mean for the reporter to update the issue? If it's been reported and well documented, the only thing left for them is to spam "bump" every 29 days. One could use the same "solution" as the stale-bot and write the bot that will reply with "bump" every 29 days.

Map Check Current Status