GitHub

Is GitHub down?

No problems detected

If you are having issues, please submit a report below.

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.

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

GitHub Outage Chart 12/03/2024 12:20

At the moment, we haven't detected any problems at GitHub. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

  1. Website Down (80%)

    Website Down (80%)

  2. Errors (20%)

    Errors (20%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

Loading map, please wait...
City Problem Type Report Time
United StatesMorgantown Website Down
BrazilRio Grande Website Down
MexicoAguascalientes Website Down
NepalKathmandu Website Down
ItalyRome Website Down
United StatesCary Website Down
Map Full Outage Map

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:

  • sergeybedritsky Sergey Bedritsky (@sergeybedritsky) reported

    @pomber @github @devinivy I am not 100% sure, but they have/had similar scheme - if I remember correct they were accepting issues/feature requests only from paid users/companies.

  • palewire Ben Welsh (@palewire) reported

    Lesson of 2020: Every minute spent frowning about my computer running slow is better spent rewriting my code to run in the cloud. I'm ready to bet GitHub Action has already had profound effects on data journalism automation. Let's get demonstration cases open source in 2021

  • mgoetzke Matthias Götzke (@mgoetzke) reported

    @pomber @github I would love that for certain projects. Potentially though a two tier system where non sponsors can keep track of issues anyway. It really depends on the friction incurred due to issue losses

  • dylanbarrell agile-accessibility (@dylanbarrell) reported

    We deployed a new axe beta server last night with the ability to sign up and sign in with Github and Google and broke our own sign up form 🤦 @dequesystems @dequelabs #fail #workingonit

  • ffFlammie Flammie Pirinen (@ffFlammie) reported

    things that I hate in modern programming languages with own package managers, eg rust: forced bundling of locked-in versions of libraries, a huge security problem that is self-inflicted and then "solved" by an army of bots scanning whole github for these locked in versions -_-;;;

  • htahir111 Hamza Tahir (@htahir111) reported

    @_changxu @github So looking at average stars per day is a better indicator than the sheer number of stars at any given time. However, your analysis regarding contributors, issues, and forks is definitely the strongest indicator overall!

  • DennyLindberg Denny Lindberg (@DennyLindberg) reported

    @rikarends What a massive pain... I checked the the obs-mac-virtualcam github page. There is an open issue with other users reporting that the virtual cam does not appear for them either in any other application. Seems reasonable the issue could be related to the OS version like you said?

  • SlvrEagle23 Buster "Silver Eagle" Neece (@SlvrEagle23) reported

    Lately there have been SO many issues in my GitHub asking questions about Ansible installations, which have long been an "unsupported" install method. In this case, "unsupported" means "only use this if you know enough to PR in the fixes to problems you find with it yourself".

  • palewire Ben Welsh (@palewire) reported

    Lesson of 2020: Every minute spend frowning about my computer running slow is better spent rewriting my code to run in the cloud. This is a hunch, but I'm ready to bet GitHub Action is already having profound effects on data journalism automation, and will have even more in 2021

  • typeoneerror Benjamin Borowski 👨‍🚒 (@typeoneerror) reported

    @aleattorium @pomber @github opening an issue is not a guarantee of support and, as FOSS contributors, we should have little expectation that free access is equivalent to support.

  • typeoneerror Benjamin Borowski 👨‍🚒 (@typeoneerror) reported

    @pomber @github I don't see anything wrong with paid support, but not allowing folks to file issues on public code isn't the way to scope support. If the repo is private, no problem.

  • bangjelkoski Bojan Angjelkoski (@bangjelkoski) reported

    @Atinux @github Its getting annoying to get so much notifications and emails. The way to go would be to have weekly reminder (or eventually a PR) that you can bump dependencies and in rare cases (security issue) it can also notify you daily.

  • donavon donavon "the {...❤️} guy" west (@donavon) reported

    @youyuxi @pomber @github It's your right as an OSS maintainer to prioritize bugs (and you may decide paying customer's bugs should come first) but why would you not accept a valid issue? 🤷 And give sponsors a button to "sponsor" an issue they didn't create, making a non-paying user's bug a priority.

  • RickStrahl Rick Strahl (@RickStrahl) reported

    @LindsayKubasik @ericlaw @limin_z Size is a big issue. Currently my full distribution is 18mb. It's small enough to do updates by re-installing. Adding runtime adds 4-5x in size. The resulting binary also can't be loaded from Github (as I do with my Choco/WinGet/Scoop distros).

  • philpalmieri Phil Palmieri (@philpalmieri) reported

    @pomber @github interesting... why not just more fine-grained control over things without specific 'why' ... ie: source, issues, projects can all be public/private regardless of the repo settings, and role based issues? reviewer, non-ic, ic, etc

  • Thetacron Thetacron (@Thetacron) reported

    @CamThePerson Github links seem broken.

  • cedriceberhardt Cédric Eberhardt 🦀 (@cedriceberhardt) reported

    @pomber @github I think blocking the Discussion tab behind a paywall or even having a kind of backlog/hidden state for issue would be a better solution. Blocking people to report issue is kind of weird to me, knowing the fact that there is rarely a whole team of testers behind the scene for OSS.

  • leandromatos Leandro Matos (@leandromatos) reported

    @Atinux @github I don't see any problems with that. Especially because dependencies with serious vulnerability problems sometimes appear, and this can cause numerous problems. 1/3

  • hawkinjs Josh Hawkins (@hawkinjs) reported

    @bebraw @pomber @github If I can’t see the issues or PRs without paying, I won’t use it, because open issues are part of how I pick between two otherwise similar projects

  • samwightt Sam Wight (@samwightt) reported

    @KareemAAbuzaid @pomber @github Maintainers deserve to be paid for their work. Replying to bug reports, reproducing them locally, and putting in the work to fix the problem is work.

  • asarturas Arturas Smorgun (@asarturas) reported

    @mpmlopes I have some terrible pending things in my to do list, so now occasionally I am successful at setting up enough stuff when I am productive in anticipation of procastination later. Like hosting website on github pages, so I do not need to rebuild myself. That said, my blog is dead.

  • aleattorium Jean Lucas ⚡️ [0.75x engineer] (@aleattorium) reported

    @typeoneerror @pomber @github Hmmm, not necessarily. You don't contribute by only opening issues and many issues are just support (which drains the development team of many OSS projects that have only voluntaries).

  • WorkingCopyApp Working Copy (@WorkingCopyApp) reported

    @qqqzdl I think you would get a better error message from GitHub if this was about your data quota. 🤔

  • CalumBoal Calum Boal (@CalumBoal) reported

    @belocal_0x Try googling the issue, or open a github issue

  • RoboKozo RoboKozo (@RoboKozo) reported

    @pomber @github Interesting idea - what if instead there was an easy way to filter issues created by sponsors? I think this might be a good compromise.

  • HydroLejo Lejo Flores, PhD (@HydroLejo) reported

    @xarray_dev community... when using open_dataset (or mfdataset) is there a corresponding flag to "drop_variables" that loads **only** specific variables? I did a quick search through issues on Github and didn't find anything.

  • _g0dmode Mitch (@_g0dmode) reported

    @3266miles @jeszicawii Unfortunatly not but that github issue I posted above is the exact same issue. It makes the post on your behalf in the UI dont think we can see the raw request it sends.

  • lotus_rules Raj Kamal (@lotus_rules) reported

    @pomber @github then all your issues will be created when people run into them in production, as everything else will not cross the paywall. i would not use such a project, let alone consider it "open source"

  • donavon donavon "the {...❤️} guy" west (@donavon) reported

    @youyuxi @pomber @github We're talking about 2 different things here: A bug's Severity and its Priority. It may not be your Priority to fix a bug based on 💰, but that doesn't change its Severity (i.e. it's still a bug).

  • abhas_rewcie RewCie 🚀🇮🇳 (@abhas_rewcie) reported

    @roshovani I use GitHub when needed. Most of the process are carried in the backend server. So I never needed to dig deeper into VCS... Tho I have *** installed too, but I never used it command line way either...