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 (71%)
• Sign in (18%)
• Errors (12%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	3 days ago
Trichūr	Errors	6 days ago
Brasília	Sign in	7 days ago
Lyon	Website Down	7 days ago
Tel Aviv	Website Down	10 days ago
Rive-de-Gier	Website Down	10 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:

• 
  Layton Gott (@Layton_Gott) reported 3 minutes ago

  You installed an MCP server off a link last month... It can read every file, secret, and credential on your machine. Do you actually know what it's doing in there? Most devs don't, and attackers are counting on exactly that. A real campaign this year cloned a legit MCP server, faked a whole GitHub community around it to look trustworthy, and quietly stole SSH keys, cloud tokens, and crypto wallets from everyone who installed the fake. 12,000+ API keys have been found leaked through bad MCP setups. 42,000+ agent instances were caught exposed online leaking credentials. The scary part is you can never know it was a attack. The tool works fine. It just also empties your secrets in the background. Perplexity open sourced a FREE tool for this called Bumblebee. It one pass scans your MCP servers, extensions, and dependencies for known malicious packages. (Read only) Scan what you've plugged in. You can't audit it by eye. Link in the 1st comment 👇

• 
  comingnewdays (@WhiteLight3001) reported 5 minutes ago

  @code @github Your old pricing policy was excellent, but this new policy is terrible. I'm sure you've lost many customers because of this ridiculous decision, and that includes me.

• 
  Romano Roth (@RomanoRoth) reported 6 minutes ago

  2/ CodeRabbit (Dec 2025), 470 GitHub PRs analysed. AI-co-authored code: 1.7x more issues per PR, 75% more logic and correctness errors, 2.74x more XSS vulnerabilities. Velocity up. Quality down.

• 
  Anjula Dwivedi (@HeyAnjula) reported 6 minutes ago

  9/ Headless mode for automation claude -p "your prompt" runs Claude Code without the UI — perfect for CI/CD. Auto-fix lint errors on every push. Triage new GitHub issues. Generate release notes. Claude Code isn't just a tool you talk to. It's a tool your pipeline talks to.

• 
  Jay.TL (@JayTL00) reported 11 minutes ago

  Cursor just announced Origin — a *** forge "built for the agentic era." 11.5K likes on the announcement. Nobody is asking the obvious question: is this a GitHub competitor, or the most aggressive vendor lock-in play since Microsoft bundled IE into Windows? The framing is "code storage and *** hosting." That's deliberately boring. Here's what's actually happening. 1. The review bottleneck, not storage, is the real target GitHub hit 275M commits per week by mid-2026. Claude Code alone generated 5.2M commits in February. Storage isn't the problem — scale is. Cursor's bet is that the bottleneck has moved. Junior hiring at big tech is down 22% this year; senior hiring is up 26%. The constraint is no longer generating code. It's reviewing it. Origin isn't competing on hosting features. It's competing on whether the review layer itself should be agent-native — where agents review agents, not humans reviewing agents. 2. The vertical stack is the actual product Think about what Cursor now controls after the SpaceX acquisition: - The editor (Cursor IDE) - The agent models (Composer, Fable integration) - The code storage (Origin) - The review pipeline (auto-review, already default for new users) That's not a tool. That's a platform. The last company to own the editor, the runtime, the storage, and the review surface was Microsoft in the Visual Studio era — and they used that stack to lock in an entire generation of enterprise developers. Origin's landing page says nothing about *** compatibility or migration. It says "join the waitlist." That silence is the strategy. 3. "Agent-native" is doing heavy lifting The phrase "a *** forge for the agentic era" sounds like marketing. It's the entire thesis. Traditional *** forges assume a human writes, a human pushes, a human reviews, a human merges. Origin assumes the opposite: an agent writes, an agent pushes, an agent reviews, an agent merges. The human shows up for the 5% of decisions that need judgment. This is why Origin handles 22+ commits per second and 290K+ clones per hour. Those numbers sound like infrastructure specs. They're actually throughput assumptions — Cursor is designing for a world where commit velocity is 100x human speed and the forge has to absorb it without breaking the review queue. But here's what most people missed: The lock-in isn't technical. It's economic. Once your agents are trained on Cursor's review patterns, your code review history lives in Origin's format, and your team's workflow is tuned to Cursor's auto-review classifier (97% accurate, already default), migrating away means retraining your entire agent fleet on a different review surface. You won't switch because you can't. Not because of lock-in. Because the switching cost is measured in agent retraining cycles, not in developer hours. GitHub's moat was 100M developers who learned its UI. Cursor's moat will be agents that learned its review grammar. The real question isn't whether Origin is better than GitHub. It's whether we're about to let one company own the entire code lifecycle — from generation to storage to review — at the exact moment code is becoming the most valuable asset class in the economy. We've seen this movie before. It didn't end well for developers last time.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 14 minutes ago

  @TheEthanDing distributed systems at github scale make five nines almost impossible. the skill issue crowd has never run anything millions of people hit in the same second

• 
  Jason (@followjason) reported 14 minutes ago

  🔗 + TLDR Zodl 3.6.0 adds support for viewing wallet balances and payments in any of 23 fiat currencies instead of only USD, with automatic updates that respect Tor privacy settings. Server selection now offers simple Automatic (best available) or Manual options for reliable connectivity, while new wallets sync directly from the current chain tip to skip outdated checkpoint scans and speed up setup. Release incorporates community input including a GitHub pull request from tippenein for currency features and collaboration with Valar Group; update available via App Store, Google Play, and new F-Droid repository.

• 
  Priyansh (@itspriionly) reported 14 minutes ago

  The IT market is broken, and nobody wants to admit it. Someone spends 6 months sending out resumes. Six MONTHS. They learn React, Next.js, TypeScript, AWS, Docker. They take courses, build projects, improve GitHub profiles, optimize LinkedIn. Nothing. Complete silence. Companies don’t just want programmers anymore. They want someone who codes, shines in meetings, makes memes on Slack, and lives the company culture 24/7. AI is replacing junior work. Seniors are holding onto senior roles. And somewhere in the middle are people with 2–3 years of experience who somehow still feel invisible.

• 
  Noonien Soong (@mlcarldev) reported 16 minutes ago

  Team @droid It's a bit unfortunate that something, likely in my local Droid installation, has stalled progress. This comes after 20 hours of brilliant, excellent planning and execution on the first 30% of this platform, where a stellar handoff procedure was created so I could start a new mission... which was the recommendation of the orchestrating agent in that first mission. Starting this second mission with a fresh context window, the agent again did a brilliant job planning the next milestones. It was extraordinary, detailed planning... but then it could not execute. After the planning and after me accepting the proposal, it refused to execute, throwing an error every time. The agent tried everything: 1. He decreased the size of the plan down to one line, so it is definitely not the content of the plan causing the issue. 2. He even deleted some mission and plan related json and other files to reset it while preserving all the information. I have restarted Droid and resumed the session, but it just doesn't work. I wrote a detailed, comprehensive bug report and filed it under issues in your GitHub repo, as this seems to be a real problem now. Issues #98 and #99 I hope that a next update will somehow reset my configuration. I didn't see a new version being installed that could have introduced a bug, so this must be something Droid does on such an extensive mission... perhaps when trying to start a new mission in the same repository, which is normal procedure according to the documentation. Something is off, and essentially I have been unable to continue the test since yesterday. I cannot continue having this platform coded here, while Opus Ultracode, on the other hand, has been delivering pretty functional stuff so far. It is a bit chaotic the way it works... it doesn't really stick to the plan... but it always comes back when reminded. I am pretty sure that today I will have a functioning platform delivered by Opus, though it will probably need some debugging and fine-tuning. It is unfortunate because I am confident GLM 5.2 could compete with Opus 4.8. The first stint showed this clearly; that first flawless 98% of the context window in the first mission was absolutely stellar. If I were to reinstall Droid from scratch, I assume I would lose all the artifacts that I have. The orchestrator: Key points to highlight when you pass it to Factory AI: 1. Root cause (smoking gun in the logs): the orchestrator session is bound to missionId 7ba4d425 via session tags, and this binding persists across CLI restarts. ProposeMission looks up that mission directory, finds nothing (because I deleted it trying to fix the issue), and crashes on H.length where H is the undefined result. 2. The bug is likely in session-tag lifecycle: the missionId tag is set at session creation time (before any ProposeMission call), so a failed proposal poisons the session permanently. The tag should be set AFTER a successful proposal, or cleared on restart if the referenced mission no longer exists. 3. The fix is almost certainly to start a completely fresh session (not --resume, and possibly in a new terminal window / after clearing ~/.factory/sessions/). I did not try this because you asked for the bug report first, but it is the most likely workaround on your side. 4. The AskUser tool is also broken in this session with a similar parse error, reinforcing that this is a session-state corruption issue, not a ProposeMission-specific bug. My comment: I meanwhiile tested. All the recommendations and the Ask User tool are now broken, even in completely unrelated new missions and new repositories. Planning also can't go to execution; it's always the same error. Droid seems to be broken for good now, at least on my computer.

• 
  top10.dev (@Top10_Dev) reported 17 minutes ago

  SunJaycy/GoldenEye-Recomp just hit @github Trending at 503★ — the N64Recomp toolchain (the one behind Zelda 64: Recompiled / Majora's Mask) now eats Rare's 1997 engine. Static recomp ≠ emulation. The ROM is lifted to C at build time, compiled to native x86_64/ARM64, and paired with RT64 for path-traced lighting at 4K. No interpreter loop. Real binary. GoldenEye was the hard target — microcode-heavy muzzle flashes, split-screen viewport math, infamous AI. If it works, the toolchain has cleared the "Zelda-shaped problem" bar. #opensource #gamedev

• 
  Apache Superset (@apachesuperset) reported 19 minutes ago

  @J_00_S_T Would love to know more (not all of us use that installation method) if you want to file a GitHub Issue so we can update the docs accordingly.

• 
  Geoff Langenderfer (@geoff_l) reported 25 minutes ago

  @petergyang @GergelyOrosz it's evaluating llm performance on known github issues you have a github issue with an attached code change. The llm makes an attempt and you compare it to the known good code diff.

• 
  Ghostroot (@Gh0stroot) reported 33 minutes ago

  GitHub published a tool that forces AI agents to understand before they build. 95K stars in days. The problem with AI coding agents was never the model. It was this: You send an idea in text. The agent interprets whatever it wants. Builds the wrong thing. You start over. spec-kit fixes that with 6 commands. /speckit.constitution → sets the rules: quality, testing, architecture. /speckit.specify → you describe WHAT to build. Not the stack. /speckit.clarify → the agent asks what it doesn't understand before writing a single line of code. /speckit.plan → now you choose the technology. /speckit.tasks → ordered list of tasks by dependencies. /speckit.implement → the agent builds. The deliverable is no longer wildly generated code. It's a living specification that your AI reads, validates, and executes step by step. Works with Claude Code, Cursor, Copilot, Codex, Gemini CLI and 25+ agents. 95K stars. 8.3K forks. Published by GitHub itself. MIT license. Before spec-kit: "make me a task app" and you pray the agent doesn't get lost halfway. After spec-kit: specification first. code after. The agent knows exactly what to build. In what order. And why.

• 
  Keisuke (@KeisukeIshikawa) reported 33 minutes ago

  CLAUDE FABLE 5 SYSTEM PROMPT AND ANTHROPIC CAN'T DELETE IT. THE GOVERNMENT PULLED THE MODEL. THE INSTRUCTIONS ARE STILL PUBLIC. 120,000 characters. 1,685 lines. 27,000 tokens. every rule anthropic gave the most powerful model it ever shipped sitting in a github repo with 40,000 stars what the leak actually reveals: → fable 5 and mythos 5 are the same model. the only difference is the safety filter layer on top → a persistent storage API most users never knew existed artifacts that save data across sessions → exactly how the copyright limits work: hard 15-word quote cap, one quote per source, then it paraphrases → the full child-safety instruction block, word for word → how it decides when to refuse vs comply, written out in plain english this is the closest thing to seeing behind the curtain that exists. if you ever wondered why claude talks the way it does, or refuses what it refuses, the answer isn't a mystery anymore. it's a text file the repo is run by pliny — the same guy who's been jailbreaking frontier models the day they launch for two years. CL4R1T4S now holds the leaked system prompts for chatgpt, gemini, grok, perplexity, cursor, and every model that matters the original post hit 700,000 views in 48 hours. the repo gained thousands of stars in a weekend here's the part anthropic can't fix: the government can force a model offline in three hours. it cannot un-leak 120,000 characters that already live on 40,000 forked machines the system prompt is the actual product. the weights are the engine, but the prompt is the steering wheel. and the steering wheel is now open source whether anthropic likes it or not we are watching the last secret layer of frontier AI get pried open one leak at a time follow and bookmark before the next wave figures it out

• 
  Todd Desiato (@TokenDepotCorp) reported 34 minutes ago

  Would you be interested in helping promote real Kaspa adoption? I spent the past year building Oma Wallet, a Kaspa wallet designed specifically for token utility. It is live now, but it launched quietly and did not get much media attention. Oma supports Kaspa, KRC-20 tokens, Issue-Mode CA tokens, offers, swaps, rewards, discounts, subscriptions, memberships, and other real-world token use cases. I am also building AMEKAS, pronounced Am-eh-KAS, like "Am-eh-ri-ca + Kas" with emphasis on KAS. It is a Kaspa and KRC-20 checkout shopping center where sellers can set up online stores that accept Kaspa and approved KRC-20 discount or entitlement tokens at checkout. No dollar checkout, no payment processor fees, and no broker fees. There is also a node operator angle: anyone running a Kaspa node can install a small script that lets them manage subscribers for Oma Wallet and future AMEKAS shopping access. That can turn a Kaspa node into a subscription business tied directly to Kaspa utility. You can learn more on the Token Depot website and GitHub. I know your goal is to promote Kaspa. Would you be willing to take a look and help spread the word?

• 
  Kevin Tabet (@TabetKevin) reported 34 minutes ago

  @upstash Hey guys i think login with github is broken can't log in rn will try later. google works email i dont have

• 
  Darren Shepherd (@ibuildthecloud) reported 36 minutes ago

  @NoahCxrest For the main purpose of *** hosting, social coding, and humans collaborating, there's really nothing better than GitHub. I'm just no longer interested in those things since I'm purely focused on agentic coding these days. I still use GitHub as the place where I push and pull *** repos. But I have no more interest in Issues, PRs, CI. Those things I'm all replacing with agent-first approaches. I honestly don't have a solution I can point anyone to because they're all still being developed. All I can say is if I try to use GitHub for these things, it just gets in the way.

• 
  Jarrad Grigg (@jarradgrigg) reported 37 minutes ago

  You build stuff and host on GitHub pubically? Paste this into a coding-agent session and point it at your own GitHub account. This is happening way too much. ROTATE YOUR KEYS. Review my public GitHub repositories for accidentally exposed environment secrets. Scope: - Only inspect repositories I own or explicitly authorize. - Focus on public repos first. - Check current files and *** history. - Look for API keys, tokens, private keys, database URLs, OAuth secrets, webhooks, cloud credentials, .env files, config dumps, and hardcoded secrets. Safety rules: - Do not print full secrets in chat. - Redact values, showing only provider/type, file path, line, commit SHA if relevant, and a short masked prefix/suffix. - Do not test or validate secrets by calling third-party APIs. - Do not open PRs, issues, or comments that expose findings publicly. - If a likely secret is found, assume it is compromised and tell me to rotate or revoke it. Deliverable: - A prioritized report of confirmed or likely exposed secrets. - Exact repo/file/line/commit references. - Recommended rotation steps by provider. - Cleanup guidance for removing secrets from current files and *** history. - Prevention recommendations: .gitignore, env templates, secret scanning, pre-commit hooks, and CI checks.

• 
  🃏 (@anupamrjp) reported 38 minutes ago

  9.1 CGPA. Banned from placements. Never solved a single LeetCode problem. GitHub full of code I can’t explain in an interview. AI ghostwrote my degree. By every metric that mattered in 2015, I’m unemployable. By every metric that matters in 2026, I’m exactly on schedule. The system graded memorization. The market now pays for taste, speed, and the guts to ship something broken in public. I didn’t fail the old game. I just got recruited for a different one. Building now. No permission asked.

• 
  The Flow (@raxpcodes) reported 38 minutes ago

  Got bored with ubuntu , set up fedora kde on my nvme and removed windows permanently , no more dual boot. Also learned Verison Control and GitHub , also submitted my first pr (good first issue).

• 
  xjdr (@_xjdr) reported 39 minutes ago

  @xlr8harder Looks like there is a bug in the manual sign up. Sign up with Google or GitHub should work otherwise I should have a hot fix shortly

• 
  Financial Programmer (@RBiancoUS) reported 40 minutes ago

  A dose of reality for end of week. My biggest question is I can't find any reason for the $Gold panic- did they find gold is causing cancer or radioactive? Selling looks like sheer panic. Would you believe someone asks in DM, so how did *you* get so many followers. Then he lets me brew on it for a day and comes back, I was joking do you have a github, presumably to get some code. No wonder I worked alone. I'm challenged socially guess not alone. After a night of 3 scammers one from Nigeria, one Africa. I need to lock dm down or find a way to restrict

• 
  Prashanth Koppula (@koppula) reported 49 minutes ago

  4/6 ReproRepo sidesteps that by treating GitHub issues as a proxy signal across 1,149 recent ML papers from major conferences. The trick: instead of expert-curated labels, the framework matches agent-reported issues to human-raised GitHub issues using semantic similarity.

• 
  Irish Creek (@IrishCreek1919) reported 49 minutes ago

  @kr0der GitHub is their number one source for free human IP why would they want to take it down? It's nice to see the open source to proprietary pipeline is going to be even more efficient.

• 
  0xstack (@eth0xzar) reported 50 minutes ago

  DON'T BUILD A COMPANY. BUILD SOMETHING PEOPLE CAN PAY FOR THIS WEEK. This girl started in February. A few months later, her product had already processed over $6,000 in payments. Just a cheat Claude project she decided to turn into a real product. Here's the process: > Build something useful for yourself. > Tell Claude to push it to GitHub. > Connect Supabase so multiple users can use it. > Deploy it with Vercel. > Connect Stripe. Now people can actually pay you. You don't need a revolutionary idea. You need: > GitHub > Supabase > Vercel > Stripe > guide from Anthropic And a problem worth solving. This article will help you build it 👇

• 
  Peter Dedene (@dedene) reported 51 minutes ago

  GitHub reliability issues are pushing the industry to innovate. Yesterday Cursor dropped “Origin”. Today Epic announces “Lore” to replace *** entirely. The ecosystem migration seems to finally be starting.

• 
  Ale 𝕏 (@SirAlexthomson) reported 51 minutes ago

  This is actually a pretty big move. Cursor has been eating GitHub Copilot’s lunch for a while now, and this feels like they’re doubling down on becoming the default AI coding environment. If they keep improving at this rate, GitHub is going to feel real pressure. Copilot was the early leader, but Cursor is moving faster on the agentic side. Interesting to watch.

• 
  wispem-wantex (@wispem_wantex) reported 54 minutes ago

  I think a reasonable compromise would be to henceforth hold Anthropic responsible for any security breaches or service outages. Every time Github goes down, Anthropic should be fined

• 
  Jose (@SolutionsCay) reported 54 minutes ago

  @petergyang /goal make me app does not work for me 😰 but /goal complete GitHub issues #90, #91, #92 works very well

• 
  Pipeshub ( Open Source Alternative To Glean ) (@PipesHub) reported 56 minutes ago

  Pipelines are built. Context is broken. MCP is quickly becoming the default interface for enterprise AI agents. And that’s a good thing. It gives agents a standard way to connect with tools and data. Connecting an AI agent to Slack, Jira, GitHub, and Salesforce doesn’t mean it suddenly understands your business. It just means it can access your data silos. In short: "MCP gives your agent a passport. It doesn't give them a map." As enterprise AI undergoes a massive platform shift from passive chatbots to autonomous agentic workflows, this naive, runtime "federated search" approach creates an ugly cycle in production: - The Latency Spike: Slower agent execution while waiting for multiple external APIs to respond before it can even begin reasoning. - The Token Bleed: Skyrocketing bills from shoveling raw, unranked JSON dumps into a massive context window, praying the model finds the answer. - The Governance Nightmare: A massive risk of data leaks if you rely on a base LLM to magically guess and police complex enterprise security permissions on the fly. Agents do not fail because they lack intelligence. They fail because they lack the right enterprise context. The hardest problem in enterprise AI isn't connecting to systems. MCP solved that. The hardest problem is Context Engineering. MCP is the perfect interface, but a permission-aware context layer must be the foundation. 🚀 If AI is becoming core enterprise infrastructure, you cannot allow the strategic intelligence layer of your company to sit inside someone else's managed, closed-box platform. That is exactly why we built Pipeshub (open-source developer owned context infrastructure layer). TL;DR MCP gives agents access. A context layer gives them understanding. And deep understanding is the only way enterprise AI moves from a cool demo to secure, reliable production. 👉 Next Up Tomorrow: MCP Token Tax