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
Paris, Île-de-France 3
Madrid, Comunidad de Madrid 3
Barcelona, Catalunya 2
Guayaquil, Provincia del Guayas 2
Kitchener, ON 2
Dallas, TX 2
New York City, NY 2
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
Guarulhos, SP 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
Granada, Andalucía 1
Cagayan de Oro, Northern Mindanao 1
Dhaka, Dhaka Division 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:

  • ascherbaum Andreas Scherbaum (@ascherbaum) reported

    @alsargent However it's still InfluxDB v1.8, as 2.0 has no way to install it automatically. (you already pointed me to the open GitHub Issue)

  • _marcusherrmann Marcus Herrmann (@_marcusherrmann) reported

    @hdv A first easy one, "Are there GitHub issues related to a11y/WCAG on this particular project"? While their absense doesn't mean everything is fine, but their presence would be a warning sign.

  • cheshire137 Sarah Vessels (@cheshire137) reported

    @MaartjeME @github Lol I actually went down this same route, removing that left margin, before I realized the problem is showing the button at all -- you can't sponsor yourself! Could you look again, see if things look right now?

  • rahmon0v Jahongir Rahmonov (@rahmon0v) reported

    First, have a problem. You can’t solve a problem properly if you don’t experience it firsthand. GitHub wasn’t built for the developer community at large. 37Signals didn’t build Basecamp for a world full of project managers and consultants. They built it for themselves.

  • cycryptr Anthony Ronning (@cycryptr) reported

    @openoms @DreaminCrypto Yeah pretty much! Saw the github issue on running a 2nd LND alongside the main one, especially for the use of something like sphinx. That's the main reason I don't use my node w/ sphinx - not linking my node to my identity. So +1 on that.

  • sic2go Simone Ivan Conte (@sic2go) reported

    @natfriedman @muratdemirbas Why GitHub? There are other alternatives, they could even put up their own *** or mercurial server. Unfortunately, however, there is too much money going on in the game for such proposal to ever become reality

  • remram44 Rémi Rampin (joinmastodon.org) (@remram44) reported

    @pjs_228 @github If you can't stand looking at open issues, you can also disable the issue tracker entirely. At least the community will know to organize somewhere else. Package authors don't owe anyone anything, if they decide to take it on and spit in our faces that's something else though.

  • NickInformation Andreas Nick (@NickInformation) reported

    @tweet_alqamar directly on the server is probably a security risk. But the meta information about Winget on github is worth its weight in gold. Download paths and installation parameters. I use this information to automatically create #AppV and #MSIX packages. Customers use them on server

  • resistance_gowy クリボー (@resistance_gowy) reported

    github issue

  • grandazz Aaron Chambers (@grandazz) reported

    @kamal Do you use the Refined GitHub extension? If so, check your console. I bet you have an error. I had the same thing happen to me last night.

  • robertjandreu Robert-Jan de Dreu (@robertjandreu) reported

    @0xAkuKun @Girgias In this case the vulnerability was in the self-hosted *** server itself. Making it possible to push code impersonating someone else. Funding might have helped maintaining the *** server. But I think the move to GitHub is an okay solution. The bad code didn't get released.

  • benaryorg Katze (they/them) (@benaryorg) reported

    @0x0a_fox For starters I'd like to get rid of that nginx inline Lua that catches my GitHub webhook to cause a rebuild of something. Because that one is broken. Whoopsie. And all it's supposed to do is basically `rm`.

  • RogueWolfIII science worm🐛 (@RogueWolfIII) reported

    LRT is incredibly funny because each vaccine will have been patented, likely including the specific RNA sequences they're using because pharma is terrible, so just publishing those on GitHub for all to read is ****** excellent fkfkfjdhsh

  • Delta2315 Swastik Baranwal (@Delta2315) reported

    @LearningShakta @github @natfriedman Don't joke it is a serious issue 😑

  • shinohai2017 shinohai (@shinohai2017) reported

    @TartanLlama To be fair it makes more sense than some of the Github issues *I* get.

Map Check Current Status