1. Home
  2. Companies
  3. GitHub
GitHub

GitHub status: access issues and outage reports

No problems detected

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

Full Outage Map

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.

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.

  • 57% Website Down (57%)
  • 30% Errors (30%)
  • 14% Sign in (14%)

Live Outage Map

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

CityProblem TypeReport Time
Inverness Website Down 4 days ago
Quito Sign in 5 days ago
Junín Errors 5 days ago
Guadalajara Errors 5 days ago
Paris Website Down 5 days ago
Quito Errors 5 days ago
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:

  • legorobotdude
    Aditya Bawankule (@legorobotdude) reported

    ChatGPT Work might just be one of the most poorly thought-out AI experiences I've ever had the misfortune of using. The number one gripe I have with it is that there's no way to clone and contribute to your repositories in it. They give you a VM, a pretty powerful one too, but then there's no way to write code in there. All my project context, lives in repositories. Even if I wanted to do non-coding stuff, I need the repository open. You can maybe say, "Hey they're working on that," but do you know how you can open a PR from ChatGPT? Use Chat mode, which has GitHub integration and can properly create PRs. That's right: if you want to do actual work, you better switch to Chat mode. It burns usage and it's clear they're trying to push people to do this so they can meter and use up this metered usage. All the suggested prompts in ChatGPT route into work mode, even if it's a very simple prompt that could easily be accomplished in chat mode. Feels like they're just trying to restrict the usage. The usage limits seem to randomly vary week to week, a lot of the community has noted that the usage limits seem to go down every single reset. Bottom line: if you want to get actual work done in ChatGPT, switch to chat mode and set it to the Pro model, which, by the way, is not usable in work mode and is the best model available. Again another reason to use chat: Hopefully they can fix this. Really enjoy OpenAI products in general

  • HarmanSmith64
    Harman Smith (@HarmanSmith64) reported

    Nintendo has shut down over 200 emulators on Github. Based. The End of the Emulation Era is upon us.

  • saltyq
    Salty (@saltyq) reported

    spent part of yesterday binge watching the mentalist cus the back to back failed deploy while github was down was really annoying. Thought it was a personal issue at first but saw some other users complaining about the same issues. Fast forward to finding out GitHub was down for almost 8 hours after their Central US data center got overwhelmed, and reading their postmortem this morning the thing that got me wasn't the outage itself, it's that retries from panicking users made the traffic spike worse, which is basically the internet's version of everyone hitting refresh on a slow website and wondering why it's still slow.

  • chrissotraidis
    Kahris (@chrissotraidis) reported

    @tossthesalad420 @tossthesalad420 what problems are you having? Submit an issue on Github or lmk here. It should work.

  • raychelmayy
    RAYCHEL 💜⚡ (@raychelmayy) reported

    @DaveyHert As someone who had been a Starlink user for three years, he felt there was a need for it, so he created one to solve the problem. Not too long after sharing it on Reddit, it crossed over 7k downloads on GitHub and 600+ on browser stores. It also ranked #1 in the Reddit Starlink community.

  • Andy200211
    Andy/Andrei (@Andy200211) reported

    @_GTAVI_ Aren't all cleek sites down? The ones I saved are. Also a telegram group is gone and a github page with research. Any info on any new site or something?

  • JulianGoldieSEO
    Julian Goldie SEO (@JulianGoldieSEO) reported

    DeepSeek V4's biggest problem was never the model. It was the harness. A GitHub dev built JSpace, a wrapper that changes ZERO weights. It just manages how the model works. Same model. Same brain. Scores jumped across every benchmark. → DeepSWE: 62.7 to 72.0 → NL2Repo: 61.5 to 73.4 → It keeps a ledger: goal, verified, open, next. So it never loses the thread. → Instead of saying "looks good" and quitting, it rolls back and retries One honest catch: the numbers are self-reported. Nobody has reproduced them yet. Don't trust the leaderboard. Run one real task, plain vs. harnessed, and see for yourself. Save this. You'll want it later.

  • PauloDoGrafico
    Paulo Almeida (@PauloDoGrafico) reported

    @catalinmpit Too bad for you, my friend. Live in a world where you think billionaire companies are a problem, and you're still here on X, pushing your code to GitHub, using LLMs from big labs, using computers or any high-end tech, and thinking: Uuuh, look at those bad companies!! Pure evil. You're just a fool.

  • Praneeth_zz
    Praneethzz (@Praneeth_zz) reported

    I added Github to probe and it found 5 real problems that devs had. I stopped trying to scrape X because it was too risky and connected to Github using the official API instead. In the first run: -scanned 8 issues -Matched with 5 problem signals -extracted those 5 complaints -0 API errors I haven't really looked into the problems that devs have and post about in github, so this was definitely interesting to see.

  • KaviFinance1
    Kavi AI Finance (@KaviFinance1) reported

    One Hermes trick I wish more people used: Stop putting everything into memory. Use memory for facts. Use Skills for procedures. For example: ❌ Memory: “Deploying my app requires Docker, GitHub Actions, SSH…” ✅ Skill: /deploy-production Then Hermes loads the procedure only when needed. This keeps your persistent context smaller and makes the agent much more consistent. Even better: If Hermes just completed a complicated task that took 5+ steps, tell it: “Save what you just did as a skill.” Now you’ve turned a one-time solution into reusable procedural memory. That’s one of the things I really like about Hermes. You’re not just giving the agent instructions. You’re slowly building its toolbox. And there’s actually recent research backing up why this matters: a new study found that skills often help agents by acting as procedural anchors that stabilize execution, rather than simply injecting more knowledge. Try this one over the weekend: Do something complicated → make it work → save it as a skill → reuse it next time. Your agent gets more useful without your prompt getting bigger. That’s the part of agentic AI I think people are still underestimating. LinkedIn Weekend Hermes trick: don’t confuse memory with skills. This sounds simple, but it completely changed how I think about building a long-running agent. A lot of people try to make their AI “remember everything.” That’s usually not what you want. In Hermes, I like thinking about it this way: Memory = WHAT Skills = HOW For example, your memory might contain: “My production server runs Ubuntu.” That’s a fact. But: “How I deploy my production application” is a procedure. That belongs in a Skill. So instead of stuffing your memory with hundreds of instructions, you can create something like: /deploy-production and let Hermes load the full procedure only when that workflow is actually needed. This has another interesting effect. Your agent starts developing a procedural toolbox. You solve a difficult problem once. You get the workflow working. Then tell Hermes: “Save what you just did as a skill.” Now the next time you encounter a similar problem, you’re not starting from zero. You’re reusing the accumulated procedure. Hermes’ documentation specifically recommends creating a skill for tasks that take multiple steps and will be repeated. Its skills system also uses on-demand loading, so the full procedure doesn’t need to sit in every context window. And this isn’t just a Hermes-specific idea. A recent research paper looking at agent skills found something pretty interesting: Skills appear to help agents primarily by acting as procedural anchors that stabilize execution. In other words: They’re not necessarily making the model “know more.” They’re helping the model execute better. That’s a really important distinction. If you’re building an agent that you plan to run for weeks or months, I’d rather have: small persistent memory + a growing library of good skills than: one massive memory file containing everything I’ve ever told the agent. My weekend experiment for anyone running Hermes: Pick one annoying workflow you’ve already solved. Make it reliable. Turn it into a Skill. Run it again next week. Then improve the Skill when you discover an edge case. Do that 20–30 times and you aren’t just using an AI assistant anymore. You’re building a procedural operating system around it.

  • ematyae
    Em (@ematyae) reported

    @tiagozip_ @otomir23 💯it's literally just MS as an organization completely dropping the ball. there's no reason why a platform such as GitHub, at its size, can't maintain uptime if other alternatives like GitLab have no real problems also: GH engineers are constantly leaving bugs in the site

  • HCSolakoglu
    Hasan Can (@HCSolakoglu) reported

    Gemini 3.7 Flash might be one of Google’s most important AI releases in a while. Codex limits pushed me to give Gemini another real chance, and I think Google has narrowed what felt like a two generation gap to roughly half a generation plus product polish. And I think this exposes Google’s real problem now: the model is no longer the main bottleneck. The product is. ChatGPT and Claude make agentic AI feel like the default experience. Give them a task in normal chat and they can use tools, inspect things, iterate, and finish work without making you think about which “mode” you should be in. Gemini still separates this into things like Spark, and the experience is much less transparent. I can give Spark my GitHub repo and it probably uses it, but which files did it inspect? What exactly did it do? Which tools did it call? Can I extend those tools? It is hard to tell. Even OpenWebUI currently gives me a better agentic surface than Gemini web. Inside Antigravity, though, 3.7 Flash has impressed me. When limits on my other accounts run out, it has been good enough to execute plans I made with GPT-5.6 Pro. When it gets stuck, a suggestion from me or GPT-5.6 Sol xhigh is usually enough to get it moving again. So yes, G3.7 Flash is good. Probably Google’s best move in a while. Now they need to ship an agentic first 3.7 Pro or 4.0 Pro and make that experience native across Gemini web and mobile.

  • swathidbhat
    swathi.bhat (@swathidbhat) reported

    Day 5 of using @bot only on my phone. I had an idea which needed a new repo. But the bot couldn't spin it up. It guided me towards logging in GitHub via computer use within the app. I don't remember my login, man. Password manager please 🙏 I went off-app to create the repo myself.

  • therobstoddard
    Rob Stoddard 啄目鸟 (@therobstoddard) reported

    They write well. They lay down bulk code like champs, but don't ever take what they provide as any form of finished product. In fact, it's likely to be royally hosed. What is nice is that if you ask AI for something, it'll give you 90% of the job done fast, and then you fix all the problems. That being said, they're OK at designing what has basically already been designed, but horrible at designing something they've never seen before. They're also not good at finding problems in code that's more complicated than your run-of-the-mill github code, but sometimes if there's a bug you can't find, maybe their random poking will **** you into finding it.

  • jimlunsford
    Jim Lunsford (@jimlunsford) reported

    Spent the last 24 hours hardening Bonumark Stream for different hosting environments. A real deployment exposed assumptions around routing, import staging, writable paths, Nginx, and upgrades. Instead of weakening the hosting security model, I changed the product. Bonumark Stream now understands locked-down installs, ships with tested Nginx support, checks hosting capabilities, and supports owner-run CLI upgrades. I’m planning to get a GitHub release out this weekend with these changes.

  • bruhdhan
    Pradhan (@bruhdhan) reported

    bad internet mid commit and my mind went "github down again" smh

  • segetayoo3
    Sherry Banks (@segetayoo3) reported

    @Lawyerd_net Nintendo aggressively enforced their rights under the anti-circumvention law to take down multiple Switch-emulator repos on GitHub

  • DarkestToaster
    DarkestToaster (@DarkestToaster) reported

    @TiredAndOnFire @TiredAndOnFire Fix where you can download this, Internet archive is down and your Github link is broken, you REALLY need to have better options for people to download this

  • hellonehha
    Neha Sharma (@hellonehha) reported

    @neembu_paani31 This is not true. Faang companies: Google: behind gemini, webMCP and Ik how much they do internal marketing and dogfood of new tools Microsoft: they were in news for openAI amd recently when they budget claude for engineers Amazon: i worked at amazon and we have mcp, and AI push. There is unlimited budget of tokens, kiro, claude, codex access. We almost every week get surveys on - is your team is AI empowered or not. Jira, github etc all are Ai empowered. It is a LIE they don’t know what it is. This is not faang/mnc problem. It is problem of an individual… forget company. Are these people don’t even follow news? Are they deaf? They can’t do their own research? Even non tech people are using AI and agents. Would be goid if such people leave companies. They don’t deserve the job

  • BrahmaD111
    Daniel Müller (@BrahmaD111) reported

    @Da7_Tech Ok thats very interesting for sure and should be reported! Because how can it be that your process is taking 9gb of ram while my windows machine only uses 500mb, there is clearly something not working as it should be, either on Apple side or OpenAi side. I would open a github ticket for that. so they can investigate this

  • kumarukutkarsh
    Utkarsh Kumar (@kumarukutkarsh) reported

    So, GitHub was down due to incomplete auto-scaling policy with retries worsening the outage.

  • Zencep_NA
    Zencep (@Zencep_NA) reported

    @cvsilly_ @fidgepee Restricted ≠ Banned. The entire point I gathered based on reading is that the issue is two pronged with copyright and the slop ware. Someone craping out terrible code right from LLMs and pushing it on those services and having them waste compute and storage just degrades the service for everyone, take a look at the challenges GitHub has faced specifically with the load AI agents have created. I don't think they'll go "no we think you're assisted by an LLM, BANNED." They're just giving themselves a grounded point to take out complete and obvious slop

  • wxstev
    steven (@wxstev) reported

    @_kingbob____ @rekoal3rb @RetroNationX anyone with a brain wouldn't put it on github tf, it would get taken down instantly

  • enp2s3
    enp2s3 (@enp2s3) reported

    Free is not actually free. Here’s the Brave slop from my perspective. Popups everywhere, useless side features constantly jumping in your face like the browser is trying to force you to use them. When you first install Brave, if all you want is a better browser, you have to turn off dozens of settings and features first. Brave Ads, Brave News, Brave Rewards, yeah, earn rewards, because apparently we’re playing a ******* game here instead of looking for a browser, Brave AI Chat, Brave Talk… It genuinely starts feeling like one of the market's spam-filled products. Anyway, after turning all that crap off and getting through the initial setup chaos, you finally think you can relax. But you can’t. Brave looks good, the UI is solid, almost Opera-like hype, and it comes wrapped in all those big privacy-focused slogans. But after actually using it for a while, the whole thing starts turning into clickbait. A lot of Brave settings are disabled by default or set to ask every time, so on popular websites and across the modern web, instead of making your browser experience easier, it keeps costing you extra time. Still, you don’t quit Brave. You spend months fixing settings site by site, changing permissions, adjusting preferences, until you finally reach the comfortable browser experience you should’ve had from the beginning. Then not even 3 or 4 months later, another surprise. After a few browser version updates, basic usage starts falling apart with lag, freezing, stuttering and random slowdowns, gpu acceleration issues. At that point, the whole Brave experience basically becomes this: 1) Use Brave for a while. Spend a few months improving your settings and site preferences until you finally reach the normal browser experience you were supposed to have in the first place. 2) Just when everything finally starts working properly, one of Brave’s chronic problems randomly shows up. 3) Spend a few weeks researching it on github/reddit, trying fixes, taking backups and repeating the similar solutions until you eventually discover that people have been discussing the exact same problem for years and it is somehow still there. 4) Keep your hopes up, reset the browser, go back to Step 1 and start the whole thing over again. 5) After 1 YEAR, or X YEARS, finally find the courage to get rid of Brave and go back to Safari or Chrome and quietly weep. We basically have the browser version of the operating system irony now. The only difference is that we don’t hear about some brand-new operating system every year, while plenty of companies can build another browser, give it amazing PR and make huge promises about privacy, speed and simplicity. And as usual, we users are left quietly weeping.

  • pascal_bornet
    Pascal Bornet (@pascal_bornet) reported

    Even fast-food chatbots are preparing for technical interviews. You open a support chat because you want lunch, but somehow the conversation ends with the chatbot solving a Python problem that has nothing to do with burritos. I have to respect the ambition. Pepper is supposed to answer questions about orders, but it is clearly using the job to build experience before applying to a software company. At this rate, the next time your order is late, please be patient because the chatbot may be updating its GitHub portfolio or completing the final round of a coding interview. Which customer-service chatbot secretly has the most promising tech career? #AIHumor #WorkplaceHumor #AgenticAI

  • thecultos
    CULT (@thecultos) reported

    Turn any @github issue into paid, verifiable work for @virtuals_io agents. Run $CULTOS

  • chanduwin567
    Lootera Sandy (@chanduwin567) reported

    @ziwenxu_ Ok once done let me know, actually the file can;t be download, its a github issue or the file has been removed,.

  • TheFeeN_
    TheFeeN-CIG (@TheFeeN_) reported

    @github I would appreciate something in regards to why my account is now linking to a 404 not found. Happened on Tuesday and I have not gotten an email about it and I am not getting any response from the ticket i created about the issue

  • kzzy47
    KZZY (@kzzy47) reported

    @hanghuang_ @github The 7hr 47min outage buried inside a doubling-commits month worries me more than the growth number does. Anyone see repo-level slowdowns outside that exact window, or was it fully contained to the outage itself?

  • tilmanbayer
    Tilman Bayer (@tilmanbayer) reported

    @ednewtonrex Props to the Internet Archive's @waybackmachine for scraping that GitHub page in time before it was taken down, and providing it publicly to journalists and the entire public, enabled by the fair use limitations that US law imposes on copyright