1. Home
  2. Companies
  3. GitHub
  4. Outage Map
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
Check Current Status

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.

Most Affected Locations

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

Location Reports
West Lake Sammamish, WA 3
Parkersburg, WV 1
Perpignan, Occitanie 1
Piura, Piura 1
Tokyo, Tokyo 1
Brownsville, FL 1
New Delhi, NCT 1
Kannur, KL 1
Berlin, Berlin 1
Newark, NJ 1
Raszyn, Mazovia 1
Trichūr, KL 1
Departamento de Capital, MZ 1
Chão de Cevada, Faro 1
New York City, NY 1
León de los Aldama, GUA 1
Quito, Pichincha 1
Belfast, Northern Ireland 1
Guayaquil, Guayas 2
Irvington, NJ 1
Araçagi, PB 1
Siegburg, NRW 1
Teófilo Otoni, MG 1
Toronto, ON 1
Voiron, Auvergne-Rhône-Alpes 1
Cochin, KL 1
Surrey, BC 1
Montévrain, Île-de-France 1
Nantes, Pays de la Loire 1
Aubagne, Provence-Alpes-Côte d'Azur 1
Check Current Status

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:

  • tschak
    Thomas Cherryhomes (@tschak) reported

    There may/probably/most likely will be bugs. Please file reports on the Github issue tracker, on Discord or in the FujiNet subforum. Bluetooth / SIO2BT mode has been removed until we can implement a smaller BT stack in the firmware If you want to use SIO2BT, do not update.

  • TheE2D
    GodderE2D (@TheE2D) reported

    Ima just make a dropdown saying if you want to login with GitHub or Discord.

  • Toble_Miner
    Toble_Miner | tsys (@Toble_Miner) reported

    @Manawyrm @blocktrron For me it is definetly *** commits, lkml or github PRs/issues. Only getting their spam on those addresses.

  • ScottWGolby
    Scott Golby (@ScottWGolby) reported

    @lorenc_dan @github @tidelift Yeah “too small” is a massive problem, I’ve worked at multiple places where getting $100,000 was possible, but $100, hell no. One place had an in house data center - with no tools, no screwdrivers, no label maker - because it was too small. Productivity killing insanity.

  • OpenBSD_src
    OpenBSD src Changes (@OpenBSD_src) reported

    nicm@ modified usr.bin/tmux: Make pane-border-format a pane option, GitHub issue 2999.

  • christophetd
    Christophe (@christophetd) reported

    Sanity check. Is it right for GitHub to take down general-purpose offensive security tools that allows defenders to reproduce, and attackers to exploit the #Log4Shell vulnerability?

  • ClintRutkas
    Clint Rutkas (@ClintRutkas) reported

    @wgrimes84 I need the ext listed from the github issue. We have a decent list already (about 150). The tracker issue has Monaco supported file types but we don’t know the ext to map to for file explorer registration

  • julianopavel
    Juliano Brasil (@julianopavel) reported

    @BenLesh Maybe they are cleaning up the database. Just like maintainers deciding to clear 2 - 3 year-old GitHub issues because. Lack of bandwidth is a real thing.

  • kosalanuwan
    It's actually me (@kosalanuwan) reported

    @h_liyan @SlackHQ No I don't use Slack or Discord or any other for that matter. Prefer GitHub Discussions and Issues instead. Recently heard there an alternative for Slack called Threads. Never tried it tho.

  • christophetd
    Christophe (@christophetd) reported

    Sanity check. Is it right for GitHub to take down general-purpose offensive security tools that allows defenders to reproduce, and attackers to exploit the #Log4Shell vulnerability?

  • steffenhiller
    Steffen Hiller (@steffenhiller) reported

    Yesterday was a beautiful example of how GitHub Codespaces can save one's (Sun)day. Wanted to spend 1-2 hours on @building_rarely. Started the app locally & was greeted w/ a semi-cryptic error msg. Did some `brew` stuff, restarted machine. No dice. GitHub Codespaces just worked.

  • Moony_codes
    Poornima Alugubelly (@Moony_codes) reported

    @RushikeshTarap1 @poojasabnani93 @github Would be nice if you let people know about these sessions in the TT server 😢

  • billba
    Bill Barnes (@billba) reported

    @DynamicWebPaige @github Don’t you be dissing GHIFS (GitHub Issues File System)

  • hoe_node
    *** Nodes (@hoe_node) reported

    Issue with Vercel deploying our Github code...

  • The_Mainlander
    Kumo (@The_Mainlander) reported

    @TheCryptoDog Go to Nomics and remove the **** Tick data layer and see how sound it is. Off to GitHub check commits. Read the paper and say hi to the Community. Check LinkedIn and other Signals. Decide if it's got a good use case and solves problems or is it a Flipper. Check DEX/CEX options...

Check Current Status