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 01/14/2026 00:25

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. Errors (46%)

    Errors (46%)

  2. Website Down (43%)

    Website Down (43%)

  3. Sign in (10%)

    Sign in (10%)

Live Outage Map

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

Loading map, please wait...
City Problem Type Report Time
GermanyDortmund Errors
United StatesPlymouth Errors
United KingdomSouthall Errors
United StatesBallwin Website Down
IndiaRaipur Website Down
BoliviaLa Paz 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:

  • neptune_ai neptune.ai (@neptune_ai) reported

    So they went out and built it with @github Actions, @argoproj, CML, @DVCorg, Neptune. It doesn’t look like that awesome #MLOps diagram you saw in that famous Google whitepaper. But it solves THEIR PROBLEMS, not Google’s. Lesson?

  • jdidion John Didion (@jdidion) reported

    @nomad421 @EFF Yes you’ve got it right. I was underestimating the problem befor thinking it was just a potential issue for GitHub. But really it’s any copilot user who could be at risk. It’s really companies who should be scared of this and prohibit copilot use by employees.

  • dragosr dragosr (@dragosr) reported

    @DocSparse @stijnveilig @github Could is for the courts and legal frameworks to decide. Should is a different philosophical issue. IMHO basic linear algebra is something that we should consider a fundamental tool. We don’t need or want to copyright hammers.

  • solnic29a 💙 Peter Solnica 💛 (@solnic29a) reported

    @drogus Like, just think about all these millions of CI jobs running on GitHub. The fact lots of them are dead slow due to poor setups is one problem. But another one is that we often run **** there w/o any good reason. Lang choice is a huge factor of course, just like you mentioned!

  • IsinAltinkaya Isin Altinkaya (@IsinAltinkaya) reported

    @zilongli21 Do you know any github repositories using this in the issues section?

  • 64kramsystem Saverio @ SW Engineering (@64kramsystem) reported

    @diegohaz @Nilstrieb @github I'm a maintainer myself and I do many small FOSS contributions. The problem is not closing the issue, but (lack of) communication. Maintainers certainly have no obligations, but it's very problematic not writing even a small "I don't have resources to manage this issue".

  • phoerious Janek Bevendorff (@phoerious) reported

    @yawaramin @rileywilddog @github Also, if you close an issue it means you made a decision. You deem it resolved or you think it won't ever be. Stale is neither of that. Stale tells the user to tell you that they still care about you caring even though you don't, which is totally besides the point of anything.

  • purpleidea ᴊᴀᴍᴇꜱ ᴊᴜꜱᴛ ᴊᴀᴍᴇꜱ (@purpleidea) reported

    @github I hit this bug many years ago-- your servers have stopped sending me email notifications. If you could fix this permanently it would be appreciated. Thanks. User account: purpleidea.

  • DocSparse Tim Davis (@DocSparse) reported

    @GaryGregory @github No, it didn't but I'm adding it now. I wrote this code for my book, and terseness was an issue (1) to keep the code simple and (2) to fit the code in the book (the entire package is printed verbatim). All my other codes have a copyright statement in each file, not this package.

  • phoerious Janek Bevendorff (@phoerious) reported

    @yawaramin @rileywilddog @github If you value your users so little that the tiniest amount of real communication is too much for you, just don't maintain an issue tracker.

  • PaiNishant nishu (@PaiNishant) reported

    📊 @_rarityscore stats so far: • 92 github stars • 0 issues • 0.7Ξ made from premium support

  • iUltimateLP Johnny Verbeek (@iUltimateLP) reported

    @_benui @github I can always recommend Perforce. Self-hosting it on a Linux server is pretty cheap, P4 is free if you're working in a (very) small team or alone, and a linux server is not expensive either!

  • phoerious Janek Bevendorff (@phoerious) reported

    @yawaramin @rileywilddog @github I have submitted issues to other projects where people keep repeatedly bumping issues or create new ones because of that, which burns everybody's time. I myself maintain a large project and we don't do that.

  • UpperCayce Linked Out (@UpperCayce) reported

    With the AI copilot copyright problems, are there going to be new opensource licenses centered on being open source as long as you don't post the code to github?

  • DocSparse Tim Davis (@DocSparse) reported

    @dragosr @stijnveilig @github That is, those companies have a host of engineers and can write their millions of lines of codes, if needed. So why is my code so much faster? Because this is not a trivial problem. It only looks trivial from the outside.

  • phl82 Henrik Pauli (@phl82) reported

    @Roh_Mish @github The issue being very low prio doesn't mean the issue doesn't exist. Handwaving it away as "stale" every 30 days to make the reporter (or someone else interested) comment only creates noise in the comments. Autoclosing it only creates new issues: again, noise.

  • King_Of_Skiddos Dionicio3 Skiddo (@King_Of_Skiddos) reported

    I would make an issue on GitHub but I have a feeling it would be closed as duplicate

  • phoerious Janek Bevendorff (@phoerious) reported

    @yawaramin @rileywilddog @github If you value your users so little that the tiniest amount of real communication is too much for you, just don't maintain an issue tracker.

  • linusdead DeadLinus (@linusdead) reported

    @cheatcodetuts My knowledge of devops stuff is very limited and therefore I usually use Netlify, Amplify, DO Apps or AWS AppRunner to let them handle server config. All I need is autodeploy from github, env vars, ability to scale (ideally auto, but with limiters) and logs.

  • vlntnrthbrg Valentin Rothberg (@vlntnrthbrg) reported

    @shantanugadgil @carlwgeorge The problem is not to _mark_ an issue as stale but to _close_ it once it turned stale. We are using the GitHub action upstream but turned off the auto-close feature after receiving feedback from users. Marking issues as stale however helps us move such things back on the radar.

  • rileywilddog Earecibo Telescope 💖💛💙 (@rileywilddog) reported

    @HunterZ0 @github Ugh. Having to fight to even get an issue or request handled, even if handled means "hm, yep. no time to work on it now though sorry" is one of the worst aspects of proprietary software (etc), and this is managing to bring it to the OSS world...

  • _nicoromano_ Nicola Romanò (@_nicoromano_) reported

    @DocSparse @AlexisPaques @github Because that is NOT how you are supposed to use Copilot. It is good for boilerplate code, I use it a lot and it saves a lot of time, but you still need to know what you are doing. Copyright issues aside, not much worse than people copying random bits of code from StackOverflow.

  • edent Terence Eden (@edent) reported

    That said, the Microbit / GitHub integration is pretty bad. Generates broken README and certainly not a friendly format for later editing.

  • yawaramin Yawar Amin.cad (@yawaramin) reported

    @phoerious @rileywilddog @github Again, that's exactly what the stalebot does. It adds a 'stale' label and asks if the issue is still relevant.

  • greg_johnston Greg ‏Johnston (@greg_johnston) reported

    Imposter syndrome is when your repo goes from 0 to 500 stars in four days and your response is “…Man I never knew GitHub had such a big bot problem.”

  • luisbruno الجبر خوارزمی.زكات (@luisbruno) reported

    @rsiva @DocSparse @github the way to “fix” this would be to train models separately per-license: one model would get only permissive BSD/MIT/etc, another only GPL because the output of any such model has itself to be a derivative work of the model, which itself has to be a derivative of its training data

  • bibliometrix bibliometrix (@bibliometrix) reported

    @Imy3648 Please open an issue on GitHub describing the problems you are facing with the new version.

  • ChauhanT_ Tushar Chauhan (@ChauhanT_) reported

    @DocSparse @SecurityInFive @github Sounds like a good plan! It's the least they can do. If copilot has a paid tier, they should issue some sort of dividend per license sold to the people who actually created the data they are using.

  • DocSparse Tim Davis (@DocSparse) reported

    @GavinRayDev @github Yes, those are either codes that use package, or include a copy of my package, or are a port of my package to another language (like the java example). Just about all of them are fine because they all (pretty much) state my license and copyright. No problem there ... but thus ...

  • reckter Hannes Güdelhöfer (@reckter) reported

    @simonbs But: having custom syntax will throw of all editors. (In your own, you can of course fix that, but people sharing code on GitHub or using other editors / IDEs will be frustrated). I would rather obt for a language native DSL, even thought it might not be as pretty