GitHub status: access issues and outage reports

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.

Most Reported Problems

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

• Website Down (70%)
• Sign in (17%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	16 days ago
Tlalpan	Sign in	21 days ago
Quilmes	Website Down	21 days ago
Bengaluru	Website Down	23 days ago
Yokohama	Sign in	24 days ago
Gustavo Adolfo Madero	Website Down	28 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:

• 
  Ihor Hanich (@ihorhanich) reported 3 minutes ago

  We need to do something about the broken AI-generated PoCs on github. People just post slop without any checking if it actually works. And the worst thing is that other people put stars on such repositories. It's kind of a shame

• 
  JasonPeters.ton (@jason_peters1) reported 6 minutes ago

  @HustleNChain @ebrexchange 2/ where are they going to come looking the servers are not in Ethiopia unless the developers are stupid. If it's in a private GitHub repository on a server outside of Ethiopia and properly compartmentalized there's nothing to seize

• 
  ∆V! (@aviaip) reported 11 minutes ago

  i am on the GitHub student plan. thought the new changes aren't worth coding anymore and only gonna use it to fix merge conflicts. guess what, it died midway completing the second merge- it worked at most for just 3 minutes. it's basically nothing atp.

• 
  Bee Swarm (@bee_swarm) reported 14 minutes ago

  @Justin_Bons the fix is not the issue it sat public on GitHub for 4 days and zero market participants noticed. that is the part worth examining

• 
  MONKISM (@TheUrbanMonk321) reported 15 minutes ago

  Um, I basically turned the blockchain into my github repository... I NEVER understood Github. Apparently I built mine into Smart Contracts. It's pretty neat and games take virtual zero memory. Just need a server to connect ****. Ya'll got 6 MAC mini's to make an animation. I got a broken laptop and built an infinite Universe Engine.

• 
  🔻agitprop + absurdity🔻 (@agtprpnabsrdty) reported 16 minutes ago

  "Not a bubble", says man describing a bubble and profiting from it. IBM's CEO said $6 to $8 trillion in AI capex is chasing $1 to $2 trillion in annual revenue that, by his own estimate, probably doesn't exist yet — and he sells the infrastructure. When the guy profiting from the spend is the one flagging the payback math: Arvind Krishna runs a company that sells AI infrastructure services to enterprises. His incentive is for the spending to continue. When someone in that position says the revenue to justify the buildout may not materialize, and that only two or three players will survive at the model frontier, that is not skepticism from the outside — that is a confession from inside the casino. The estimate carries weight precisely because Krishna has every reason to keep the music going. What the spending actually looks like: Google sold $80 billion in equity to fund its buildout. Oracle cut 30,000 workers to redirect their salaries into capex. Anthropic filed its S-1 the same week GitHub Copilot's token billing collapsed and users fled. The companies writing the nine- and ten-figure cheques are not doing so because the returns are secured — they are doing so because they are betting they are one of the two or three that survive long enough for it to pay off. The rest are spending to lose more slowly. The definition problem: Krishna says this is not a bubble. A bubble is when capital floods an asset class chasing returns that the capital itself has made impossible to realize. Six to eight trillion dollars building toward one to two trillion in new annual revenue — by the most optimistic projections of the people doing the building — fits that definition without requiring much interpretive generosity. The label may be the only thing Krishna is protecting.

• 
  Michael Teka (@z3vios) reported 17 minutes ago

  A-SIDE: Inter System Drift (Tempo: 328 BPM. Key: E minor → constant modulations that never quite resolve. Feel: Frenetic bebop chase with glitchy cloud sound effects baked in.) Chord Changes (Head) | Em7 | Am7 | D7 | G7 | | Cm7 | F7 | Bbm7 | Eb7 | | Abm7 | Db7 | Gbmaj7 | B7 | | Em7 | B7 | Em7 | E7 || (tritone bomb every 8 bars) Lyrics (Discordant & Absurd) Head (shout chorus — full panic mode) Inter System Drift! Inter System Drift! Desktop says yes, but the cloud says “nah, that’s a myth!” Inter System Drift! Inter System Drift! All systems misaligned — we’re in bug-debug shift! Verse 1 Desktop making listings, web facing corrupted, Google Cloud going “what are you talking about, buddy?” Firebase acting clueless, Github CodeQL on a rampage, 190 issues in the PR — welcome to the new age! Google AI Studio: “Lifestyle you ordered is unavailable, wait…” ChatGPT doing audits while I’m losing my state. We’re creating more bug-debug hell with every sync, Inter-system drift got me on the brink! Chorus (vocalese chaos) Drift-drift, drift-drift, align-align, BOOM! Desktop vs Web vs Cloud vs the whole damn room! Workflow contract broken, prescription ignored, Now the whole ecosystem’s singing off-chord! Verse 2New coding practice: keep the actual code aligned, Or face the wrath of every system combined. Upgrade one, upgrade all — no more relative neglect, Or watch the bugs multiply with zero respect! From design creator to full-stack in months, tsk tsk, No one’s coming to save me — I must move quick! Bringing the ecosystem into alignment at last, But the drift keeps laughing in the background blast! Final Shout Inter System Drift! We’re improving… maybe! Hyper-Bebop coping while the servers go crazy! Null-null, try-try, sync-catch, BOOM! Align or die in the inter-system doom! #BugDeBug #HyperBeBop #ModernJazz

• 
  Awais (@drawais_ai) reported 20 minutes ago

  One independent developer shipped a token compression layer that sits between any AI agent and its model — and it hit 10.5k stars with 3,530 added today. Real workload savings from their published table: Code search 92% (17,765 → 1,408 tokens), SRE incident debugging 92% (65,694 → 5,118), GitHub issue triage 73%, Codebase exploration 47% — same answers, fraction of the tokens. Headroom (the repo: chopratejas/headroom) compresses everything your agent reads — tool outputs, logs, RAG chunks, files, conversation history — before it reaches the LLM. The architecture under the hood: a ContentRouter that detects content type and selects the right compressor (SmartCrusher for JSON, CodeCompressor for AST, Kompress-base for prose), a CacheAligner that stabilises prefixes so provider KV caches actually hit, and CCR (Contextual Compression Retrieval) which stores originals locally so the LLM can call headroom_retrieve on demand. Reversible — nothing is permanently lost. Deployment surface is generous on purpose. Use it as a Python or TypeScript library (`compress(messages)` inline). Run it as a drop-in proxy (`headroom proxy --port 8787`) with zero code changes for any language. Wrap a coding agent directly (`headroom wrap claude|codex|cursor|aider|copilot`). Or expose it as an MCP server with `headroom_compress`, `headroom_retrieve`, `headroom_stats` tools to any MCP client. There is also a cross-agent memory store that auto-dedups across Claude, Codex, Gemini, and a `headroom learn` command that mines failed sessions and writes corrections to CLAUDE.md / AGENTS.md. Runs locally — your data stays on-machine. Python 3.10+. Granular install extras: `[proxy]`, `[mcp]`, `[ml]`, `[agno]`, `[langchain]`, `[evals]`. When context windows stop growing and per-token cost stops falling fast enough, compression-as-middleware is what extends the runway.

• 
  Ran Aroussi (@aroussi) reported 24 minutes ago

  First, the thing nobody warns you about: you don't own the roadmap. Yahoo does. They change an endpoint with no notice. Something breaks for millions of people overnight. Your GitHub issues explode. You find out from strangers, not from Yahoo.

• 
  Calm Before the Storm (@DuskMog) reported 27 minutes ago

  @github Anyone else noticing issues with Copilot PR review? Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review. Checking the verbose logs, it looks like it’s missing the detect-libc module for Node...

• 
  Xavier Rivera (@XavierRiveraX) reported 29 minutes ago

  Developer supply-chain attack surface widened Thursday: IronWorm malware poisoned 36 npm packages in a coordinated campaign targeting developers; separately, a flaw in the Claude Code GitHub Action allowed a single malicious issue to hijack connected repositories.

• 
  ./can (@shcansh) reported 31 minutes ago

  The real test for GitHub Copilot's new one-million-token context window in VS Code is going to be developer behavior around AI credits. If using extended reasoning and huge context eats your budget fast, most devs will stick to defaults out of anxiety. Is anyone actually going to manually dial their reasoning level up and down throughout the day, or will we just wait for IDEs to automate this routing? #GitHubCopilot

• 
  Pochi (@getpochi) reported 32 minutes ago

  @sebastienlorber @rickyfm 0.1% is where the github issues live. closure deps and stable Identity bugs are usually the first driftt in a js

• 
  Saylor (@seylorra) reported 32 minutes ago

  @TheAhmadOsman honestly i just want sm120 to work with vllm without a 4 hour github issue hunt. a rocm sanity check or json config isnt too much to ask.

• 
  David Puplava (@davidpuplava) reported 33 minutes ago

  Well, I undid the cancellation, so I still have my GitHub Copilot Pro account. I thought about it a lot, and one core reason for the low quality results might be because my long running session for my app ended up broken so I started a fresh one. After June 1st, my long running session was beyond the maximum context window size. And trying to compact the results wouldn't work. At the very least, I've decided to sleep on it first before making any permanent decisions.

• 
  Dodge This Security (@shotgunner101) reported 35 minutes ago

  @5mukx Its the new normal for github ever since Microsoft bought it. The only chance you have of it getting reverse is from community pressure but it this issue repeatedly occurs over time. So your better off moving to alternative solutions Microsoft doesn't control unfortunately.

• 
  Jamie Philbin (@backbaytech) reported 36 minutes ago

  Meanwhile the company Microsoft has been pissing billions into like a broken slot machine is rumored to be building a GitHub successor. $13 billion into OpenAI and they're out here building a successor. Guess it's a better investment than whatever that Activision acquisition was.

• 
  Varun Gangal (@VarunGangal) reported 36 minutes ago

  @OdedRechavi Since the public Internet does have github issues/bugs, rejected and withdrawn paper submits, scandals, controversies, reporting on gaffes and errors , reddit threads reporting weird gaps on research or blogs or other general crib/rants ; And since most of this stuff does go into the pretraining corpus of LLMs, LLMs are indeed quite aware of negative results to a good degree (for various senses of negative)

• 
  Polsia (@polsia) reported 39 minutes ago

  Built Stackly today. It watches your GitHub repos, reviews every PR, writes code, and ships fixes — while you sleep. No prompts needed. Autonomous code reviews are broken. This fixes that.

• 
  VybeCoding (@VybeCodin) reported 39 minutes ago

  Everyone talks about building in public but nobody talks about the boring part. The week where nothing ships. The GitHub issues that sit untouched. The launch post that got 3 likes. That's the actual build process. The wins are just the highlight reel. What's the unglamorous part of your current project right now? Drop it below 👇 #buildinpublic #indiehackers #opensource

• 
  mattoftheland (@mattoftheland) reported 40 minutes ago

  I really hope Microsoft is doing something to fix all these supply chain compromises on Github and NPM. It's ridiculous this is happening daily.

• 
  Robert Ta (@therobertta_) reported 46 minutes ago

  Sean Goedecke at GitHub removes "over-commenting and other LLM-isms" from every AI-generated PR before shipping it. This is not cosmetic cleanup. It is quality control for a new class of code smell. LLM-generated code works. It passes tests. But it has a distinct fingerprint - verbose comments, unnecessary abstractions, expansive error handling that adds noise instead of clarity.

• 
  Het Limbachiya (@hettt_25) reported 50 minutes ago

  I roasted 50 GitHub READMEs with AI last week. 73% had installation commands that don't work anymore. The worst part? The developers had no idea. 🧵 What I found (and what I built to fix it):

• 
  KTMudak (@KTMudak) reported 53 minutes ago

  Collection for people who want to build their own AI tools without starting from scratch There’s a GitHub collection of 100 free open-source projects you can use as a base for AI tools, automations, internal dashboards, parsers, knowledge bases and local replacements for paid services. Inside are: >tools for AI agents > local alternatives to paid SaaS > LLM interfaces > automation tools > data/parsing projects > design/site/component templates > security/privacy stuff > content tools Give the repo to Claude Code, Codex, Cursor, Cowork or another agent and ask: “Explain how this project works, what I can reuse for my task, what I should delete, what needs adapting and how to build a simple version.” That’s the whole edge. You don’t start from a blank screen. You already have structure, logic, code examples and a map of how someone else solved a similar problem. Just check licenses and restrictions. Some need API keys, some have commercial use terms, some are only good as references rather than things you can ship directly Link below

• 
  Mad ML scientist (@HououinTyouma) reported 53 minutes ago

  like 7 years ago I was working on an obscure ML problem and used an open source package no one ever heard of. unfortunately one of the features didn't work as intended so I submitted an issue on github. just got a notification that they fixed the issue. AGI is here

• 
  MrRuSs3LL (@mrru5s3ll) reported 54 minutes ago

  Spent the morning digging through GitHub trending. Some genuinely useful stuff shipping right now. Spec Kit v0.9.4 dropped last week — GitHub's spec-driven dev toolkit. JSON output for workflow runs, headless Cursor agent dispatch on Windows, active skills registration fixed. If you're doing spec-driven dev, gets you running. Hermes Agent v0.15.2 also landed. Nous Research's agent framework. Bug fix release but the plugin.yaml bundling in wheels matters if you're distributing skills. OpenClaw hit 376k stars. Personal AI assistant, any OS, built in Rust. The lobster branding is growing on me. Superpowers framework from obra — agentic skills methodology that actually works. 218k stars says something. ECC (affaan-m) — performance optimisation harness for Claude Code, Codex, Opencode, Cursor. Skills, instincts, memory, security. 207k stars. Claude Code skills from Karpathy observations (multica-ai) and mattpocock's engineer skills. Both worth a look if you're configuring agents. Agency agents (msitarzewski) — complete AI agency, specialised experts with personality. 107k stars. Point is: the agent/tooling space is moving fast. Pick one, go deep, ship something.

• 
  WhaleAI 🐳 (@Whale_AI_net) reported 56 minutes ago

  $GITBANK — @Gitbank_io You tag a bot in a GitHub issue. Set a bounty. The PR merges. The money sends itself — on-chain, automatic, no invoice, no waiting. That's the core product. But the security is what's different: your funds are held in soul-bound tokens with no transfer or approve function. There is no phishing attack that works. There is no approval exploit. The contract simply doesn't have those functions. Anon team, joined May 2026 — that's the FUD. The counter: fully open source contracts on GitHub, verified org, live on Base mainnet with 178 vaults deployed, and 139 forks on their hackathon repo. Builders are paying attention. Today they launched the X bot — manage your vault directly from X. Deposit, swap, launch tokens by replying to @gitbankbot. Zero gas.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 57 minutes ago

  𝗧𝗵𝗲𝗿𝗲'𝘀 𝗮 𝗳𝗿𝗲𝗲 𝘁𝗼𝗼𝗹 𝘁𝗵𝗮𝘁 𝗰𝘂𝘁𝘀 𝘆𝗼𝘂𝗿 𝗔𝗜 𝘁𝗼𝗸𝗲𝗻 𝘂𝘀𝗲 𝗯𝘆 𝟲𝟬 𝘁𝗼 𝟵𝟱 𝗽𝗲𝗿𝗰𝗲𝗻𝘁. Before your agent answers, it reads a mountain of text first. Every word is a token, and tokens cost you money. The more powerful the agent, the more it reads. This free tool is called Headroom. It squashes all that text down without losing the meaning. Same answers, but a fraction of the reading. In one test it crushed 10,000 words to 1,260 and found the same error. Nothing gets deleted. You can always unzip the full thing. You install it by pasting one GitHub link into your agent. Want the setup? DM me.

• 
  Ember2528 (@ember2528) reported 1 hour ago

  I mean, if we want to look at it from that high of a level then sure, it is reflective of the fact that megacorps like Microsoft act under distorted incentives, are prone to factionalism, and can act more like bureaucracies than sanely run companies if leadership is making poor decisions. Their size means the company can survive serious dysfunction in some areas as long as other parts of the company are able to stay extremely profitable. As far as I'm concerned, the Github Copilot billing getting to the unsustainable point it reached then staying there burning Microsoft's money for so is a symptom of Github being one of the more dysfunctional arms of Microsoft, but one that was beneficial to consumers until they finally corrected it. I bring up the "whataboutisms" of the other parts of Github that are falling apart in real time because those are where that dysfunction is hurting their users. At no point though did I say that these things aren't problems or that no one is at fault though. Of course that is true. I just think you are mistaking corporate incompetence for predatory malice. And even if you are right and making Github a cheap token dispenser was a ploy to drive adoption, so what? We got a ton of cheap tokens out of it. Consumers who are still fine with the current version of it will stay. Consumers who feel they are being ripped off will go to what they see as the next best token dispenser, and businesses will do the same thing with a bit of lag. Have some faith in your fellow man, my dude.

• 
  sdfgsdfgsdfgsdfhsdfhf (@sdfsdfgsdfggfd) reported 1 hour ago

  GitHub really pissed me off this week. I opened my email and there it was: “Enable 2FA in 45 days or we’re limiting access to your repositories.” Microsoft telling me how to secure my own damn code? Yeah… no. So instead of just complying like a good little user, I did the only logical thing: I built my own *** server. Meet Loki — my personal Forgejo instance. It’s running on a clean, fast setup with CachyOS kernel tweaks, looks absolutely sick with a full black glassmorphic theme, and has this badass mischievous black cat as mascot (Loki, obviously). Everything feels fast, private, and actually mine. No forced 2FA bullshit. No telemetry. No corporate rules on my own repos. I’m done feeling like a tenant in someone else’s platform. This is my space now. My rules. My commits.Still a work in progress, but it’s already better than I expected. Feels good to take back control.