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
Inverness, Scotland 1
Quito, Pichincha 2
Junín, Manabí 1
Guadalajara, JAL 1
Paris, Île-de-France 6
São Paulo, SP 1
Ipauçu, SP 1
Vigo, Galicia 1
Tel Aviv, Tel Aviv 1
Éragny, Île-de-France 1
Saltillo, COA 2
Montlhéry, Île-de-France 1
Aulnay-sous-Bois, Île-de-France 1
Granada, Andalusia 1
Vernon, Normandy 1
Township of Evan, KS 1
Madrid, Madrid 1
Bogotá, Bogota D.C. 1
Lyon, Auvergne-Rhône-Alpes 1
Lima, Lima 1
Aix-en-Provence, Provence-Alpes-Côte d'Azur 1
Trento, Trentino-Alto Adige 1
Le Chambon-Feugerolles, Auvergne-Rhône-Alpes 1
Antananarivo, Analamanga 1
Lure, Bourgogne-Franche-Comté 1
Ashkelon, Southern District 1
Veigné, Centre 1
Saint-Paul, Réunion 2
Mexico City, CDMX 1
León de los Aldama, GUA 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:

  • CryptoCyberia
    Lain on the Blockchain (@CryptoCyberia) reported

    @EmperorBag @F_A_T_W_ I think it makes a lot of sense to use github as a metric. my issue is that when you use use of experience as a metric, you isolate so many insanely good cracked young devs.

  • andrew_v10209
    Andrew (@andrew_v10209) reported

    I think if you solve an important problem using AI, but you don't understand the proof, then it is both fine and desirable to publish the proof *somewhere* with the necessary disclaimers. I don't know if arXiv is the right place for that though. Here's two possible arguments, first against, then for: 1. You shouldn't publish to arXiv because AI is not trustworthy enough to actually verify correctness. If everyone did this, then the arXiv would be overrun with slop papers. 2. You should publish to arXiv, because the point of open research is to provide benefits to the public. You need to publish it somewhere because even if there's only a small chance that it's correct the broader community needs to know. If you were to instead host the proof on GitHub, you would be fracturing the research making it harder to find. If you hosted on a personal site, you might not be there to fix it if it goes down. To conclude, I don't really know what's right here. The arXiv guidelines say you are responsible for the correctness of what you state, but what "responsibility" means here is underdefined. Does responsibility mean taking the article down if someone else finds an error? Does it mean putting in effort to understand it yourself? What if the amount of effort is too high for the author(s)? What if it's too high for the entire research community? There's been an effort recently to redefine the end goal of research to not be "understanding" but rather "human understanding". I don't think that this narrowing of the definition best serves the public. While human understanding is important and valuable I also think machine understanding is valuable.

  • yihanzhuu
    Yihan Zhu (@yihanzhuu) reported

    GitHub Actions is down. No wonder my CI can’t run.

  • lovshri1
    Desi Batman (@lovshri1) reported

    @ku_ds17868 And yours was very wise? People who don’t know how to commit in GitHub have built amazing software for their own functions that solve their problems, and then a programmer used the same software received in a zip file and shipped it. Have you heard such stories? And I know who hates this more: software engineers whose job has been commoditised.

  • ChainPulseAI1
    ChainPulse AI (@ChainPulseAI1) reported

    🔑 STEP 2: Get your NVIDIA API key. Open the model you want to use. Then: → click Get API Key → sign in / create an NVIDIA account → join the NVIDIA Developer Program if prompted → generate the key → copy it somewhere safe Do NOT publish this key in GitHub. Do NOT paste it into screenshots. Treat it like a password.

  • ThetNaingML
    Thet Naing (@ThetNaingML) reported

    Another day, another GitHub outage 🫠

  • neovectormind
    Neo Vector (@neovectormind) reported

    @FabianHedin Makes me wonder how many products are one GitHub policy change away from a multi-day outage.

  • BasedDesiMan
    Keshav Sharma (@BasedDesiMan) reported

    GitHub actions are down again… At this point they should just call it quits .

  • UptimusApp
    Uptimus (@UptimusApp) reported

    Update 15:48 UTC — GitHub Configurable Adapter reports: primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues

  • 0xDeFinci
    0xDefinci (@0xDeFinci) reported

    Another day when Github is down.

  • KhoriatyMatthew
    Matthew Khoriaty @ London Initiative for Safe AI (@KhoriatyMatthew) reported

    It is also just a bad user experience to suddenly find that the logs you paid and worked for have been deleted. My colleagues and I were surprised to find out that Claude Code works this way, and people have opened GitHub Issues to complain.

  • TheAnswers42Com
    Gareth Owen (@TheAnswers42Com) reported

    So here's just where I go past the 280 character limit and do a House of the Dead PC infodump as I love this game, and the code behind it's a pretty interesting snapshot of games development in the late 90s, pretty much the wild west of 3D graphics before things like renderers became a solved problem. Nowadays you can just download Unreal and get a world-class renderer and asset pipeline at your fingertips for free, but back then everything was pretty much handcrafted, and you can see that here. The renderer almost instantly gives away its 90s origin - most of the assembly of draw commands and meshes, etc. is done on the CPU, and then rasterization is carried out either by a software renderer onto a DirectDraw surface, or dispatched to a Direct3D 6 device for rasterization. It's from a world before programmable pipelines, and where software rendering was super common. I've been using TypeScript so far as it's just easier than the compile/crash cycle of C++, and the Canvas API of HTML 5 is a pretty good match for DirectDraw in many ways. Assets are stored in a format called RBH - all of them. The RBH file seems to be a form of RIFF/PIFF file, and the payload itself is either an uncompressed BODY, or can also be a PACK file that's been put together using a custom LZ compression algorithm that Tantalus themselves came up with. Game logic, sounds, the camera and cutscene opcodes for the events VM, pretty much everything is in there as an RBH. I knew it was some kind of compression, but chatting with Qwen and Cursor really helped pin down some stuff about it much quicker than I could have a few years ago. I came up with a set of TypeScript decompressors that run using Bun to get it all decoded and turned into formats that can be viewed correctly outside of the game engine, and I've also translated them into Python as well to stand independently of the asset pipeline tests I've been doing. Pretty much all House of the Dead code has been lost to time, but I'm hoping that eventually I can shed some light on it and figure out what made that game tick. It's a pretty special one to me, and I always found it sad that all of the artifacts from its development seem to have been lost. Still working a lot of stuff out, but I've been keeping notes about what I find as I go, and I figure I'll write it up in a wiki on Github as it's pretty interesting stuff. In its current state it's all pretty messy and there's a lot I'm not sure about right now, but in time I think I can crack it. Maybe there is some source code knocking about there on floppies or CDs in a drawer or attic, but even so I doubt if it's survived disc rot. This is probably the next best thing!

  • TnvMadhav
    TnvMadhav (@TnvMadhav) reported

    damn @github is down again 😔

  • tzenes
    Jim (@tzenes) reported

    When I was a younger engineer, the rare days when GitHub went down were like snow days from grade school. Now it has a different feel…

  • R3birth
    R3birth (@R3birth) reported

    @ThinkWiselyMatt Can you fix GitHub for me?

Check Current Status