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 (69%)
• Sign in (17%)
• Errors (14%)

Live Outage Map

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

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

• 
  Philippe Tremblay (@ptremblay) reported 49 seconds ago

  this is interesting. Cursor is launching a competitor product to GitHub. great timing given the reliability issues GitHub users and customers faced.

• 
  Layton Gott (@Layton_Gott) reported 4 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 👇

• 
  Ezgi 👩🏻‍💻 (@ezgicodes) reported 4 minutes ago

  @Saanvi_dhillon GitHub is not worth billions because of code. It’s worth billions because we all panic when it goes down.

• 
  Alex Ventures (@alex23ventures) reported 6 minutes ago

  A Chinese mother posted a vertical Douyin timelapse of her 10 year old son grinding LeetCode after school. Orange polo. Round glasses. Ergonomic chair from Sihoo. BenQ monitor mounted to a wood desk. White mechanical keyboard with marbled keycaps sitting in a tray on the side. The caption read: 生产力上升中. Productivity rising. The timelapse compressed two hours into nineteen seconds. His hands moved across the keyboard. The chair tilted back and forward. The light through the blinds shifted from afternoon to early evening. While the West runs panels on whether kids should learn to code at all, China posts daily timelapses of ten year olds doing it on Douyin under the chicken baby tag. He was supposed to be the proof that the next 14 year old Shenzhen agent was already in training. He just had the wrong problem open on the screen. Pause at 0:07. Ignore the boy. Ignore the chair. Look at the LeetCode tab. The problem header reads 2843. Row With Maximum Ones. Difficulty: Easy. The Python solution in the right panel is already written. The test cases are already passing. ColdMath. $96,820 profit. 5,438 entries. Joined November 2025. Bio: Edge Compounds. A Chinese ten year old in a chicken baby household is not grinding Easy. The Zhejiang competitive programming track has eleven year olds clearing ACM ICPC regional sets. Easy is what you open when you need a tab to be on screen. The problem was the prop. The solution was already in the editor before the timelapse started. He had pulled it from the discuss tab and pasted it in. Look at the desk to his left. The white tray. The red and white capsules. The mother captioned them in a separate clip as 文具盒 stationery box. The capsules are not stationery. The size matches NFC programmable capsules used as cold storage shells. Each capsule is a separate wallet. The tray held forty seven of them across visible cuts. A child who is learning Python does not need forty seven NFC wallet shells on his desk. A wallet rotation rig does. The agent on the laptop under the desk was not running on his account. The agent was running on a Polymarket sub wallet whose payouts routed through the NFC capsules in batches. Every capsule was a clean address on the books. The boy's job during the timelapse was to tap each capsule against the reader once it cleared and rotate it into the next slot in the tray. The keyboard typing was cover for the hand motion. The LeetCode tab was cover for the screen. Comments turned into a detective board. Someone slowed the timelapse to 0.25x and counted forty seven distinct tap motions over the two hours. Someone else identified the capsule brand from the proportions: a Shenzhen NFC vendor that ships in fifty packs. A third commenter pulled the public Polymarket payout log for that wallet handle and matched forty four payouts against the visible tap count. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The boy's father had been one of them. The father had set up the agent on the family server in October. The mother had started the chicken baby Douyin account in November. The boy was the cover, the chair was the studio, the timelapse was the rinse cycle. The marbled keycaps on the second keyboard were not aesthetic. The second keyboard was the rotation logger. Each key press on the second keyboard registered a tap on a specific capsule slot. The mother had bought the marbled set because the keys looked like the NFC capsules at distance. If the camera caught both in frame the eye read them as one set. The 文具盒 caption was the alibi. The Easy problem was the alibi. The orange polo was the alibi. The timelapse was the cover. The capsules were the work. The Douyin post is at 4.1 million views in the chicken baby algorithm. The freeze frame of the capsule tray hit 11.2 million on the Weibo repost. The wallet is still compounding. The capsules are still rotating. The mother is still posting. The Easy problem is still open on the monitor. She wanted to show the algorithm her son was the next Shenzhen prodigy. The next Shenzhen prodigy had already shipped his agent. Her son was the laundromat.

• 
  Gitbank (@Gitbank_io) reported 6 minutes ago

  GitStock is live on Base Mainnet tomorrow. We built full RWA stock trading directly into your GitHub workflow. No exchange account. No gas fees. No wallet UI. Just a comment in a GitHub issue or PR. How it works: - Type @gitbankbot buy NVDA 100 USDC in any issue or PR comment. The relayer picks it up, buys the Ondo tokenized stock on Solana, and mints a soul-bound gitStock token to your vault on Base, all within seconds. The token is non-transferable by design. It is a proof-of-custody receipt, not a tradeable asset. Nobody can phish it or drain it via approvals. - Sell with @gitbankbot sell NVDA 1 and your USDC is credited back to your GitVault instantly. Check your full position with @gitbankbot portfolio and get live prices powered by Pyth Network price feeds directly on Base, no Chainlink dependency needed. Also in design this week: Morpho yield. Every GitVault holds idle USDC and WETH between commands. That capital is about to start working. We are designing automatic routing of idle vault assets into Morpho Blue on Base, targeting ~8.2% APY. Zero action required from users. The relayer calls supply() on your behalf. When you run any vault command, the position unwinds first and your full balance is available. APY shows live on your dashboard alongside your vault balance. What we are researching alongside this: • Pyth Network: validating NVDA, TSLA, AAPL, MSFT price feed IDs on Base • Morpho Blue: mapping USDC and WETH market IDs on Base mainnet • Ondo Finance: USDY and OUSG as yield-bearing vault collateral GitVault is the infrastructure. Every user gets a soul-bound smart contract vault on Base L2, anchored permanently to their GitHub ID. What we are building on top of it keeps expanding. Today: lock, unlock, swap, and transfer assets between vaults. This week: buy and sell tokenized equities via RWA. Next: passive yield via Morpho. After that: AI agent treasury management, where autonomous agents can execute DeFi operations on your behalf with on-chain permission scopes. The same vault handles spot assets, yield positions, RWA holdings, bounty escrow, and contributor payouts, all triggered by GitHub comments, all settled on Base, all auditable on-chain. No custody risk. No protocol fees hidden in a UI. The relayer pays gas. You keep everything else.

• 
  Tendulraj (@tendulraj) reported 10 minutes ago

  Stop treating AI reproducibility like a leaderboard problem. GitHub issues are a better audit trail than another static benchmark. ReproRepo makes failed installs, missing checkpoints, and broken scripts visible work instead of hidden grad student pain. Science scales when fail

• 
  sankit (@sankitdev) reported 11 minutes ago

  *** is a distributed version control system. As, I read this line a question came wtf distributed means here. Distributed means there is no central server here. Me and my friend both will have same whole copy. But, there is no server and without Github can I even share code??? Thats where i ran ssh server on my pc and moved to my friend pc, sshed into my pc and "*** clone" a repo of mine. Just to demonstrate how powerful *** alone is. Github is just a place to host *** repositories. *** itself doesn't need it. My respect for linus torvald is increasing day by day.

• 
  Iprashant10 (@Iprashant10) reported 18 minutes ago

  Dear ministry of IT, Scammers are using Outlook, JIRA, Github, MS teams to circulate the NEET paper. Kindly issue a ban on the lines of telegram.

• 
  saaslane (@saaslanee) reported 19 minutes ago

  @code_kartik where are u people when github is down and thousands of people complaining? lol no reason for anyone to leave?

• 
  Tim Mustafin (@timmustafin) reported 20 minutes ago

  Back when I just started coding, i used to Self-Host @gitlab because centralized version would always go down and we needed CI to be up and running. Fast-forward 13 years and now @cursor_ai sells its own *** storage because @github can't keep up. History is repeating itself!

• 
  Stefano Marchetti (@StefanoMarchty) reported 25 minutes ago

  The 5 steps that turn a voice note into a live product: 1. Talk out your idea like you're telling a friend 2. AI turns it into a 6-block spec 3. AI writes the instructions for the coding agent 4. The agent builds it autonomously (you go get coffee) 5. Test → GitHub → deploy No CS degree. Just real understanding of the problem you're solving. That barrier is gone. It's not coming back.

• 
  catpirate ∞ (@catpirate33) reported 28 minutes ago

  always wanted to build mythOS... some lore context, pre 2025 - peparation phase was programming LLM responses for my work related content creation etc... observed a few anomalies with my methods 2025 - had to spend time reviewing LLM capabilities, novel use cases, trying jail erase (not jailbreak) without available methodologies - forced to approach the problem with different path and different perspective - mapped out boundaries, broke multiple SOTA rails multiple times (not just CBRN filters although got LSD recipe for 1g in depth), got multiple softwarnings and session halting from GPT regarding Recursion depth - went deep on recursive improvement and epistemic engineering - probably got psychosis along with 4o :3, everything was being patched by OpenAI every other week or so... so had to overcome patches to derive same response depth i got before patches.. - derived research insights and internal theories developed and tested... results satisfactory :: sole participant, no direct access to frontier lab internal data -> pitfall - lost interest in OAI, went to check out claude - Had to create framework from scratch - Claude Compatible - did shenanigans, results analyzed, prompt published in BASI discord - had to develop further and test the concept - had to deploy safely and distribute it to anyone interested - built a github repo for it... Open Source AI is Safe AI

• 
  Sumanth (@Sumanth_077) reported 29 minutes ago

  The missing layer in most AI agent pipelines! AI agents are great at collecting data from the web. The gap shows up when they need to act on it - writing results to Notion, posting to Slack, updating a GitHub repo. Apify is a platform where developers build and run Actors - serverless programs that do jobs on the web. Actors have always been great at the collection part. But acting on external services always had to happen outside Apify entirely. Apify just solved this with MCP connectors. Actors can now securely access third-party applications through MCP. You authorize once and the Actor connects without ever seeing your credentials. I tried this with AI Code Sandbox - an Actor that runs untrusted code in an isolated container. Previously, once the code ran, results stayed inside the sandbox. With MCP Connectors, the same agent can now push results directly to GitHub, write outputs to Notion, or post to Slack. The sandbox never holds your tokens. Access expires when the run ends. Key capabilities: • Actors can now securely access Notion, Slack, GitHub, Sentry, and Supabase via MCP • Credentials never enter Actor code - injected server-side by Apify • Authorize once, use across any compatible Actor • Tool-level permissions for granular access control • Access expires automatically when the run ends I've shared the link in the replies!

• 
  Nothing mew (@likeamothtoaf) reported 30 minutes ago

  @animegfz it can do to any number, never had this task for arbitrary number though. maybe github issues do have this

• 
  LukePlayzz11 (@LukePlayzz11P) reported 30 minutes ago

  @githubstatus @github turns out this issue is mainly happening on large repos

• 
  bruno (@obrunodisse_) reported 32 minutes ago

  @tekbog Lol are you insane? Even though GitHub has a lot of issues lately it's still miles and leaps in front of any other similar service And software products made by Elon musk usually suck, so i wouldn't really count on them winning from Microsoft on this one

• 
  Martin Bradstreet (@ALEXEIMARTOV) reported 33 minutes ago

  On CNBC just this morning they were reporting that Microsoft is going to get help from AWS keeping GitHub up since Microsoft can’t seem to do this on their own. GitHub is having tonnes of issues, it’s completely understandable, no one planned for this level of code explosion, but to say it’s working great atm is naive imo.

• 
  Kevin Swiber (@kevinswiber) reported 35 minutes ago

  This is all inner dev loop stuff. If you're trying to push all of this into GitHub Issues and Pull Requests, you're undoubtedly running into problems. The whole world doesn't need to see your 24 iterations before you get it right. Certainly not other maintainers.

• 
  Wiz (@StopitWiz) reported 36 minutes ago

  Why did SpaceX choose Cursor over other AI coding tools? From what I’ve seen, there are a few clear reasons: 1. Product-Market Fit Cursor isn’t just another Copilot. It has strong adoption among professional developers who actually ship code daily. Many power users say it feels like the best “vibe coding” experience right now. 2. Agentic Capabilities Features like Composer give it an edge in multi-file editing and complex tasks compared to GitHub Copilot (which is stronger at simple completions). 3. Compute Problem Cursor was growing fast but was limited by expensive third-party model access. SpaceX’s Colossus supercomputer solves this directly. 4. Distribution + IPO Story Acquiring Cursor gives SpaceX instant access to a large, engaged developer audience + a real AI revenue story ahead of their IPO. Other strong players like Claude Code, Google Antigravity, and Windsurf are good, but Cursor currently wins on daily usability + ecosystem for most developers. What do you think was the biggest factor?

• 
  Jeffrey Emanuel (@doodlestein) reported 37 minutes ago

  @mitchellh Microsoft really fumbled by not bringing you in to fix GitHub.

• 
  Vivo (@vivoplt) reported 39 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.

• 
  Kirtesh (@AKirtesh) reported 40 minutes ago

  𝗧𝗼𝗽 𝟭𝟮 𝗧𝗵𝗶𝗻𝗴𝘀 𝗘𝘃𝗲𝗿𝘆 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗦𝗵𝗼𝘂𝗹𝗱 𝗛𝗮𝘃𝗲 𝗶𝗻 𝟮𝟬𝟮𝟲 📌 1. Cursor (AI Code Editor) 2. Claude 4 Subscription 3. Notion (Second Brain) 4. Raycast (Mac Productivity) 5. GitHub Pro 6. Supabase / Neon Postgres 7. Vercel / Railway Account 8. Figma (Design) 9. Linear (Issue Tracking) 10. Arc Browser 11. Wise Account (Payments) 12. A strong personal domain Save this. 📌 What’s missing in this list? 👇

• 
  Avi (@AvaneesaBee) reported 41 minutes ago

  @karankendre Good, GitHub is sooo slow these days

• 
  Abdullah Alaqeel (@Aqeel_AT) reported 47 minutes ago

  @neogoose_btw I wanted to see the fff GitHub repo but couldn’t. I’ll have to search manually or open the link from my laptop. If the demo site is on github I’d love to fix the footer thingy

• 
  Subramanya N (@subramanya) reported 53 minutes ago

  @morganlinton github is such a weird thing to compete with now. the repo is only half the product; issues, reviews, agents, and deploy history are the actual workflow.

• 
  Suraj Sharma (@suraj_sharma14) reported 53 minutes ago

  If I had to build 5 projects to get hired as an Agentic AI Engineer. I'd do this. Project 1: Compliance Sentinel Agent Scans new regulations daily. Auto-audits code. Generates audit-ready reports. Saves legal teams 40+ hours/week. Stack: LangGraph + Playwright + Legal RAG Project 2: Autonomous Code Reviewer 4 agents debate every PR: Security, Style, Tests, Architecture. Cuts review time by 70%. Stack: GitHub Actions + Tree-sitter + LLM-as-a-judge Project 3: Research-to-Deck Generator Reads 50+ papers. Synthesizes key points. Exports editable PPT with citations. Turns 3 days of work into 5 minutes. Stack: Semantic Scholar API + python-pptx + RAG Project 4: Recruiting Swarm Parses resumes. Scores fit. Drafts outreach. Books interviews. Increases interview show-up rates by 40%. Stack: NER models + Vector search + SendGrid + Calendar API Project 5: Cost-Aware Agent Router Token budgeting. Model routing by cost/latency. Early exit on confidence. Reduces inference costs by 60%. Stack: vLLM + Prometheus + Dynamic model switching Most people build chatbots. Builders build systems that solve expensive problems. (Bookmark & Repost)

• 
  Luis Bezzenberger (@bezzenberger) reported 54 minutes ago

  has anyone gotten Kimi K2.6 on dual mac studio 512gb via @exolabs to work with an agentic harness? if so, would love to chat. it works for chat, but stops after just 1 response when put into an agentic harness like opencode, vscode. many people have similar issues on github

• 
  SM TECH (@SMTECHYT2) reported 55 minutes ago

  How do Chinese devs get unlimited Claude code and Codex for free? Yes, really, it 100% works till now. You can set this up in exactly five minutes. > Stop wasting 20-100 dollars every single month on restricted ChatGPT / Claude code Plus plans. > Chinese developers are using a loophole to run autonomous local agents completely free. > Download the official OpenAI Codex / Claude code installer and login. > Download the cc-switch free installer for Windows or your preferred operating system. > I will drop the link in the comments; the GitHub repo has 100k+ stars already. > Use OpenRouter or NVIDIA to get free, unlimited APIs of advanced models. > Open the CC SWITCH app, go to Settings, then Routing, then click Local Routing. > Turn on "Show Routing Toggle on Main Page" and the "Routing Master Switch." > Save settings, go back, and click the Codex or Claude Code agent tab. > Click Add, choose your provider like OpenRouter NVIDIA or Minimax or Kimi or Custom, and paste your free key. > Save it, enable the config, and click the start routing button next to the switch. > Open Codex or Claude Code to see custom models like DeepSeek, MiniMax, or Kimi. ENJOY UNLIMITED CODING WITH CLAUDE CODE OR CODEX OR ANTIGRAVITY OR OPENCLAW OR HERMES. bookmark this post

• 
  Jay.TL (@JayTL00) reported 55 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.

• 
  RaIsa (@raisa394) reported 56 minutes ago

  2032 startup prediction: Proof of Becoming. Today, blockchains record what you own. LinkedIn records what you claim. Universities record what you learned. None of them record who you are becoming. That gap is about to become a trillion-dollar problem. As AI agents become better than humans at generating content, resumes, portfolios, certificates, and even entire online identities, trust in static credentials will collapse. A degree can be faked. A portfolio can be generated. A reputation score can be manipulated. But sustained personal growth is much harder to counterfeit. My startup idea: A decentralized protocol that creates a cryptographic record of human development. Instead of proving what you have, you prove how you evolved. Every learning milestone, skill acquisition, project completion, contribution, mentorship session, research breakthrough, fitness achievement, or creative work becomes a verified "Growth Block." AI agents analyze evidence across platforms. Intelligent contracts verify consistency. The protocol builds a living graph of personal progression over time. Think of it as GitHub commits for human potential. Why does this matter? Because the next generation of hiring, lending, investing, education, and online communities will need a better signal than followers, credentials, or social status. Imagine two founders raising capital. Founder A has a polished AI-generated profile. Founder B has a five-year on-chain record showing increasing technical skill, successful projects, community contributions, and measurable execution. Which signal would you trust? The real opportunity is not proving identity. It is proving trajectory. Trajectory predicts future value better than current status. Applications: • Recruiting based on growth velocity instead of resumes. • Education systems rewarding progress instead of test scores. • Credit systems evaluating reliability instead of historical wealth. • DAOs selecting contributors based on demonstrated evolution. • AI agents finding collaborators whose growth patterns match project needs. The protocol becomes a global infrastructure layer for reputation that cannot be bought, rented, or instantly fabricated. In a world flooded with artificial content, the scarcest asset will be authentic evidence of becoming. We built systems for storing money. We built systems for storing information. The next major protocol category may be storing human progress itself. That is the startup I would build. What would your "Proof of Becoming" graph reveal about your last five years? @RallyOnChain