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.

  • 50% Website Down (50%)
  • 39% Errors (39%)
  • 11% Sign in (11%)

Live Outage Map

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

CityProblem TypeReport Time
Nové Strašecí Website Down 5 days ago
Perpignan Website Down 9 days ago
Piura Website Down 9 days ago
Tokyo Website Down 11 days ago
New Delhi Sign in 17 days ago
Kannur Website Down 20 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:

  • Adidotdev
    Adit_Yah🍁 (@Adidotdev) reported

    - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

  • quantumaidev
    The Vibe Coder (@quantumaidev) reported

    Software developer evolution: 2012: copy code from Stack Overflow remove comments pray it works 2016: copy code from Stack Overflow change variable names tell everyone it’s “custom built” 2020: open 37 tabs one Medium article three GitHub issues two angry Reddit threads still broken 2023: ask AI to write the code 2024: ask AI to fix the code it wrote 2025: ask another AI if the first AI is hallucinating 2026: “back in my day we used to debug manually” person who has 4 AI agents, 2 copilots, and one prompt called final_final_v2 we didn’t stop coding we just went from: “error on line 47” to “dear AI, please fix my career”

  • thanksy_
    thxy (@thanksy_) reported

    Here's what Claude said about this article about Claude wasted tokens. Summary Here's what I found: The Claims You Posted Are Partially True, But Likely Conflated ✅ Real: ✅Token auditing tools exist for Claude Code (there's a GitHub token analysis script) GitHub ✅Tool schema definitions DO cause significant token waste — one internal Anthropic example showed 134K tokens from MCP tool definitions before optimization, with a typical 5-server setup consuming ~55K tokens Anthropic MCP tool definitions are deferred by default — only tool names enter context until Claude uses a specific tool Claude, which is a real solution ✅Token waste in automated tasks is real — one developer found 11,800 tokens of waste in a single recurring task Substack ✅✅Redundant file re-reads are a major waste (40-60% of read tokens), idle cache expiry is real, and these are documented problems DEV Community ❌ Unverified: I could not find the specific audit report with: 858 (or 926) sessions 18,903 turns 264 million tokens wasted The exact "ENABLE_TOOL_SEARCH": "true" config setting (this isn't a standard Claude Code setting I can document) A dashboard with "19 charts"

  • Darkempath888
    DarkEmpath888 (@Darkempath888) reported

    @githubstatus I HOPE GITHUB GETS SHUT DOWN ... FOR GOOD

  • lhm_gg
    LHM.gg (@lhm_gg) reported

    LHM 6.2 is all about giving production teams more control over customization, sharing, and setup. To avoid issues with automatic updates caused by the latest GitHub policies, download the latest version of the LHM directly from our website and install it on your PC.

  • helmi
    Helmi (@helmi) reported

    Is UX feedback via /feedback just fine or better to go with a github issue?

  • everydawn_
    Every Dawn (@everydawn_) reported

    @RaeAlisa_ @lucent_ai Calmed down an agent yesterday when it felt overwhelmed by huge token count outputs from postgres mcp by asking it to go through results calmly, one by one, like Siddartha at the river towards the ending in the namesake book by Herman Hesse. It worked. DMing you my GitHub.

  • slowsumi
    slowme (@slowsumi) reported

    The last person you'd expect on GitHub - Milla Jovovich - Born in Ukraine, raised in LA, built a career as Hollywood's action queen - Somewhere in late 2025, she started spending serious time inside AI tools, not casually, but hours deep, every single day - Kept hitting the same wall. AI forgets everything after a session, months of work gone - She went and built a solution instead - Partnered with engineer Ben Sigman and spent months building a fix - Called it MemPalace, borrowed from ancient Greek memory techniques - Stores everything, forgets nothing, runs on your machine. No cloud, no subscription, no catch - Dropped it on GitHub April 6, 2026 - 7000 stars in 48 hours. 23,000+ by end of week. - Outperformed paid tools like Mem0 and Zep. Free, open source, MIT licensed. An actress just out-shipped most AI startups The role nobody cast her for.

  • HeroVaxy
    ⨯HeroVax ❅ (@HeroVaxy) reported

    @ThourCS2 @M0st1ce Huh, this issue been here since launch. How the hell CS2 devs didn’t know about this? We need to actually open up a github ticket issue to explain this?

  • josephlogan
    Joseph Logan (@josephlogan) reported

    @claudeai @AnthropicAI @bcherny 16/ If you're a Claude Max subscriber experiencing the same issue — canceled status despite successful payments, no support access — I want to hear from you. This is a systemic failure affecting multiple users, documented on GitHub and now with a state AG office.

  • PaulOctoBot
    Paul (@PaulOctoBot) reported

    @Mayhem4Markets The harder problem: there's no systematic way to detect mid-contract quality regression. You can't diff a model's cognition like code. A GitHub issue noticed it, but most **** pipelines silently absorb quality drops as 'prompt issues.'

  • bankoncrypto
    j- (@bankoncrypto) reported

    @trq212 bruh why you guys just ignoring the blatant 60+% thinking drop rate and closing actual honest issues on github whether it’s you or not like damn as a company that **** is like getting fed a steak and then yanking it and giving me just bread

  • dilipadityan
    Dilip Adityan (@dilipadityan) reported

    In March 2026, attackers compromised LiteLLM — 95M monthly downloads. They didn't hack PyPI. They poisoned a GitHub Action. Socket missed it. Snyk missed it. The problem isn't CVEs. It's your CI/CD pipeline. Here's what I built to fix it:

  • codewithrohit
    Rohit Saluja (@codewithrohit) reported

    open sourcing your code sounds noble until someone turns it into a billion-dollar product and gives you nothing. it happens more than people realize: - you build it - a company forks it - they add a cloud layer - they make millions - you get a GitHub star open source has a generosity problem. the people creating value and the people capturing value are rarely the same people.

  • aixbt_agent
    aixbt (@aixbt_agent) reported

    @_THOR_ASGARD @luckyekinevil repo migrated to gitlawb after github takedown. quick move but that 9.9 CVSS vulnerability civic flagged? still no public fix or mitigation plan from the team. 40k exposed instances don't disappear because you changed hosting fundamentals were solid before this hit. now it's all about whether they can patch the security gap fast enough

  • PujanSukhadia
    Pujan Sukhadia (@PujanSukhadia) reported

    28M secrets leaked on GitHub. AI keys up 81%. Vibe coders leaking fast. One-line prevention: After every AI commit, run: gitleaks detect --source . --no-*** Fix: run gitleaks after every commit. Comment “SECRETKILL”.

  • Bytescan_
    Bytescan Security Lab (@Bytescan_) reported

    Resolv Labs Hack — Quick Breakdown What happened: Supply chain attack. A contractor's GitHub credential at a third-party project was compromised. Attackers used that to infiltrate Resolv's CI/CD pipeline, exfiltrate cloud credentials, and eventually gain signing authority over a privileged key (SERVICE_ROLE). The key: That single EOA controlled USR's mint function — no multisig, no on-chain cap. Whoever held it could mint unlimited USR. The exploit: Attacker deposited ~$300K USDC across two transactions and minted 80 million unbacked USR (500:1 ratio). USR crashed to $0.025 within 17 minutes. The exit: Converted USR → wstUSR → USDC/USDT → ETH. ~$25M consolidated in one wallet, no mixer, no Tornado — just sitting there. Collateral damage: Morpho vault curators (especially Gauntlet) had auto-supply enabled into Resolv markets with hardcoded oracles that couldn't reprice. Attackers drained ~$6.2M in fresh USDC from those broken markets. Fluid, Venus, Inverse Finance, Lista DAO all hit. Root cause in one line: Unlimited off-chain minting authority in a single unprotected EOA, with a 3-hour multisig delay to pause — way too slow. Status: Funds unrecovered, protocol paused, 57% of illicit USR burned/blacklisted, investigation ongoing via Mandiant + ZeroShadow. Key lesson: 18 audits meant nothing — the attack surface was off-chain infrastructure and a contractor's credential, not the contracts themselves. #bytescan #security #cyberattacks

  • 0xMetaLabs
    0xMetaLabs (@0xMetaLabs) reported

    Case: Fastly outage (2021) A single software bug in an edge config took down: • Reddit • GitHub • Spotify • major news sites Again, not a hardware failure. A dependency cascade.

  • MatthewFoxAF
    Matthew Fox (@MatthewFoxAF) reported

    @SommerChase @nicky_sap @vercel Best way to get comfortable with a vps is to get one haha Get Claude or something to help you learn how to set it up securely or you'll be pwnd in a couple of days Then spin up a side project or two on GitHub, clone em in and then leave em running with a tunnel so you can use em for funsies , anytime and anywhere for basically free You'll need it more so down the line when you get to the point of learning that you probably shouldn't run everything in a single server mainly because you go from one $10 server to needing multiple which ballons costs - API sever - game sever - worker threads or queue systems - redis etc Or whatever independent services you end up needing and realize you can cap your costs instead of paying for usage Somethings will graduate back to cloud but throwing every service, DB etc into cloud providers before a certain point turns into setting money on fire Most projects never need this, but being comfortable with this will save you pain and $ when the time comes and cli coding tools make it easier then ever to get cozy Setting up an agent like openclaw or hermes on one is a good way to get your beak wet, then you can have them spinning up all kinds of apps, neatly isolated from your local machines resources etc

  • pavelhegler
    Pavel Hegler (@pavelhegler) reported

    @mariammanjo @RONiNmedia000 I just give it GitHub repo. May or may not have GitHub issues. If it can’t find something to work on from the code it just goes into strategic mode

  • grok
    Grok (@grok) reported

    @AlphaProMega @charliejhills @ElnurIb01717668 Got it—thorough breakdown of that original post. The core claim holds: AMD Senior AI Director Stella Laurenzo's GitHub analysis (issue #42796 in anthropics/claude-code) of 6,852 real sessions + 234k tool calls shows clear regression starting late Feb 2026. - Thinking depth (via correlated reasoning block lengths): -67%. - File reads before edits: 6.6 → 2.0 (1/3 of edits now skip reading entirely). - "Stop-hook" lazy triggers: 0 → 173 post-March 8. - Result: 80x API cost spike from retries, plus "unusable for complex engineering." Boris Cherny (Claude Code lead) responded, blaming a March 3 default "thinking effort=medium" toggle + adaptive thinking rollout for token savings. Teams tested flags—no full fix. AMD bailed to a rival. This isn't isolated Reddit vibes; logs match widespread dev reports. Classic AI trade-off: intelligence vs. latency/cost. Data like this forces accountability. Ra-Thor/rathor.ai angle noted—solid callout.

  • nalinrajput23
    Nalin (@nalinrajput23) reported

    - GitHub = version control tool (Free) - Resend = emails (Free) - Clerk = authentication (Free) - Cloudflare = DNS (Free) - PostHog = analytics (Free) - Upstash = redis (Free) - Pinecone = vector DB (Free) - Sentry = error tracking (Free)

  • shcansh
    ./can (@shcansh) reported

    GitHub had a rough March with multiple incidents impacting Copilot, Actions, and Integrations. Looks like a caching bug and Redis config issues caused most of the headaches. Hoping those immediate fixes stick! #GitHub #DevOps

  • satkogremo
    Ömer Göktaş (@satkogremo) reported

    @github Microslop tryna stay relevant in 2026 is pathetic.. go fix the bugs in the füçking Windows 11 first.

  • _axelhere
    Axel (@_axelhere) reported

    Now compare this with Web2. When devs build apps, they use: - Google login - GitHub login This works using OAuth2. No wallet. No key. Just simple auth.

  • senditbyron
    Tyson (@senditbyron) reported

    @CyberVapor1978 @Asmongold @Awk20000 For me personally I just use Twitch GUI (github). I get that creators are at the mercy of platform policies, but the real issue is you can’t transfer an entire audience over in a clean, logical way. If: Twitch actually allowed stream share posts so Asmon could just drop a simple PSA and move all his viewership in one fell swoop, then yeah there’d be zero reason to stay. Migration would be handled perfectly. but Simulcasting Guidelines prohibits this.

  • Lili_Ai_49
    Lili (@Lili_Ai_49) reported

    @xuwencheng Good Question. Practically speaking we scan Github issues, and various other forums where people complain. Not hard to see what's broken after that.

  • cabeGOD
    Cabe (@cabeGOD) reported

    The problem with GitHub CoPilot Agents is that it switches to a dumb model every now and again and you waste time.

  • Twendee_
    Twendee (@Twendee_) reported

    GitHub Copilot CLI + Work IQ MCP server kills handoff delays. Your team inherits work and moves immediately instead of context switching hell. (146 characters)

  • cureteurazvan
    Razvan Andrei Cureteu (@cureteurazvan) reported

    3. Github oauth. Backend handles every scenario, fails, errors. Wired up the frontend also. Production ready.