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
Kitchener, ON 2
Madrid, Comunidad de Madrid 2
Dallas, TX 2
New York City, NY 2
Warsaw, Województwo Mazowieckie 1
Saint Andrews, Scotland 1
Sumaré, SP 1
Racine, WI 1
Guayaquil, Provincia del Guayas 1
Paris, Île-de-France 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
Nouméa, Province Sud 1
Los Angeles, CA 1
Marietta, GA 1
Miami, FL 1
Florence, SC 1
Halle (Saale), Saxony-Anhalt 1
Siegen, NRW 1
East Lansing, MI 1
Maricá, RJ 1
Bari, Puglia 1
Noida, UP 1
Victoria, BC 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:

  • gagliardi_vale Valentino Gagliardi (@gagliardi_vale) reported

    I create an unprivileged user on the same target machine, with disabled login: adduser deploy --disabled-login I authorized this user public key on the target user, let's call it app_user, which happens to be on the same machine. I store deploy id_rsa key in Github secrets.

  • edaqa Edaqa 😊 Mortoray (@edaqa) reported

    @cybwn @github There are workarounds of course, but it just doesn't make any sense. I want to attach a source sample directly to the issue. For now I copy and paste it inside the issue.

  • Ramperkash Hilgard Bell (@Ramperkash) reported

    Day 5 of #procjam #7dfps: Not much to show, I mostly did admin, but once I got time for work: * I discovered I was missing some old code from github * Tracked it down on bitbucket * Discovered some bugs in it * Spent ages fixing them Hopefully I'll have more to show tomorrow.

  • __exyi Stanislav Lukeš (@__exyi) reported

    @pomber @github Just close them if you don't like them. You can do that by API. IMHO it's terrible idea - there is a great value to well written bug reports and feedback. If your users are using issues for support, just send them away or ask for money, that's legit.

  • NicholasStrayer Nick Strayer (@NicholasStrayer) reported

    @camillevleonard @tladeras @github Number 2 causes way more problems than it should.

  • hadilq Hadi Lq (@hadilq) reported

    @pomber @github At least there could be an option for issuer to put some money for the PR that will solve that issue!

  • eamodio Eric Amodio (@eamodio) reported

    @rikki_js @pomber @github Yeah I like this, but built-in and also something that makes it clear that they aren't a sponsor and maybe should be. Like gentle nudges and reminders, e.g. when filing an issue, etc. Maybe also send email to non-sponsors if issue isn't responded to in a time period to sponsor?

  • hartez E.Z. Hart (@hartez) reported

    @ruiespinho @praeclarum We _are_ doing it for the users, that's the problem. There's an open GitHub discussion about removing that behavior.

  • mdziemann Mark Ziemann (@mdziemann) reported

    @RevDocGabriel Glad to hear that it's useful. GitHub issues would be best

  • S_2K Stephan Kämper (@S_2K) reported

    @pomber @github Also, in case a repo/its maintainer is receiving so many reports that they’re are burden, may be that is a hint at a problem with the repos content (some kind of quality issue) or the community of users/contributors. It might be that the number of issues is not the real problem.

  • S_2K Stephan Kämper (@S_2K) reported

    @pomber @github Bad idea. Software testing & bug reporting is 1 way to contribute to open source. While there are bad issue reports, the good ones are an investment of time/effort on the side of the reporter and that’s probably not paid. That is some form of sponsoring, too, just not monetary.

  • TheLX5 lx5 (@TheLX5) reported

    @HackerVilela MaxTile all the way. It seemed pretty much complete in the GitHub branch, except the overworld which was kinda broken lol

  • FluentCoding FluentCoding (@FluentCoding) reported

    @benawad Alright I tried it (with the Github login 2 thing) but it didn't work unfortunately. Is it only a problem for android users if I might ask or only for me cuz of whatever reason?

  • shahidcodes shahid (@shahidcodes) reported

    @pomber @github Bad, only production issues going to be created thus making the library or project not useful. Not sure that’s an OSS way.

  • phillipsj73 Jamie Phillips (@phillipsj73) reported

    @erikras @pomber @github Monetizing for who? That's part of the issue is that bigger businesses can monetize it without giving back. We are passing that burden to individuals without addressing that bigger issue. I feel it is a poor idea that will push people away.

Map Check Current Status