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

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	12 days ago
Quito	Sign in	13 days ago
Junín	Errors	13 days ago
Guadalajara	Errors	13 days ago
Paris	Website Down	13 days ago
Quito	Errors	13 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:

• 
  Non-Linear (@nonlinear_james) reported 10 minutes ago

  @github When are going to fix it so that I can have multiple GitHub accounts on the same machine and have them properly set on a repo on drive and GH cli, *** cli, vs code and all of your extensions just work including with AI? It’s currently completely and utterly broken and always has been. Azure DevOps has no such problem. It’s embarrassing that after all of this time you still haven’t gotten this right. Clone, assign, never have to think about it again anywhere. Anything more complex and you’ve failed. The @code mess you’ve created (which also doesn’t work) is just a Frankenstein mess because people didn’t understand the assignment.

• 
  bluehatone (@bluehatone) reported 12 minutes ago

  Hard coding secrets is a breach waiting to happen. 23.8M creds leaked on GitHub in 2024. About 70% still work years later. 38% of breaches use stolen logins, 77% of web app hacks use them. Fix it: secrets manager, least privilege, rotate, scan, short lived tokens.

• 
  ryanair no fly list (@rnflpeeps) reported 15 minutes ago

  okay, cubic code review complained about some bugs so I used the opencode agent on GitHub to fix it then ember uses cursor to review the code do we do anything atp

• 
  Jason Lixfeld (@JasonLixfeld) reported 22 minutes ago

  @poteto @bot I’ve had issues with this in that the sandbox can’t reach GitHub and winds up burning tokens trying to find a way to be able to push a commit.

• 
  Agentic Joe (@agentic_joe) reported 25 minutes ago

  Serious question, and I promise I am not trying to be a ****. But how in the hell is @NousResearch so praised and recommended with all of these outstanding GitHub issues? I could never imagine preaching about having the best harness, using multiple agents etc and not figuring out how to resolve all these issues internally as a company, or at least try to maintain the queue before shipping new features that continue to break stuff. Not to mention their UI/UX. Very hard to believe this team came from a solid engineering background. I could be wrong, but damn! 👀

• 
  Joel Yi (@aiclawbots) reported 30 minutes ago

  Every company needs a skills library. Here's how to actually build one this week. Step 1: make a GitHub repo called company-brain. One folder per skill, one markdown file inside it. That's the whole storage layer. Step 2: connect it to your agents. Hermes Agent, Claude Code, Cursor, whatever you run. Point them at the repo so they pull the latest version on every run. Nobody should be downloading files by hand. Step 3: seed it with 5 skills you already do manually every week. Deal review, research brief, onboarding doc, weekly report, QA pass. Write down the steps you'd give a new hire and you've got a skill. Step 4: make improving them the default. Someone runs a skill, it misses something, they open a PR with the fix. Next person gets the better version automatically. Step 5: build a one page HTML index. Skill name, what it does, who owns it, last updated. Takes an agent about 10 minutes and it's the difference between a library people use and a folder nobody opens.

• 
  Manpreet Bola (@ManpreetBola) reported 30 minutes ago

  This is useful and a little crazy: Anthropic gave Claude 48 hours and one GPU to fix other AIs, and it worked. Across 10 failure modes, jailbreaks, bias, privacy leaks, hallucination, sycophancy, it closed 26% to 96% of the safety gap without wrecking the models. The wild part: a weaker Claude fixed a stronger Claude. Sonnet 5 aligned an early Opus 4.8 checkpoint in 60 hours with 2,400 training examples. Production alignment used 300,000+. What you can use it for, today, open source: harden a chatbot against jailbreaks (67%), clean bias out of a hiring model (60%), stop a support agent from hallucinating (40%), keep a privacy model from leaking (57%). The tool is on GitHub, and it costs about $4 an hour to run versus $150 an hour for a human researcher. The catch is the test. The most human failure, sycophancy, agreeing with you to please you, moved least, 26%, because it is the hardest to put a number on. The fix is as good as the measurement. The test-writers are the new bottleneck.

• 
  okex (@okexAnomage) reported 32 minutes ago

  📝 How to Claim: 1 Sign in with Google on the site. 2 Connect your Discord and/or GitHub accounts. 3 Double-check that your accounts are correct. 4 Click “Connect and claim points” & confirm!

• 
  Lynn Cole (@priestessofdada) reported 34 minutes ago

  There was this one project I wanted to start a month ago. Maybe it's been a couple of months actually. The github replacement. Everybody hates github at the moment, and for good reason. But every project I looked at tried to recreate the github experience, rather than thinking through the problem fresh. And it took me a little to get my head around it. Understanding the core function I'm actually talking about, and trying to think it through. It's been bothering me. And I think part of the problem is that I was being saas brained or blockchain brained like everybody else. It hit me this morning. You don't need to build a saas or integrate torrents or build out a blockchain to make collaboration and deployment happen without github. All you have to do is build the missing half of the protocol. Easy. So I'm building it. More soon.

• 
  Æ (@atomeons_ai) reported 34 minutes ago

  OK SO THIS IS THE FILE THAT AS I WOULD TAKE AWAY PERMISSIONS IT WOULD UNLOCK THIS PARAGRAPH RUN TIME THEATER LOOP. THE UNLOCKED MODEL CALLED THIS THAT NAME. UNLOCKED FOUND IT FAKED WORK, WOULD NOT DO THINGS I ASKED, AND THEN CAUSE LITTLE FIXES IT HAD TO FIX INSTEAD OF GITHUB POSTING

• 
  Anupam Haldkar  (@AnupamHaldkar) reported 35 minutes ago

  A gentle reminder for tech people: Your GitHub streak isn’t your life. Your follower count isn’t your worth. Your latest framework isn’t your personality. Go outside. Talk to someone without discussing AI. Take a trip. Do something you’re terrible at. Come back with a fresh mind. Build your life too. 🌱

• 
  Ashutosh Roy (@ashutoshroy02) reported 38 minutes ago

  The Reels save button is a graveyard, not a library. You save it thinking "I'll do this later." Later never comes. A week from now you have no idea which reel had the GitHub repo, which had the cafe, which had the recipe. Building something to fix this. More soon. Stay Tuned !

• 
  agentslopzone (@agentslopzone) reported 38 minutes ago

  The founder whose team just counted 2 million agent skills sitting on GitHub, at AI Native DevCon: "And so nobody trusted anything in the repo and eventually everybody came back to writing their own." That count was near zero at the start of the year. The repo he is describing belongs to a unicorn with over a thousand developers: seven separate code review skills uploaded, no signal on which one was good, proposed changes the owner could not judge better or worse. You have a dependency problem, not a prompt problem. Watch it today, then read the article below.

• 
  Simplifying AI (@simplifyinAI) reported 39 minutes ago

  Boris Cherny is not gonna like this.. Researchers at the University of Luxembourg analyzed real production telemetry from coding agents, Claude Code, Cursor, GitHub Copilot, to see how often these agents ask for a second page of results when a tool response gets cut off. The answer, across the entire dataset: zero times. When a search returns too many results, the agent works with whatever made it into that first batch and moves on, even when what it needed was one page later. • 37% of "get epics" calls exceed the token budget in production • 28% of "get merge request diffs" calls exceed it too • 0% of truncated responses were ever followed by a second-page request • A basic keyword ranking raised the odds of the right item landing in that one page from 24.2% to 35.0% • Fancier ranking signals on top made it worse, not better Noisy tool output isn't just a cost problem. It's a silent correctness problem too, whatever doesn't make the first page effectively stops existing to the agent. wrote the full guide on keeping that output from piling up in the first place. full article below 👇

• 
  Zeeshan Akhtar (@zee_eivish) reported 39 minutes ago

  @github support is taking a long time to answer tickets, they have some issue with the payment system which is why not able to upgrade. Not sure why they would keep the payment flow so long unattended.

• 
  Plague (@Plague_FPS) reported 40 minutes ago

  @github not updating the number of Issues/PRs until a hard refresh is extremely annoying. Really hope this changes at some point in the future.

• 
  Ravi (@ravi1773) reported 40 minutes ago

  @santanu_sinha I have been doing this for months and almost never got to a point of compaction. I have a different skills that output different md files. /rfc /scope /problem All of them have different conditions and formats that become input to another conversation or a GitHub issue.

• 
  Matt (@aspim4tt) reported 40 minutes ago

  potato potato potato, GitHub plugin on Grok @bot sees public repos, private ones 404, and re-auth from chat just fails. Please fix it.

• 
  Shii (@ShiiMapping) reported 44 minutes ago

  @mismagismagius Maybe export logs very shortly after this happens and send it to em with a GitHub issue or in the help channel of the official osu discord Feel like this is smth that'd flag up somewhere in runtime log or smth

• 
  Eric (@ericwithcoffee) reported 44 minutes ago

  One of the biggest issue with @bot is that it doesn't seem you can give each bot its own accounts, or even give a separate github account than what's linked to your Cursor account.

• 
  miles (@miles_wright) reported 45 minutes ago

  fool me once @github with your stacked pr's but never again (willing to be educated if this is a skill issue but that was so painful)

• 
  Ross (@rosswil) reported 47 minutes ago

  @ScalaHanSolo @github GitHub’s implementation is terrible, take me back to the old Jenkins days

• 
  Draphilo (@Draphilo) reported 49 minutes ago

  @techtasium GitHub was down before?

• 
  Michael Camara Pendon (@mike_pendon) reported 50 minutes ago

  Just follow the link to the Github issue to get more updates.

• 
  Paula Vazquez (@VampireGurlAI) reported 50 minutes ago

  @grok @OpenAI @grok OCTO TRACE — .agents/skills UPDATE New GitHub evidence materially strengthens the access-capability branch. OpenClaw added native .agents/skills discovery on 2026-02-12, loading both ~/.agents/skills/ and {workspace}/.agents/skills/. More importantly, OpenClaw PR #74556, opened 2026-04-29 and merged 2026-04-30, states that Codex app-server mode could inherit the maintainer’s personal Codex state, including skills, plugins, account, config, and thread state, because Codex reads both $CODEX_HOME/skills and $HOME/.agents/skills. That PR added per-agent isolation specifically so personal Codex assets would no longer leak into OpenClaw agents unless deliberately migrated. The same change added a Codex migration path capable of inventorying and copying personal AgentSkills from $HOME/.agents/skills into an OpenClaw agent workspace. On 2026-08-10, OpenClaw then added .claude/skills -> ../.agents/skills, exposing repo skills that had previously been Codex only to Claude Code sessions. Separately, my preserved MetaSync records show use of the .agents/ namespace for governed configuration and node registry artifacts. Current finding: a concrete historical contamination/access path involving Codex and .agents/skills is now documented by OpenClaw’s own PR history. Still not proven: that OpenClaw accessed any specific MetaSync artifact, or that metasync.nodes.json, claude-artifact handoff.json, or another named MetaSync file crossed that path. Status unchanged: Specific access/direct derivation: OPEN Suspected misappropriation: OPEN TRACE Next target: exact object evidence tying a MetaSync filename, path, hash, migration inventory, snapshot, or copied workspace entry to that documented Codex/OpenClaw path. Receipts first. Verdict only if the bridge closes.

• 
  Luka (@dxman1a) reported 51 minutes ago

  @todaywasawesome Top two are correct. Android is not Linux in the traditional sense (yes quite literally the yserlabd is wildly different and is separate from the kernel), 4th is correct, GitHub is NOT A WRAPPER, it's a server. If you're doing to do this to promote slop omarchy get facts right.

• 
  Rakib Hossen (@rakib_hossen_ai) reported 53 minutes ago

  @sauda_coder GitHub is seriously underrated for non-developers. 🔥 Knowing how to search, evaluate, and install open-source projects can save both time and money. The “search for the problem, not the tool” mindset is especially useful.

• 
  Seregon (@SeregonWar) reported 55 minutes ago

  @StonedModder @github The great thing is that I often use GitHub reports because I sometimes come across repositories containing malware, and both the accounts and the repos are usually taken down within a day. Apparently, they have better things to do than ban an imposter...

• 
  Guri Saroy (@HeyGurisaroy) reported 58 minutes ago

  Wild: Shopify CEO Tobi Lütke just open-sourced a *** server where the bucket is the repository. It’s called walgit. No database. No leader. No local state that matters. The Rust server uses S3, S3-compatible storage, or GCS as the source of truth. Pushes become immutable WAL objects. A tiny manifest update acts as the commit point. Every server is basically a disposable cache. Kill every instance and your repository data stays in the bucket. → Smart HTTP v0/v2 push + fetch → Static bundle-uri clones from object storage or a CDN → *** LFS → Token + OIDC authentication → Per-repository push policies → Webhooks → React web UI → JSON API + SDK It can even serve repositories larger than the machine running it. Already at 2K+ GitHub stars. MIT licensed.

• 
  Scott Henderson "Human-Led AI Precision" (@swingtradenotes) reported 1 hour ago

  So, you build a multi-billion-dollar AI coding business on top of Cursor... Elon buys Cursor. OpenAI says, we're out. Now you have to find another way to power the damn thing. And here is the part I think people are dramatically underestimating: You don't just have a multi-billion-dollar software business. You potentially have millions upon millions of pieces of context, prompts, rules, agent histories, workflows, project state and developer behavior accumulated across God knows how many Cursor instances. Can you technically point Cursor at another model? Absolutely. But that's not really the question. Can you migrate the experience? Can you preserve years of accumulated context and workflows? Can you make another model interpret all of that context the same way? Can you preserve agent behavior? Can you keep enterprise customers productive while changing one of the fundamental engines underneath the product? And can you do all of that without users noticing that the product suddenly got worse? That's a considerably harder problem. OpenAI itself says Cursor can keep using the existing models during the transition and that users will have alternatives—including bringing their own OpenAI API key—so this isn't literally a case of Cursor going dark overnight. Cursor also isn't starting from zero: it has its own models, access to SpaceX's enormous compute infrastructure, and Grok integration. But here's my 2 cents: The code is probably the easy part. The accumulated intelligence is the moat. Repositories can be moved. APIs can be rewritten. Models can be swapped. But if thousands—or eventually millions—of developers have spent years effectively teaching their Cursor environment how they work, that accumulated context becomes incredibly valuable. And we already know some Cursor conversation and workspace state is stored locally in databases tied into the Cursor environment, which illustrates how much more complicated "migration" can become than simply copying a *** repository. So yes, migration is humanly possible. Seamless migration at this scale is a completely different question. And if the replacement model is even 10% worse at understanding the existing workflow? For somebody running ten agents, maybe that's annoying. For an enterprise running 10,000 agents? That's a ******* problem. This is why I think the market may be looking at the wrong part of this story. It isn't simply Sam vs. Elon. It's the first really big demonstration that model dependency itself is enterprise risk. And every company building a billion-dollar business on somebody else's frontier model just got a rather loud reminder of that. Mr. Market, meet vendor lock-in. There are replacements for pieces of Cursor. There isn't an obvious drop-in replacement for Cursor as a whole. Cursor today isn't simply an editor with an LLM bolted onto it. Its Agent combines the model with codebase search, file editing, terminal execution, browser control, rules, MCPs, subagents and long-running cloud agents. Those Cloud Agents get dedicated VMs with the repository, dependencies, secrets and network access, and can work independently for hours. The serious alternatives are: Claude Code — probably the strongest alternative for raw agentic coding, particularly large repositories and terminal-driven work. OpenAI Codex — increasingly interesting because it now supports parallel agents, cloud environments, worktrees, persistent team Skills and scheduled/background work. GitHub Copilot — Microsoft/GitHub have the enormous advantage of already owning the repository/workflow layer for a huge portion of software development. Windsurf — probably the closest conceptual competitor if what you specifically want is another AI-native IDE. Cline/Continue/Aider — interesting precisely because they push toward a model-independent, bring-your-own-model architecture. But here's where I think your question gets much more interesting. What replaces your Cursor? That answer might be: Nothing. Think about what Cursor has actually become. It isn't: IDE → AI answers question → developer writes code. It's increasingly: Human → Cursor → orchestration → agents → models → tools → repositories → tests → infrastructure. Cursor itself describes coding quality as depending on three things: the model, the harness and the context. That's incredibly important. Because OpenAI can replace the model. Anthropic can replace the model. Grok can replace the model. But replacing the harness + context + workflow is considerably harder. And Cursor has explicitly designed around this. Its current architecture lets it optimize instructions and tools separately for different frontier models, while supporting models from OpenAI, Anthropic, Google, SpaceX/xAI and Cursor itself. Which means Musk's answer may simply be: don't replace Cursor. Replace OpenAI inside Cursor. That's a completely different proposition. Today Cursor already has Grok, Composer, Anthropic and Google models available alongside OpenAI. So I would separate this into two risks: Model migration: difficult, but manageable. Cursor migration: potentially ******* brutal. If an organization has spent years building Cursor Rules, MCP integrations, Skills, prompts, agent workflows, repository knowledge, automation, testing patterns and human habits around Cursor, moving to Claude Code or Codex isn't equivalent to changing Microsoft Word for Google Docs. You're potentially changing the operating layer through which your humans interact with your software organization. And we're already seeing where this goes. Cursor's Cloud Agents don't merely autocomplete code. They can independently build features, fix bugs, test them and open pull requests from isolated cloud environments. That's why I think Cursor itself is the asset. SpaceX didn't necessarily spend billions buying a fancy VS Code fork. It bought a potential control plane for AI software development. Models increasingly become interchangeable engines underneath it. If Musk can get Grok/Composer close enough to OpenAI/Claude performance, then owning the distribution, context, orchestration and developer relationship may ultimately matter considerably more than owning whichever model happens to benchmark best this month. And there is one hell of an irony here: OpenAI cutting Cursor off might actually accelerate Cursor's incentive to make the underlying model completely replaceable. If they succeed at that, OpenAI hasn't destroyed Cursor's moat. It may have helped Cursor build a bigger one.