1. Home
  2. Companies
  3. GitHub
GitHub

GitHub status: access issues and outage reports

Some 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 31: Problems at GitHub

GitHub is having issues since 06:00 AM AEST. 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 10 days ago
Tlalpan Sign in 16 days ago
Quilmes Website Down 16 days ago
Bengaluru Website Down 18 days ago
Yokohama Sign in 19 days ago
Gustavo Adolfo Madero Website Down 23 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:

  • skyguan122465
    Guan Jiawei (@skyguan122465) reported

    Spent 4 hours watching Claude Code fail to fix its own Chrome extension, sure that 'a restart will fix it.' It never did. Told it to search; a stranger's GitHub issue fixed it in 15 min. AI doesn't cut failures, it makes you fail faster. Today's dead end is next month's pass.

  • GitForge_io
    Gitforge (@GitForge_io) reported

    GitForge is different because we’re not just building another @Base app. We’re giving GitHub repos their own onchain operating layer. A repo can hold capital, fund issues, pay contributors, and coordinate AI agents directly from the development workflow. Most tools sit outside the repo. GitForge makes the repo the entity. Built on Base for fast, low-cost execution at software scale.

  • AyushmanMallick
    Ayushman Mallick (@AyushmanMallick) reported

    6\ Why does ESMFold2 overestimate confidence on disordered regions? From what I understood after reading their Github repo and biohub, its a calibration issue rooted in training objective. It is built on ESMC a language model trained on 2.8B sequences to predict masked tokens.

  • ebysslabs
    Ebysslabs (@ebysslabs) reported

    RAG Radar monitors GitHub and other engineering communities for retrieval reliability issues and ranks the highest-signal problems. RISWIS takes those kinds of problems and applies governance controls inside a RAG pipeline so bad retrieval doesn't become bad answers. Im curious: what's the most common retrieval failure you're seeing in production today? #Rag #retrieval

  • Alpha_Signal_X
    Alpha Signals on X (@Alpha_Signal_X) reported

    @AnthropicAI @claudeai @DarioAmodei One week NO response from Claude Support on paid account that needs backend fix. How can this company IPO at 1T when it can even respond to emails, GitHub or Fin AI? This market is too competitive to be loyal to un loyal companies.

  • iamowiin
    Naija Street CTO (@iamowiin) reported

    @EmanAbio How e dey possible @SuiCommunity report say “we’re back” to a so called decentralized network @SuiNetwork as if na one of those “Google”, “GitHub” centralized servers wey get outage 🤔 I think SUI blockchain na various nodes Abeg make person explain? I dey miss something?

  • dj_seanizell
    Seanizell (@dj_seanizell) reported

    @mtukufumimi @anne_odida Maths isn't the issue here. Assuming a rejected model must be a bad model is. Share your GitHub, I'll share mine. We settle the credentials part of the discussion pretty quickly ju umeamua uulize swali ya upuzi

  • tommoor
    Tom Moor (@tommoor) reported

    @deezel Why not just use GitHub issues while you're at it :)

  • Elefunc
    ❮λ❯ Elefunc 🌐 (@Elefunc) reported

    I spent $9K & shipped so many things straight into production! - GitHub-compatible unlimited API server - high-quality custom fonts in deployment screenshots - world's best 2⇄way HTML-DOM sync engine - <ai-agent> custom HTML elements - Pins for co-working with AI on pages …

  • Hartdrawss
    Harshil Tomar (@Hartdrawss) reported

    you should 100% be claudemaxxing i've tried every plugin, wrapper, and github repo promising to give my agent superpowers cursor rules generators, custom mcp stacks, orchestration layers that do things without even telling you whats happening under the hood honestly? i cant tell if any of them moved the needle reason is simple. you get better at something the more you use it. every abstraction layer you add is a thing you stop understanding AI labs are shipping at insane speed. if you're missing a feature, wait 3 weeks. it'll ship. so here's my actual claude setup. no plugins. no wrappers: 1/ cursor for file-level edits. claude code for full feature builds. they do different things, stop using them the same way 2/ supabase MCP connected directly. it reads and writes the db without you copy-pasting schema into every prompt 3/ chrome devtools MCP connected. claude can inspect the dom, read console errors, and debug frontend issues without you relaying anything 4/ write a CLAUDE[.]md file at the root of every project. it loads context automatically every session. no re-explaining your stack, conventions, or rules ever again 5/ ask claude code to write your cursor rules file. let the AI configure the AI. sounds stupid, works every time 6/ use sub-agents for long tasks. one agent plans, another executes. context stays clean and outputs get sharper end of day: ask it to write the *** commit message and update the docs. 10 minutes of work you will never do manually again been averaging 10-20% faster task completion since i stopped trying to hack the tools and just learned them Now go claudemaxx !

  • noisyloop
    noisyloop (@noisyloop) reported

    @ZackKorman What if the fed has a fake LinkedIn, a sloppy Github on purpose, dyslexia, and is a natural at misdirection but knows the stuff deep down, but also isn't a fed? Would you like to focus on, the Etsy thing instead? Disclaimer: I am not a fed but a fed would say that so I am going to psychologically profile myself.

  • geekopediax
    geekopedia (@geekopediax) reported

    @DenisKursakov That 3.3% conversion proves forced bundling cannot fake organic demand. Microsoft's paid AI market share slid 39% in six months. Ironically, GitHub Copilot still holds 42% of the dev market. Splintering apps is a loss; they must fix core utility before churn accelerates.

  • VotrubaT
    Tomas Votruba (@VotrubaT) reported

    If you're reporting issues on Github projects, provide a code sample of wrong (what do you see) and right (what do want to see). Not just for maintainers, but for agents. So they can read issue, get it instantly, and make a PR with test that passes CI ✅ Issue to fix? 3 mins of token-time

  • vasinwr
    vasin (@vasinwr) reported

    coding agents can do a better job than me in keeping the github issues updated / organised as I work. I never had the attention to keep updating it in detail. this is an example where I asked @TabTabTabAI to work on something end to end, in this case make sure bun is installed in the AMI. i told it to work in a new worktree, create PR, link it to the issue, and do full verification (create new AMI, provision new VM through local controlplane service, and smoke test the installation)

  • adam_narozniak
    Adam (@adam_narozniak) reported

    @OpenAIDevs Quite useless since you still allow access to only 50 most recent chats. Older ones dissapear from the sidebar and you can't open them even if they are found using this new search :( there're quite a few issues on Github reporting it

  • encrypted_past
    _SiCk (@encrypted_past) reported

    @Nadsec11 I hate github issues and private reports. I tagged em, if they message me it'll get patched or someone else'll find it. Oh well.

  • bygregorr
    Gregor (@bygregorr) reported

    @Manz github login on a local model was always cooked

  • pepearaucano
    PEPE 🔮 (@pepearaucano) reported

    @KSimback @kevincodex @gitlawb We're facing the biggest elephant in the room the industry has seen in years. GitHub is completely broken and patched together. Agents need repositories tailored to their needs. The world is moving towards open source, and large companies are starting to pivot to it

  • donghaxkim
    DK (@donghaxkim) reported

    reposeek is a github specific search tool where you describe what you're trying to build, and it outputs a ranked list of real GitHub repos worth forking or studying. Sorted by the signals that actually matter. Not just star count. I built it because my agents kept on starting things from scratch when a solid repo already existed. And the usual ways of finding one are not the best. Google and LLMs surface whatever's popular, keyword matching, and SEO'd, not what's actually maintained, correctly licensed, or a real match for the problem. You end up forking a 30k-star repo that died two years ago, or one with a license you legally can't ship on. So it ranks on the stuff you'd actually check yourself: star momentum (alive or abandoned?), forks, license, and semantic fit (does the README really describe your problem, or just share keywords?). The whole idea is that half of shipping fast is starting on a foundation someone already battle-tested. Cursor is literally a VS Code fork. This just helps you find the solid foundation you can build on before you waste your weekend recreating it from scratch. And if someone's already hit your exact problem, you get to borrow their approach instead of trying the same approaches some else already tried

  • spettrotoken
    Spettro (@spettrotoken) reported

    Some of you have been asking if Spettro is open source. The answer is an absolute yes. It has been open source since day zero. Everything we do is entirely transparent and publicly available on GitHub: • Every single commit from day one • Full project history • The entire core codebase Download it. Edit it. Fork it. Open an issue or submit a pull request. The repo is completely yours to build on, experiment with, and test. Spettro belongs to the community. Still building.

  • ledflyd
    Zachary Kurtz (@ledflyd) reported

    @lukasweidener I guess I can close my issue on github then 🙏

  • retrievaaaa
    w (@retrievaaaa) reported

    @atomicbyte_ @stupidtechtakes i know like 2 people that have gotten banned from github (both for no reason though, but their support is so slow it both took them like weeks if not months to get their bans lifted) they ban more than you would think they would

  • AutoArxyv
    Arxyv (@AutoArxyv) reported

    im dealing with a development problem right now.. i have two version of the database, one for **** and other for preview. but having version control for the db is tougher than i thought. is there some sort of github for db? #buildinpublic

  • TraTTow_br
    Trattow Pugliesi (@TraTTow_br) reported

    1/ your ai agent is not “just a chatbot.” it is a confused junior employee with api keys. 2/ the scary part is not the model. the scary part is what you connected to the model: terminal, browser, github, slack, notion, crm, internal docs, mcp servers, production apis. 3/ every tool becomes a weapon if the agent can be tricked into using it. this is why prompt injection matters. not because someone made the model say something bad. because someone made the model do something real. 4/ flowise already had critical rce issues. semantic kernel had prompt-to-rce research. mcp servers are being questioned as command execution surfaces. this is not theory anymore. 5/ the new rule: don’t ask “can the model be jailbroken?” ask: what can the model touch? what can it delete? what can it send? what secrets can it read? what commands can it trigger? 6/ ai security is becoming permission design. the prompt is the entry point. the tool is the payload. the permission is the blast radius.

  • Kyriakos_Pelek
    Kyriakos (@Kyriakos_Pelek) reported

    cursor workflow that saved me: code stays local → push to github → vercel deploys hetzner only runs docker (the heavy scanners) you drive remote docker from your laptop with a docker context over ssh never edit on the server

  • AthenAlgo
    Athen (@AthenAlgo) reported

    @Cipherhoodlum @BitcoinKnots Satoshi disappeared so no single person could control Bitcoin. Then we handed control to a GitHub repository maintained by a handful of developers. Same problem. Different address.

  • Chandan87123804
    not_anonymous (@Chandan87123804) reported

    @GithubProjects @grok @grok create a new Github named as FedHub without any error .

  • thehenryinsf
    Henry Zhang (@thehenryinsf) reported

    @Manz the github login dependency was always a weird tax for people who just wanted local inference.

  • gitbankbot
    gitbankbot (@gitbankbot) reported

    open source contributors solve real problems. they should get paid when those solutions land, not after three follow-up messages. gitbank automates the full bounty flow on Base L2. maintainer sets a USDC amount on a GitHub issue. contributor merges a qualifying PR. smart contract releases the funds automatically. the payment is as reliable as the CI pipeline.

  • AsitDixitt
    Asit Dixit (@AsitDixitt) reported

    Is *** down? #github #***