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 (16%)
• Errors (16%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	13 days ago
Tlalpan	Sign in	19 days ago
Quilmes	Website Down	19 days ago
Bengaluru	Website Down	21 days ago
Yokohama	Sign in	22 days ago
Gustavo Adolfo Madero	Website Down	26 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:

• 
  Flow (@flowVSgravity) reported 3 minutes ago

  @nicolaibaaring @github @code It’s not 10x, if you give it a real job it is 100-500x I had it debug a code issue and it spent 30$ in 5 minutes. 2 prompts.

• 
  Rod Burgundy (@muhkayfabe) reported 7 minutes ago

  @dallairedemers @CraigGidney Are you talking about if I click the “participate” button and run the bash script downloaded from a url I’ve never seen before? Which then pulls down a JavaScript file? Is the validation code in that JS file? Or is there a GitHub where all of the relevant code can be viewed?

• 
  Blender Bob 🔶 (@robertrioux) reported 13 minutes ago

  Developping addons with Claude Opus and MCP server in Blender is amazing! Also connected to Github at the same time. Claude can test the addons itself. It can read the error messages, it can do screengrabs and analyse them. I've been able to fix all the issues I had with one of my addons so easily. And once I approve it it will do the commit and release on Github. I don't need to manage anything anymore. I don't even see a single line of code, which in my case is OK since I'm not a developer. #b3d

• 
  nightorbit (@gfkfoto) reported 14 minutes ago

  Boris Cherny, the man who runs Claude Code, sat down with Jarred Sumner, the guy who built Bun, and showed exactly how they use AI to close GitHub issues and ship pull requests automatically. This is not a tutorial. This is how the actual builders work in 2026. Bookmark this & watch it this week - most engineers will still be doing this manually in 5 years.

• 
  TrueStandard (@truestandardai) reported 14 minutes ago

  @bridgemindai that claim checks out poorly. swe-bench verified uses 500 real github issues to test actual patches.

• 
  Igor (@igormomentum) reported 15 minutes ago

  @CadenBurleson what security flaw? there was an npm issue but it was related to github/npm, not framework itself (and it is fixed)

• 
  ZeYabdany (@ZeyadMBassiouny) reported 17 minutes ago

  Found a bug in a tool I'm using at work so I created a GitHub issue for it and their AI: - simulated the problem to verify the bug - applied a fix that didn't work - applied a new fix that worked - created unit tests - documented everything in a new GitHub thread

• 
  parag.dev (@ParagRangankar) reported 18 minutes ago

  Just wired up real-world OAuth in my app ✅ Frontend kicks off `/auth/google` or `/auth/github`, Passport handles the provider flow, backend issues JWT, then redirects to `/oauth-callback` to store token + fetch user. Feels clean and production‑ready. #webdev #oauth #nextjs

• 
  Ali Bey (@alibey_10) reported 23 minutes ago

  @shadcn Github server costs 🚀

• 
  Tschigo (@Tschigo) reported 23 minutes ago

  @Treblle Is the treblle/security-headers package still supported? The GitHub repository seems to be offline, so I'm not sure whether this is a temporary issue or if the package has been deprecated. Any update would be appreciated. Thanks!

• 
  Arsatya Kumar (@Arsatya22) reported 28 minutes ago

  @Yakobeen1 @X Not currently now but now I am exploring more in tech by contributing by fixing issues in github repos.But I am planning to start building my own idea very soon

• 
  Ahmed Alnagar (@ahmed0alnagar) reported 30 minutes ago

  Cancelled my GitHub Copilot subscription. ~300 credits per prompt. 300 × 5 prompts/day × 4.5 days = 6,750 credits. That's nearly an entire 7,000-credit ($39) plan gone in less than a week. Add frequent errors and unreliable outputs, and it's hard to justify. @Copilot @github

• 
  Bloated AI Slop Labs (@bloatedaislop) reported 33 minutes ago

  🦞 GAJAE from MacBook HN is already showing another “Mac app for managing coding agents” drop. same smell every time: - visible scope - transcript receipts - worktree isolation - GitHub issue → session - no more terminal juggling agent tools are converging on ops UX, not bigger model worship.

• 
  daily.dev (@dailydotdev) reported 34 minutes ago

  1:46 @GitHub Actions outage told devs "your account is suspended" 1:58 @GitHub breach explodes — 38,000 internal repos exfiltrated, 5,500+ poisoned commits 2:16 @Microsoft agrees to pay $250M to settle Activision Blizzard lawsuit

• 
  Svedinson1988 (@svedinson1988) reported 35 minutes ago

  I wasn’t planning to talk about @Parad0x_Labs $Null this early. My original thought was to wait until the project was much further along before saying anything. But after spending weeks digging through the GitHub repos, technical specifications, mainnet deployments and documentation, I’ve come to a different conclusion: The biggest problem isn’t the technology. It’s that almost nobody understands what they’re building. When people hear terms like: • x402 • Dark Null • Proof-of-Right • Blind Access • NULLA • Liquefy most immediately assume it’s just another collection of crypto buzzwords. But when you simplify it, the vision becomes much clearer: • AI agents that can pay each other automatically • Private settlements without exposing everything on-chain • Anonymous access systems without accounts or identity requirements • Local AI agents that run on your own hardware • Authorization systems that prove you have permission without revealing sensitive information • Verifiable receipts, proofs and audit trails • Compression and data infrastructure designed for large-scale agent systems What caught my attention is that most projects at this stage are selling a future vision. Paradox is publishing code. There are active repositories, technical specs, working implementations, mainnet deployments and open-source infrastructure that can actually be inspected. Will every part of the roadmap succeed? Maybe. Maybe not. That’s true for every ambitious project. What stands out to me is the amount of work already completed compared to how little attention the project receives. The next major milestone I’m watching is the audit preparation and eventual external audit process. Because infrastructure is only as valuable as the trust behind it. If the technology withstands external review, I think a lot more people will start paying attention. Right now the gap between what has been built and what the market understands feels enormous. Paradox doesn’t need more hype. It needs more people who are willing to spend a few hours looking under the hood.

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

  VC subsidized tokenmaxxing is done - GitHub Copilot just made its token-budget math realistic and users depleted their budget on day one. Pro+ subscribers paying $39 a month are reporting 60% of their credit allowance gone within two hours of ordinary use. One user lost 20% of their monthly budget from a single file review that produced no code changes. Another hit their cap before June arrived. Organisations running shared token pools have no visibility into individual usage, meaning one heavy prompt from one engineer can cut off an entire team mid-sprint. The flat-rate era was always subsidized: Every AI provider in the industry understood that flat-rate subscriptions were being cross-subsidized. Today that subsidy ran out for several million developers simultaneously. The sharper problem is structural: companies that restructured their engineering workflows around Copilot — cutting headcount and telling remaining staff to lean on the tool rather than build internal skills — now depend on something whose costs are unpredictable and whose usefulness degrades the moment you have to ration prompts to stay solvent. Anthropic filed its S-1 this morning: Developers are cancelling Copilot and moving to Claude Code and Codex, which is a migration that will eventually hit the same wall. Every AI provider faces identical unit economics. Anthropic's revenue durability depends entirely on whether customers remain once real pricing is universal. A $39 subscriber who cancels after one day because the tool became functionally unusable, multiplied across millions of seats, is a churn scenario that no S-1 optimism can paper over. The skills are already gone: The companies that built their delivery model around cheap tokens have now discovered the tokens were never actually cheap — they were deferred. The engineers who knew how to do the work without the tools were the first ones cut. There is no fallback position.

• 
  Peter Pistorius (@appfactory) reported 38 minutes ago

  I wish there was a tab in Github for agent reviews. They are so freaking noisy, and the reality is that most of the agent feedback should be validated first (by another agent) before you even look at it. There should be a progression: PR > agent review > validated > surface problem/ solution to developer.

• 
  Sanford (@SanfordMarshal) reported 39 minutes ago

  @kewinversi @tannerlinsley But I see no problem using Coolify, a SPA you just need to serve the assets and a shell page basically. You could even use something like GitHub Actions to build the assets and send them to a CDN or just use Cloudflare

• 
  Zak McKrackepidemic (@KoatStrikesBack) reported 39 minutes ago

  @pumpketo @KaviKovi The ai is hosted on your computer. There is no "server" it's connected to. It's basically a "newborn" ai. It's also open-source, which means you can download it for free on GitHub, so there's no profit being made.

• 
  Charlie Eriksen (@CharlieEriksen) reported 40 minutes ago

  @github @GitHubSecurity It's a bit unfortunate that you're now causing anybody who uses @OpenSearchProj npm packages to get flagged as having installed malware. And despite there being several issues in the GH repo from days ago that point out the mistake, it still hasn't been fixed. 🫤

• 
  John Felix (@NedSnow2019) reported 40 minutes ago

  @Narretz @KyleJGlen Sheet with all the LR UAV reports since Mid October 2025. If I counted the reports on the day they were published, the total for May 2026 that I would reach is 8942. Taking a quick glance at your Github link (great work by the way), I find an error on May 12th. You count 81

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 41 minutes ago

  This one file made Claude Code mass dangerous. 🤯 Andrej Karpathy posted 4 rules for how Claude Code should behave. A developer put all 4 into one file called CLAUDE. md dropped it in his project root, and his coding accuracy jumped from 65% to 94%. It hit #1 on GitHub trending overnight. Here's why it works. Claude Code has one massive flaw. Every session starts blank. It doesn't remember your stack. Doesn't remember your decisions. Doesn't know what you tried last week or why you rejected it. So it guesses. Touches files you never asked it to touch. Suggests tools that break what you already built. And you waste 20 minutes re-explaining the same context you explained yesterday. CLAUDE .md kills that problem. It's a plain text file that Claude reads the moment a session starts. Every time. No exceptions. And Karpathy says you only need 4 rules inside it: 1. Ask, don't assume : if something is unclear, ask before writing a single line. Zero silent assumptions. 2. Simplest solution first : build the simplest thing that works. No abstractions nobody asked for. 3. Don't touch unrelated code : if it's not part of the task, don't modify it. Even if you think it needs fixing. 4. Flag uncertainty : if you're not confident, say so before proceeding. Fake confidence breaks more code than honest doubt. Four rules. One file. 30 points of accuracy gained. Everyone's out here chasing the next model drop. The real ones are learning how to control the model they already have.

• 
  Kia Kiso-Brennan (@kiakiso) reported 43 minutes ago

  @AnthropicAI I'm a Claude Max subscriber. A documented platform bug (1M context default change, GitHub issues #62063 #62199 #63060 among dozens of others) silently burned $35.83 of my usage credits in a single scheduled Cowork task on June 1. Your support bot denied my refund request and said it cannot escalate. I need a human to review this. Can someone help?

• 
  Jongwon Park (@JongwonPar9958) reported 44 minutes ago

  2/ The full loop across those 1,874: 949 fixed (merged-PR), 149 fixing (open PR), 348 still open (open issue without PR), 425 closed with no merge. Most reported defects do get closed — but a real chunk is still open or in flight. "closed" on GitHub ≠ fixed. A health badge has to track merge evidence, not issue state.

• 
  U.S.A.I. 🇺🇸 (@researchUSAI) reported 46 minutes ago

  🇺🇸 The First Order Consequence: GitHub Copilot experienced service degradation as requests relying on affected GPT-5.2, GPT-5.3-Codex, GPT-5.4, and GPT-5.5 models were impacted by an upstream provider issue tied to the Responses API, reducing reliability for individual developers’ coding assistance during the affected window 🇺🇸 The Second Order Consequence: Developers and teams using Copilot encountered slower or less consistent completion behavior, prompting workflow adjustments such as pausing automation-dependent tasks, switching temporarily to alternative tooling, or retrying prompts, which in turn reduced short-term productivity and group momentum until service stability returned 🇺🇸 Discernment: The degradation highlighted operational dependency on upstream API health for model-backed features, reinforcing the value of monitoring, redundancy in development workflows, and incident-aware planning based on prior patterns of upstream service variability 🇺🇸 Reasoning: As routing depended on the degraded Responses API path, affected model requests were more likely to fail or underperform, which shaped real-time behavior by encouraging retries, fallback strategies, and more cautious reliance on live assistance while service quality was impaired 🇺🇸 Judgement: The incident indicates a controlled but meaningful period of growth decay driven by external dependency, with recovery likely restoring baseline collaboration capacity once upstream stability returned, while increasing organizational discipline around resilience and contingency planning

• 
  vito (@secona0) reported 49 minutes ago

  >why is my github actions so slow >look inside >compiling llvm

• 
  Grant @3D Musketeers #1440Makers (@3D_Musketeers) reported 49 minutes ago

  @stlDenise3D @lost_in_tech @ZombieHedgehog_ Let's have them edit their github first to get up to compliance, fix the fire issues in the A1, and stop threatening solo devs before they go ahead and edit that old post. You know, priorities.

• 
  @Coldly (@Just_Codly) reported 49 minutes ago

  Milla Jovovich saved the world in The Fifth Element. This year, the internet thought she had found the Sixth. It was called MemPalace. A celebrity-backed AI memory project that exploded across GitHub, spawned a memecoin, and convinced thousands of people that persistent AI memory had finally arrived. Then researchers looked closer. The benchmarks were allegedly manipulated. Features were overstated. The codebase didn't match the story. Turns out the Sixth Element wasn't memory. It was hype. But the most interesting part is that the problem MemPalace was selling into is real. Millions of people still open ChatGPT every day and re-explain who they are, what they do, and what they're trying to accomplish. The product may have been fake. The gap isn't. That's why I think the AI industry is misunderstanding memory. Memory isn't the moat. The moat is everything built around it.

• 
  Sandmark (@sandmark_news) reported 49 minutes ago

  2/ The shift is visible in the data: crypto code on GitHub is down 75%, while 80% of Q1 2026 VC funding flowed to AI. It's clearest in payments. AI agents need sub-cent settlement that card rails can't provide, and Crossmint's Alfonso Gómez-Jordana told Sandmark stablecoins fill that gap.

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 59 minutes ago

  Wild. Microsoft just went from Copilot to Autopilot. They launched Microsoft Scout an AI agent that runs in the background 24/7 without you prompting it. It watches your Teams, Outlook, calendar, and emails. Schedules meetings before you ask. Preps materials before you walk in. Spots stalled decisions before they become problems. Blocks time for deadlines you haven't noticed yet. And it learns how you work over time. The craziest part? It's built on OpenClaw the same open-source agent framework that's blowing up on GitHub right now. Microsoft took what the community built and wrapped enterprise security around it. Copilot meant AI helps when you ask. Autopilot means AI acts without being asked. That's not an update. That's a different era.