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
Guarulhos, SP 2
Paris, Île-de-France 2
Barcelona, Catalunya 2
Vaughan, ON 1
Abingdon, MD 1
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
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:

  • tourcoder 代码旅行 (@tourcoder) reported

    Found a cool #GitHub feature, if add the issue link or id in commit, @GitHub will automatically associate the corresponding issue. If commit format is [fixed: #issueID], the issue will be closed. But [not fixed: #issueID] can also close the issue, this seems to be a problem.

  • marcgravell Marc Gravell (@marcgravell) reported

    @MrTurnerj @Chiser99 I guess I'm really looking for a supported API - looks like the GitHub issue (other tweet) is what I'm looking for.

  • AlexRob12252696 Alex Robinson (@AlexRob12252696) reported

    @linmobblog Haven’t looked in a while but Right to left input is a known issue. There is a patch you can add to make it work if you search around the flutter GitHub issues

  • whitingdev whitingdev 🏳️‍🌈 (@whitingdev) reported

    What problems do you truly need to solve to have a distributed web of contributors (e.g. github/radicle or twitter/mastodon?) So far I see: Single sign on Federated identity Search Web of trust recommendations Censorship (onion routing, new laws, blocklists, badbits) Ddos

  • LlESGREEDMISERY Ett mer ljus i himlen av en miljon stjärnor. (@LlESGREEDMISERY) reported

    @reduzio For For example I recently read about a MIDI issue, so I looked up for files that may be related. I found Alsa MIDI driver might be causing it based on the commit history, so I commented about it in the GitHub issue page.

  • Nick_Craver Nick Craver (@Nick_Craver) reported

    The Docker thing and the libraries I work on make me wondering the same thing: Could @github help better somehow with the "are you on the latest version?" when filing an issue. It's such a common first requested data and first response scenario. I wonder what we could do here...

  • Nick_Craver Nick Craver (@Nick_Craver) reported

    @vcsjones @github For example, choosing an older release from a drop down or something could provide a link to all issues fixed in newer versions…or some such. It could help users get info faster and take load off maintainers at the same time.

  • diapolo101 Diapolo10 (@diapolo101) reported

    Just managed to get Coveralls running with PyTest in GitHub Actions for the first time. Took me a few hours of trying, debugging and banging my head against the wall, but the end result was worth it. Found parts of the codebase I forgot to test, will fix that.

  • MrTurnerj James Turner (@MrTurnerj) reported

    @Nick_Craver @github Honestly a drop down that pulls versions from releases would be a good first start. Could then use that data to determine which version fixes what automatically.

  • DCuplink Alex E, Network Ogre (@DCuplink) reported

    Just discovered none of my commits have shown up even my private stuff because I wasn't using my github tied email. Whoops. Guess that's something I should fix?

  • blackbeard_ca . (@blackbeard_ca) reported

    @jeanjohn_music @Kylin_Network @pepeDgemhunter Not looking for a codebase. Just progress on dev tasks. Which there are several from Kylin on GitHub, but updates seem to have slowed down in the past few months. I’m a supporter of KYL and trying to dmor, but maybe I’m not as savvy as you, if you know a better way I’m all ears!

  • davidcelis david celis (@davidcelis) reported

    @olivierlacan @jacobrothstein @github PRs are implemented on top of issues, yes, but that toggle for org admins really does only work for issues themselves and not PRs

  • marsdeat Mx Andrew Marsden /məks.ˈændru.ˈmɑː(r)zdən/ (@marsdeat) reported

    I'm not looking forward to the idea of trawling through github issue postings, so does anyone know if there is community consensus on a Brackets fork yet?

  • MikolajKonarski Mikolaj Konarski (@MikolajKonarski) reported

    @alcides @stephenrkell I wasn't clear: the 5% doesn't include running the *** server. Communication is still by mailing zip files, scp to faculty server, or via projects on github, gitlab, etc. However, installing *** is just `sudo apt install ***` and creating ssh key is basic poweruser literacy.

  • nicolas09F9 Nicolás Álvarez (@nicolas09F9) reported

    @brcha @endrift @Helios748 People (or bots?) sending pull requests to open source projects replacing all code with a miner so that it gets run by the CI, has been a thing since before GitHub had a CI service built in. Removing free tiers will reduce this problem a lot but not 100% solve it.

Map Check Current Status