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 (67%)
• Sign in (20%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	4 days ago
Paris	Website Down	8 days ago
Saint-Paul	Website Down	9 days ago
Saint-Paul	Website Down	9 days ago
Mexico City	Sign in	9 days ago
León de los Aldama	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:

• 
  Eric Ventor (@ericvtheg) reported 2 seconds ago

  Github outage?

• 
  regent0x (@regent0x_) reported 3 minutes ago

  Anthropic CEO Dario Amodei on how they use claude internally: claude now writes 90% of their code and handles 77% of real github PRs, up from 5% a year ago a bug broke their whole training cluster, engineers chased it for days, they told claude "just poke around" and it found it in one prompt but the claude on your machine can't do this, out of the box it only reads files and runs terminal commands, no PRs, no database, no slack it's a genius locked in a room with no windows MCP servers are the windows, 4-6 of them in one afternoon turn claude from "writes code when asked" into "reads the failing PR, queries the db, posts the fix in slack" in one prompt most people bolt on 20 broken servers and wonder why claude got dumber the guide below has the exact handful that matter

• 
  Parth Patel (@parthmern) reported 6 minutes ago

  @Hiteshdotcom @subhra8640 yeh 100% agree but i did the same went to temp mail made new github ac and did login with it kind of same thing but agree that it can help with multiple dummy logins btw: new CN course on youtube is good one, i always watch while going to work on subway

• 
  Aseem Shrey (@AseemShrey) reported 6 minutes ago

  GitHub doesn't normalize signatures before verifying, so the mutated commit keeps its Verified badge. And because a commit hash includes its parent, changing one commit cascades new hashes down the whole chain. A ton of tooling assumes "this commit hash = this exact content, signed by this person." That assumption is wrong.

• 
  Jesse Showalter (@imjesseshow) reported 9 minutes ago

  My friends think I'm throwing a party. I built a full product workflow disguised as a game. Character assignment. Clue tracking. Suspect board. Host dashboard. Figma, Claude, GitHub, Vercel, Supabase. The stakes are real. Friendship stakes. If the app crashes mid-clue, I fix it in front of people who know where I live. AI didn't remove the pressure. It removed the excuses. What would you build if you stopped stopping at the mockup?

• 
  Noah Hein (@TheNoahHein) reported 11 minutes ago

  I opened a bunch of issues in OSS repos as part of a bounty program for an old job. You would comment in the issue and get assigned to it. The bounties were from 2-5k USD. So periodically I get random people replying to those GitHub issues trying to snipe people’s work it is hilarious. “I will do this bounty for $1k less and I already have the PR ready just assign it to me” I love the petty drama 😭😭😭

• 
  Rodrigo (@consolerod) reported 13 minutes ago

  claude and github going down every 40 minutes is the biggest argument for being able to ship software manually

• 
  ricky b (@rbranson) reported 18 minutes ago

  put kimi k3 on what i'd consider a "new guy joined the team" web dev task for my home label printer app, using kimi code. prompt: add the ability to queue multiple labels and then print them out chained together and then perform the final cut * only one reasoning effort level: cool * feels to be ~20TPS: uncool * kimi code has auto-approve: cool * auto-approved my /plan: 🤦 (1mo old open issue on github) * the plan was long and extremely technically detailed with code-level changes, no interactivity * wrote some tests, started up the server and did some curl checking * one-shotted it: nice * web UI changes followed existing styles fairly well, but nothing too clever * i liked that the default view only changed with a single button * didn't follow the repo instructions on how to start the web server * plan: 7m5s, execution: 14m12s * tokens consumed: input 3.6M output 34.7k total 3.6M (11% of 5h/2% of weekly) so k3 is really slow, makes pretty good UI, and writes pretty poorly.

• 
  a thousand eyes (@wittenberg0rca) reported 19 minutes ago

  @hydratedgorilla @github @vercel github outage

• 
  The Ramen Don (@RealRiddimHours) reported 22 minutes ago

  @GregoryGregman @rocksoverrocks @actualinc I guess that's true. I didn't really know what github did 9 months ago but through trial and error with ai assistance I'm able to make stuff now. Self teaching through AI has been doing wonders for me since 2023, its nuts

• 
  Tanish (@Tanishrajurs) reported 25 minutes ago

  They've shipped an MCP server any AI agent (Claude Code, Cursor, VS Code) can now search their full paper database, read PDFs, explore GitHub repos. Agents standing on 3M+ papers instead of guessing

• 
  adam (@usedexra) reported 30 minutes ago

  I swear GitHub only goes down when your on a time crunch.

• 
  Filip (@fristovic_) reported 30 minutes ago

  GitHub is down. AWS sending astronomical bills. Cloudflare bugging out. The end is near.

• 
  sgbett (@sgbett_614) reported 31 minutes ago

  @kristovatlas I have copilot enabled, and a skill /copilot-check that reads review comments evaluates them on merit then fix/resolve with comment. It iterates until nothing is left. Then i run /review fix (what should be) minor polish issues and kicks off a final /copilot-check loop. Not bullet proof but catches a lot of errors. Customer copilot-instructions.md for GitHub. The other thing that makes a big difference is closing the “defer” gap (Claude defers things but the only record is a comment in a now closed PR. I have it lean toward always fixing there and then unless there is a compelling reason for it to be a separate PR. If it must be deferred then it must get a new issue. Just lately I’ve been nailing down its proclivity to write comments instead of self documenting code. My code ran about 8% comments/code. Claude was putting out 48% comments. Horrendous. Telling it how to write code that doesn’t need commenting over hitting metrics to try and make sure it makes sensible decisions. We will see!

• 
  andrew (@Vavassor) reported 32 minutes ago

  @MrZing07 I agree but also I rarely see people actually submit issues to VRM on github. I see same with other software, folks complain privately for years instead of telling creators what they want. So any new effort folks need to trust them to listen, know how to contact, and help improve

• 
  Michael Carpenter (@wiggycorp) reported 39 minutes ago

  Dang. GitHub is down. Too bad, I guess users will have to wait for these updates.

• 
  م٣الع٤ (@m7l5_dz) reported 40 minutes ago

  @NoemiTitarenco We have less problem with our self hosted Gitea than with Github (we have to use it because a lot of AI features gravitate exclusively around Github...). I got shocked when the diff tool is buggy on Github. Sometimes we have to send the PR to Gitea just to read it properly.

• 
  paresh pisipati (@paresh_pisipati) reported 42 minutes ago

  You cannot deny the fact that Satya Nadella revived Microsoft when Steve Ballmer was pushing it down the Tech ladder. When he took over, Microsoft wasn't even in the cloud race. Over the last 12 years, he made master moves - Overhaul of Microsoft products (MS 365) - Github Acquisition - LinkedIn Acquisition - MS Teams becoming the standard chat app in offices - Expanding gaming division beyond console - MS Azure - 2nd largest Cloud Platform - Copilot packed with enterprise licenses to make it the go-to AI platform

• 
  Preston Thorpe (@PThorpe92) reported 43 minutes ago

  something crazy going on with github actions rn. totally down it seems

• 
  Rahul kumar (@ats1999_er) reported 49 minutes ago

  @GithubProjects I can't, because GitHub is down.

• 
  Feral (@feraltekk) reported 49 minutes ago

  Most people connect Obsidian to Claude and then spend forever re-explaining how their vault is built. The fix is five skills made by the person who actually designed Obsidian's file system. Claude follows the real rules instead of winging it. Five skills. Two commands to add them. From then on Claude loads them every time it touches a note. 39,000 stars on GitHub. Barely anyone is using it yet. And once Claude actually understands your vault, the loop can start. You have written the same idea three times this year. You do not know that yet. Your notes app does. A loop rereads the vault every six hours. Finds what repeats. Flags what was abandoned. Surfaces the note you forgot you wrote. You cannot see your own patterns from inside your own head. The loop does it now.

• 
  Will Hopkins (@illothy) reported 51 minutes ago

  @ellie_huxtable I think you jinxed it by saying nice things about GitHub, they went down again today

• 
  Steven Grant (@1stevengrant) reported 51 minutes ago

  @owenconti @laravel github had issues but those now resolved and my repo connections are now totally fubarred

• 
  Forgehausens 🏳️‍⚧️ 🇦🇺 (@The_HRforges) reported 52 minutes ago

  Eh "stealing code" isn't even really that real because most programmers I know will copy/paste **** from github if it means they don't have to figure out how to do it themselves. The problem with AI generated code is not the same problem as AI generated art.

• 
  Jacob Gadikian (@Senpai_Gideon) reported 52 minutes ago

  @bdowns328 Yes that's exactly the problem. It's just not all that great. GitHub keeps getting worse and worse but gitlab is still not better than GitHub

• 
  Data Value Consulting (@DVC_analytics) reported 54 minutes ago

  SWE-bench Verified: 500 human-filtered GitHub issues; a patch must pass the real repo's tests. Claude Mythos 5 leads at 95.5% (July 2026). Catch: many issues predate 2024, likely in training data. SWE-bench Pro (1,865 tasks, private repos) shows a steep drop from that number.

• 
  Adam Kranz (@adam_kranz) reported 54 minutes ago

  Torturing my programmer by making a series of GitHub issues that amount to "I want to make the website self aware"

• 
  atmen (@atmen189) reported 57 minutes ago

  Fed it a briefing on OpenClaw - the AI agent blowing up on GitHub right now. Got 9minutes of two AI hosts breaking down the $2K -$6K setup fees, security risks, and why it’s different from a regular chatbot. Sounded like a real podcast, not a summary.

• 
  Vatsalpandya333 (@Vatsalpandya333) reported 59 minutes ago

  A customer-reported bug should not create six different workflows. But today, it usually does. Support captures the issue. Engineering asks for context. Someone checks logs. Someone checks the latest deploy. The team searches GitHub. Slack fills up with partial updates. Then someone still has to explain what happened to the customer. @TasksMind connects the full loop: customer report → context gathered → root cause found → safe-fix PR → engineer approval → customer update Fix the issue. Close the loop. Keep the customer.

• 
  Sudo su (@sudoingX) reported 59 minutes ago

  now i'm running the harness fight i've wanted to run for a month. hermes agent vs openclaw, same model, same tasks, both pointed at a 3.9gb bonsai on a single 3090. lean vs bloated, head to head, and i post whatever happens. disclosure first, i contribute to hermes, so i'm not pretending i'm neutral. what i can do is make it a fair fight. upstream versions of both, same local endpoint, no fork tricks, and let the receipts talk. here's what's actually in each box. > hermes agent. a one-file agent loop, around 25 direct dependencies. it parses and repairs tool calls off many model families natively, which is the whole reason it reads what a local model actually emits. built for open weights from day one. #1 on openrouter by daily usage. > openclaw. thousands of typescript files, roughly double the dependencies. for years it leaned on the server to parse tool calls and only shipped its own repair recently, for a single format. way more github stars than hermes. built for the big api models, and it shows. now the honest part. i uninstalled openclaw months ago. my experience was that it was built for someone else's models, it choked on local, and the bloat made it slow just to start. but that was months ago and these things move fast. maybe they fixed the local story. maybe the parsers are there now. i'm not going to assume, i'm going to run it. that's the whole test. can either harness hold a tool-calling loop on a 3.9gb model without falling apart. one early tester says bonsai breaks on iteration, another says it tops agentic benchmarks. that split might not be the model at all. it might be the harness. this is what finds out. results coming. i'm not calling it early.