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
New Delhi, NCT 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:

  • pixelastic Tim Carry (@pixelastic) reported

    @theystolemynick @Kikobeats Thanks. Does it warn me somehow? With an email or github issue in case something is broken or is that just an enhanced UI view to compare screenshots?

  • jm_le_roux Jean-Marc Le Roux 🇪🇺 🇫🇷 🇨🇦 (@jm_le_roux) reported

    @FlohOfWoe @github Yes, but you also have to: - link the issue/PR together manually - close the issue manually when the PR merges All of that is automated by default in GitLab for MRs created with the "Create Merge Request" button on issues.

  • EMU_SDMS emuDevs (@EMU_SDMS) reported

    Just FYI: The EMU-webApp is currently not working. I have fixed the issue and am waiting 4 GitHub to update the gh-pages web page

  • superherointj superherointj (@superherointj) reported

    @gausby It is the only place I get to find people that know the answers. Either that or opening issues on GitHub. Other places do not concentrate high skilled people. And questions beyond the basics go unanswered. And then, Slack is suggested. Telegram groups is good for basics only.

  • Nanjizal_net Nanjizal (@Nanjizal_net) reported

    @trinichrys529 @HaxeFlixel Install linux! You can normally build all aspects of your haxe ecosystem from github, even re-compling haxe from ocaml, I suspect defender and trend micros are getting false positives. Not a fixel user, not had virus problems with any of haxe ecosystem although normally on mac.

  • liam_silk Liam Silk (@liam_silk) reported

    @jackdomleo7 Don't really use it, GitHub issues tend to give me more information these days.

  • jm_le_roux Jean-Marc Le Roux 🇪🇺 🇫🇷 🇨🇦 (@jm_le_roux) reported

    @FlohOfWoe @github It takes so much manual work and it's so error prone.

  • soh_satoh soh satoh (@soh_satoh) reported

    If you are still having issue with ReProvision Reborn, please open an issue on Github. I will not provide any support on Twitter.

  • andir0815 Andi (@andir0815) reported

    I don’t know what to make of someone emailing you after having opened a GitHub issue at the competition… Are you that desperate to get customers? Are you just meaning well because you created your product out of frustration with the other?!?

  • WarrenSeine Warren Seine ✰ (@WarrenSeine) reported

    @jm_le_roux @FlohOfWoe @github No, if you say Close #<id> in the commit, GitHub will close the issue on merge. But yes, it could be streamlined a bit considering how frequent this workflow is.

  • FlohOfWoe Andre Weissflog (@FlohOfWoe) reported

    @jm_le_roux @github Ah alright. In my projects, most PRs actually don't have an issue attached. I seem to remember that once an issue was "linked" to a PR by mentioning it in the PR discussion, then the issue got closed automatically when the PR was merged. I agree though, it's a bit obscure.

  • bjornritzl Björn Ritzl (@bjornritzl) reported

    @jm_le_roux @FlohOfWoe @github One thing I'd like to have is a UI option where you can create a branch and start a PR from a GitHub issue. This would automatically link the issue and pr and auto close on merge.

  • zoobab zoobab "NO Software Patents" (@zoobab) reported

    @adymitruk @jwildeboer Using a non-free platform to sign this letter, this is not a good sign in the "do what you preach". RMS would have objected at using Github in the first place.

  • Seburo13 Seburo (@Seburo13) reported

    @mhoye @github You were making the right kind of trouble...I think it is okay.

  • sknot213 ً (@sknot213) reported

    @ninja_muffin99 did you look at the dropped inputs thing? that might have contributed to some of the perceived difficulty (there is a pull request in the github that purposes to fix it but idk, maybe you already fixed in the private dev branch?)

Map Check Current Status