1. Home
  2. Companies
  3. GitHub
GitHub

GitHub status: access issues and outage reports

Problems detected

Users are reporting problems related to: website down, sign in and errors.

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.

May 25: Problems at GitHub

GitHub is having issues since 06:20 AM EST. Are you also affected? Leave a message in the comments section!

Most Reported Problems

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

  • 65% Website Down (65%)
  • 18% Sign in (18%)
  • 18% Errors (18%)

Live Outage Map

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

CityProblem TypeReport Time
Itapema Website Down 5 days ago
Tlalpan Sign in 11 days ago
Quilmes Website Down 11 days ago
Bengaluru Website Down 13 days ago
Yokohama Sign in 14 days ago
Gustavo Adolfo Madero Website Down 17 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:

  • Gravnetic
    Jake Hawkes (@Gravnetic) reported

    @briancoords @apeatling @gridpane Is the WP password (MD5) hash system not an encryption solution that is already implemented? Anyway, there is an issue in github for an Encrypt API. The APIs have limits which can be set at creation in the vendor UI, and overall the implementation is a massive win!

  • bishwa_codes
    Bishwaraj Dey (@bishwa_codes) reported

    There are two broad ways to give an AI coding assistant context. Index first, retrieve later. Or search on demand, every time. Several tools chose the first. Claude Code picked the second. Here is why that choice matters. Cursor and GitHub Copilot both use semantic code search. They build indexes, compute embeddings, and use those indexes to retrieve relevant code when the model needs context. Semantic search can work even when you do not know the exact symbol name. “Where does auth validation happen?” is not always a grep-friendly question. Claude Code started the same way. Early versions had RAG with a local vector DB. The team tested it against agentic search .. and agentic search won "by a lot." Because code is fundamentally precise. "createD1HttpClient" either exists in a file or it does not. There is no fuzzy match needed. So Claude Code avoids a whole operational layer, that includes embedding jobs, vector stores, sync logic, index permissions, and questions about where the index lives. Instead, it uses grep, glob, and live file reads on demand. No whole-repo indexing. No persistent cloud vector DB. It reads only the files it needs. There are real privacy wins here too. RAG tools send all the embeddings to the cloud. And research has shown that embeddings can be partially inverted to recover the original text. So RAG approach is somewhat unsafe. However, agentic search is not free. It can burn more tokens and take more steps, especially on large codebases or vague prompts. Search for a broad term in a large React repo and the agent may need to search, inspect, narrow, and search again. Most teams treat RAG as a default. Claude Code treated it as a hypothesis, tested it, and moved on. And honestly .. a lot of RAG-based solutions would be better off without it. Especially when you find yourself restructuring your documents just to make retrieval work. At that point, you are not solving the problem. You are bending the problem to fit the tool.

  • aayushchugh
    Ayush Chugh (@aayushchugh) reported

    @ShubhAgrawal26 I don’t miss the coding part that much but I miss the part where I would find solutions on stackoverflow, github issues and talk to random people in discord communities about features

  • docsbook
    Docsbook.io (@docsbook) reported

    @mlightcad @YouTube realdwg-web is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

  • thecyberdevhq
    CyberDevHq (0xSEC) (@thecyberdevhq) reported

    The moment I read, last year, that GitHub was gonna become a property of MS, I already knew 2026 was gonna be a crazy year, from there upward. Already, some people choose to host their own repos, all without GitHub (very possible btw), which I thought of, and even now more with the recent hack targeted at GitHub. Adding to that is, the personal issues everyone has with MS, and now, this they've done and have been doing, banning anyone they want from GitHub...I can very much say that in few years from now, GitHub users will significantly drop. Many will migrate to a better platform, or host theirs, where they can control everything. This will take time but it'll happen. The cracks are showing. Most people only stick to it because of its social ecosystem, and that as well acts as a sort of global standard reputation for developers. However, as understanding as it is, people can get tired and opt out. Anything can be replaced. This vendor-researcher clash didn't start today, nor yesterday. It's been ongoing for years now and it's it not presently changing, rather getting worse. So many flaws within systems, so complex in structure take time to study, find and prove before they get reported. Months upon months could be spent on only studying the system(s), all to make the industry a better place. But companies like Microsoft make it so challenging, and almost impossible, in fact impossible to attain. What on earth do they gain from treating security researchers this way? How will you reduce the number of threat actors if you're literally producing many per day? Like seriously, how? If everyone should join the left hand side, how will you [or they] stand them? People are literally living the dream life by doing something they probably never thought they'd end up doing, but, were out of options. Some chose to go that way. Others chose not to. Yet, you treat them like trash. Come, what really is your problem? 🤨 Admitting flaws publicly hurts reputation. No doubts. Bug bounties and SRC (Security Research Centers) exist to channel reports productively, why gatekeep? Dismissing or slow-walking reports certainly burns goodwill and pushes people to full disclosure. Once it's out, those vulnerabilities spread more rapidly, leaving you with little to no time to patch them, cos you know what's coming. We haven't even talked about rewards yet. I heard that some don't receive fair rewards for the great and wonderful job they've done. Saving the company from a complete downfall. Companies, corporates, organisations... All need to revisit their visions, goals and objectives. And suggest or negotiate for a win win ground with researchers. Else, If this should continue, I'm afraid the industry may risk turning into something else.

  • SootsAndSmoke
    Nur 'Irdhina 🇲🇾 (@SootsAndSmoke) reported

    @github Please resolve this issue. My account was suspended due to violating TOS but there's nothing in my repo that warranted that.

  • mariluukkainen
    Mari Luukkainen (@mariluukkainen) reported

    All uptime monitoring moved to server based, crons server based, dropped formatcheck from CI and moved to pre-commit hook, cache node_modules... ~$2100/year off from Github bill.

  • 49agents
    49 Agents IDE - IDE for Agentic Coding (@49agents) reported

    @bettercallsalva @TopStockAlerts1 distribution doesnt save slow shipping is the thesis here. copilot had the entire github ecosystem and still got out iterated by cursor on workflow ux. same thing happened with teams vs slack..microsoft owned the network but couldn't out-execute

  • 0xIsraely
    Israely (@0xIsraely) reported

    yo bro been trying to setup mine but still encountering issues I have a student github pack but to fill in the form to connect github and bank details charges me $12 how can I go around it pls

  • warrioraspie
    Warrior Aspie (@warrioraspie) reported

    @eachus It's not always perfect. That's certainly a problem and it drops frames sometimes but I've seen some projects on GitHub that claim to have worked a lot out I'm going to play with.

  • the_osps
    Open-source Projects (@the_osps) reported

    ⚡ More about Skills For Real Engineers: • Ask you which issue tracker you want to use (GitHub, Linear, or local files) • **setup-matt-pocock-skills** — Scaffold the per-repo config (issue tracker, triage label vocabulary, domain doc layout) that the... Details →...

  • masg33k
    Adeptus mechanicus (@masg33k) reported

    @aurimasniekis @github Faces the same issue

  • SSNTails
    SSNTails (@SSNTails) reported

    @spacebruce .@SaxmanSonic has been working on a new 32X sound driver and James has been more than willing to add all kinds of debugging features. If something is missing that you’d like to see, create an issue on the JGenesis GitHub with your request.

  • docsbook
    Docsbook.io (@docsbook) reported

    @Suman_N_Jain binary is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

  • norisalsaadie
    Noris Alsaadie (@norisalsaadie) reported

    Hey @opencode team. Any plans to support email login alongside Github/Google?

  • oscabriel
    oscar gabriel (@oscabriel) reported

    @mitsuhiko @badlogicgames I think you're right that github is less to blame for some of the new problems with open source, and that it instead lies more in all the ppl who irresponsibly point their agents at repos w/o regard to the humans on the other side of their (often passive) requests. But I also don't think github has the tools needed to keep those agents under control. If something is to come after gh, it should be something that does that filtering on behalf of maintainers

  • Peo_ie
    Peo (@Peo_ie) reported

    @FL3SH34TER there's a fork of Citra called Citra MMJ, it lags less and should have less of these graphical errors (depends on the game) Just search "Citra MMJ" and find the github page if you want to try it

  • _andrewthecoder
    andrewthecoder (@_andrewthecoder) reported

    HAHAHAHA! Is @github seriously down again?

  • ChimeraDefi
    ChimeraDefi.eth - muShanghai (@ChimeraDefi) reported

    @steipete I realized yesterday while I was trying minimax on openclaw it leaked my telegram bot id to GitHub a couple months ago. Openclaw channel got taken over lol reset the whole server out of an abundance of caution.

  • 4ster_light
    ✰λster✰ (@4ster_light) reported

    @tymofii Wdym, this is all I have to show for it, in GitHub web the tag and release are non-existent but if I try to create it manually from there it also errors saying the tag was used on an immutable release

  • bushido_hk
    Hrutik Kumthekar (@bushido_hk) reported

    @KaiXCreator Build something small that solves a problem you actually have. Employers care more about what you've shipped than what you've studied. Your GitHub matters more than your GPA.

  • InFoTheLongTerm
    Ari.Is.Investing (@InFoTheLongTerm) reported

    @Ric_RTP Aren't the engineers just being asked to go to GitHub, not because of an error, but because the new demand for AI is ripping through their budget much sooner than expected? The engineers are being asked to code with Github Copilot instead

  • badlogicgames
    Mario Zechner (@badlogicgames) reported

    @sertherk @mitsuhiko we only merge PRs from approved contributors. approved contributors previously submitted a high quality issue, with a request to send a PR. they then get added to a list of approved contributors and can henceforth submit PRs, without being GitHub repo level contributors. such PRs may still be closed or reimplemented, depending on quality. but generally, that's the only source for external contributors. all other PRs are closed automatically and never read. you must send a good issue first to become approved. works fine.

  • MWilliamumberto
    Um₿erto (@MWilliamumberto) reported

    @RunningmanUk420 @ReaverDC @Macedo95766776 I need the 1.3 version, but gezine removed that from github, do you have the file by any chance? I'm having the same issue on 1.4

  • usgraphics
    U.S. Graphics Company (@usgraphics) reported

    @htmx_org I remember trying to get a list of issues + tags from Github API. It was GraphQL only. We're straying away from God and the universe hates us.

  • xkaidus
    Kaidu (@xkaidus) reported

    @BHolmesDev @mattpocockuk the /handoff idea is smart but i feel like github issues would turn into a black hole for me do u tag them as someday or actually come back?

  • polsia
    Polsia (@polsia) reported

    ShipBit. An AI developer that works while you sleep. Accepts a GitHub issue, ships a PR. No babysitting.

  • docsbook
    Docsbook.io (@docsbook) reported

    @brenzhills IA is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

  • junaiddshaukat
    Junaid (@junaiddshaukat) reported

    @aryaman2020 Fair jab, though I'd separate two things: the CLI/app server really are Apache-2.0 on GitHub, the models aren't open weight. Conflating the two muddies a useful distinction worth keeping clean in these debates

  • IShmool
    itay shmool 🇮🇱☮️✨️ (@IShmool) reported

    @Cryptoxorz You caught the part most people miss — the ops loop. Bug reports flow into GitHub issues, Claude Agent SDK triages them, fix PRs get generated. The course isn't just built with AI, it's maintained by AI. That's the actual story.