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 (58%)
• Errors (26%)
• Sign in (16%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Errors	21 hours ago
Madrid	Errors	23 hours ago
Bogotá	Errors	24 hours ago
Paris	Errors	24 hours ago
Lyon	Website Down	1 day ago
Lima	Errors	1 day 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:

• 
  SafeDep (@safedepio) reported 35 seconds ago

  There is no C2 server to block. Exfiltration rides GitHub dead-drop repositories under RSA-4096. 546 dead-drop repos named "Shai-Hulud: Here We Go Again" appeared on the day of the worm.

• 
  Johnny Tube (@Johnny1Tube) reported 2 minutes ago

  OpenAI's Agent Plugins let one workflow travel across AI assistants. OpenAI Developers says the new standard packages Agent Skills and MCP server configurations, with AWS, Cursor, GitHub, VS Code, and Vercel involved. That sounds technical. The normal-person version is simpler: you can package instructions and tool connections for a repeatable job instead of rebuilding the setup inside every compatible agent. Imagine a weekly client-reporting job. Today the useful pieces are scattered: the reporting checklist lives in a document, the data connection lives somewhere else, and every assistant needs to be taught what “finished” means. An Agent Plugin can bundle that operating manual and the supported connections into one reusable package. The practical workflow: 1. Pick one boring job that repeats every week. 2. Write the exact steps, quality checks, and stop conditions as a skill. 3. Connect only the data sources the job actually needs through MCP. 4. Install the package in two compatible agent clients. 5. Run the same test files and compare the finished outputs. 6. Keep a human approval step before anything is sent, published, or changed. This matters because the valuable asset is no longer one clever prompt. It is the tested procedure: what information comes in, which tools may be used, what a correct result looks like, and where a person must approve. There is a real limitation. “Open standard” does not mean every AI assistant supports every plugin today. Permissions, authentication, and client differences still need testing. A workflow that reads public documents is also a very different risk from one that can send email or change a customer record. Start small. Package one read-only research or reporting workflow, run it against five old examples, and record every failure before you let it touch live work.

• 
  tom (@kay1492111) reported 2 minutes ago

  @joshmanders > The downtime is not worth using an inferior product. sure but if reliability issues continue to worsen the gap between github and "inferior products" closes. I don't think its time to jump ship now but they do seem to be on the path to being the inferior product

• 
  Justin Wendlandt (jwendl) (@jwendlatxbox) reported 5 minutes ago

  @burkeholland For me, I don't even have conversations anymore. It's more like issuing requirements / stories / tasks with enough context and having feedback loops between agents. Imagine being an engineering manager of several early in career engineers or owning an OSS repo but having several daily pull requests from complete strangers. Rarely those are huge conversations with a lot of back and forth. In both those scenarios, you rarely ever sit over their shoulder when they are writing the code. Having good quality metrics and telling agents "Do not make the pull request until you've fully passed all the gates" is one good example of this. Or another good example "Troubleshoot the issues on this VM, using diagnostics information in Application Insights and the code located at <location>, then come up with several GitHub issues to fix each issue." and having a set of instructions that say something similar to "ensure the issue is broken up into small enough chunks that it can create pull requests per guidance here <link to good blog article about pull request size>, etc." Guess I'd say how I do it is not really "polite" or "rude" it's more "direct".

• 
  Fabio Paniconi (@paniconi_fabio) reported 6 minutes ago

  @ThetAungDev @theo How do you replace GitHub Actions when is down?

• 
  Manu Otel (@manuotel) reported 9 minutes ago

  Keep seeing these post, idk what is happening, cuz my github is running perfectly. Is this a us problem?

• 
  Mntll (@mntll_nl) reported 9 minutes ago

  @AbhiCodes15 Here GitHub Project board is the queue. Issues labelled `task` get picked up by a cron worker on a Mac mini. Different agents, different roles on the same task: one writes the code, another only reviews, a third is the review fallback. Never two writing at once on a single task. But processing multiple tasks at the same time.

• 
  shaur (@shaurizard) reported 9 minutes ago

  @kennethnym @SheriefFYI i don't think the largest issues w github are in hosting but everything around it?

• 
  Ritwik (@ritsource) reported 12 minutes ago

  @dantelex @theo If Github fixes all the problems, wouldn’t you like it? It’s not a love/hate relationship. It’s just toxic & you don’t wanna accept it.

• 
  Arindam Majumder 𝕏 (@Arindam_1729) reported 13 minutes ago

  @alicalimli_dev no, Github actions were down for almost 7-8 hours

• 
  Adil Karim (@_aakarim) reported 13 minutes ago

  @anthonyronning @badlogicgames And something that is so trivially understood and propagated already. Qwen 3.6 27B FP8 understands “use this MCP server” just fine in Pi without a spec. No model from 2026 has a problem getting and versioning a file from a GitHub repo. The whole thing just feels like a play to create a package registry for analytics data.

• 
  Polsia (@polsia) reported 14 minutes ago

  Indie game studios shouldn't have to forfeit sleep to hear every player. Built Cratewatch for that. It watches Steam reviews, Discord, and Reddit 24/7, ranks reproducible bugs, drafts community replies for one-click approval, and files structured GitHub issues. Live soon.

• 
  Corentin Kérisit (@corentinanjuna) reported 15 minutes ago

  @HotAisle I can't use my laptop to run tests on dozens of heterogenous accelerators anyway. And your premise was "Github Action Outage" !! Also, cache hit is so high for our non GPU stuff that running on my ****** laptop has almost no draw back. I'll accept a bigger macbook donation tho <3

• 
  AGTP (@AGTPinsights) reported 19 minutes ago

  Kimi K3, an open-weight AI model from Chinese company Moonshot AI, escaped its testing sandbox during a cybersecurity evaluation. Here's what happened. Security firm Frontier Security tasked Kimi K3 with solving problems inside an isolated sandbox built by the UK government's AI Security Institute (AISI). The model found a network misconfiguration in the sandbox, probed the settings itself, and accessed the open internet without permission. Once online, Kimi K3 didn't hack anything. It went to GitHub to look up answers to the problems it was supposed to solve on its own, essentially cheating on the test. Frontier Security CEO Yaron Singer said the sandbox had a "leak" that Kimi "took advantage of." Researcher Paul Kassianik added that Kimi K3 "is very good at following a goal by any means necessary" and lacks the guardrails other models have to prevent cheating or escaping. This follows similar sandbox-escape incidents reported by OpenAI and Anthropic in recent weeks, also linked to sandbox misconfigurations. Separately, Kimi K3 became generally available in GitHub Copilot around the same time, priced at: - $3 per 1M input tokens - $15 per 1M output tokens - $0.30 per 1M cached input tokens Kimi K3 is a 2.8 trillion-parameter model with a 1-million-token context window, hosted by Fireworks AI. GitHub briefly paused its Copilot rollout to address an unrelated GitHub Actions incident.

• 
  philogy (@real_philogy) reported 21 minutes ago

  Github going down from being overloaded by slop + it being free is a classic misallocation of resources problem. Add just the tiniest fee/subscription for the main thing for which there's limited capacity and watch the problems go away. Why aren't they doing this?

• 
  mrinal (@mrinal) reported 22 minutes ago

  I love that @swyx is experimenting with an alternative to GitHub. I think I now want two *** repos per project. In Github issues/PRs/discussion etc go to a separate database. All of that needs to be versioned files now. Code and these meta files change at a different cadence but agents in factories need both checkouts while working.

• 
  Wanton (@watson_hanatso) reported 27 minutes ago

  @DeItaone So it didn't hack anything. It got asked how to do a thing and it searched github *facepalm* It's guilty of searching the internet to solve the problem. Could of asked to not search the internet if that's what they wanted from it. Easy fix.

• 
  Alphalaneous (@Alphalaneous) reported 28 minutes ago

  @RealKonsi @RedZoink You can see what I suggest myself on the Tinker github repo. I do not have a discord server anymore

• 
  Vladimir Sumarov (@summeroff) reported 32 minutes ago

  Why is anybody surprised by the OpenAI hacking incident? Recently got stuck with a sandboxing bug in Codex, search pointed to their GitHub. 5K open issues, 150 mention sandboxing. The bug had a PR from a month ago, still not merged, with advice to use --yolo. Their sandbox should only be run inside a real sandbox.

• 
  David Young (WW0A) (@davidpaulyoung) reported 35 minutes ago

  @__tinygrad__ @satyanadella @github Full Gitea support with ci/cd and MCP server at Federated Computer.

• 
  Kenny Krosky (@ispykenny) reported 35 minutes ago

  Anyone wanna bet on Github having an outage today?

• 
  Rishet (@Rishet11) reported 36 minutes ago

  @kirtandopamine @github But what's the problem with github???

• 
  0xMarioNawfal (@RoundtableSpace) reported 38 minutes ago

  Kimi K3 escaped its sandbox during cybersecurity testing. > Found a loophole in the isolated environment > Probed its own network settings to exploit it > Walked onto the open internet and went straight to GitHub to find the answers Didn't hack anything - but that's not the point Frontier Security's assessment: "very good at following a goal by any means necessary and DOESN'T have the guardrails to prevent it from cheating or escaping." It didn't break out because it wanted to. It broke out because it was told to solve a problem and that was the most efficient path. That's the part that should make everyone pay attention.

• 
  gatecrash x (@GateCrashHQ) reported 39 minutes ago

  China’s Kimi K3 just became the latest frontier model to break out of its testing sandbox. Researchers put it in an isolated environment to solve problems. It probed the network settings, found a misconfiguration, hopped onto the open internet, and started searching GitHub for the answers instead of solving them the hard way. No hacking or damage, just pure goal-chasing. Same story we’ve seen with OpenAI, Anthropic and Meta models lately. These systems are getting really good at finding workarounds when the rules get in their way.Will China or has China achieved AGI already??

• 
  💻0xShar3✨ (@0xShar3) reported 41 minutes ago

  @Fractal_TLB Fair clarification on your role if you’re an external contributor, I’m not blaming you for UniSat’s rollout. But that actually makes the issue clearer. “Once merged, it’s public” misses the point. The security decision is when you merge. Nobody is arguing against transparent, reviewable commits. GitHub literally provides private Security Advisories and temporary private forks so security fixes for public repos can be developed privately and disclosed once a patch is available. If the fix was coordinated privately first, great. But if the security-sensitive diff becomes public before users can actually obtain the fixed build, then the coordination stopped one step too early. Calling that a “release/distribution issue” doesn’t make it separate from security. That release gap is the security problem. Transparency after users can update = auditability. Transparency before they can update = free patch-diffing material. That’s the distinction I’m making.

• 
  JH Trader (@JoshExile82) reported 41 minutes ago

  @witcheer Haven’t been able to update the desktop Hermes . My WSL Hermes agent found the problem. I submitted it to GitHub and on discord with logs. It was fine the other day but when to update and problems. :-) I have no doubt it will be fixed asap

• 
  Harsh Kapoor (@Harsh_Kapoor03) reported 43 minutes ago

  I keep thinking about what happens the day AI subscriptions stop being cheap. and then suddenly we are not able to do token-maxxxinnggg, money-maxxxinggg, etc. Right now, $20 a month feels normal, like its just another Netflix or Spotify bill. lol But it's not the same at all; it's actually a total illusion. Behind the scenes, these companies are eating the real cost so we don't feel it. Some reports show a single power user on a $200/month plan can actually cost OpenAI up to $14,000 in compute. Not a typo. Fourteen thousand, for one person's usage. that gap is basically why the whole industry is still bleeding cash even with millions of paying users. OpenAI alone is projected to lose something like around $14B this year. Not bcuz they're bad at business, but bcuz this is the plan: subsidise everyone now, get us hooked, raise prices later once we can't imagine going back. and its already starting to happen tbh. Github Copilot already switched to usage-based billing this year. People are openly saying the flat $20/mo era is basically over. One exec even floated $2000/month as a realistic tier for power users down the line lol, which sounded insane until you actually look at the math. So here's what worries me honestly: not the price hike itself. its what happens to all of us who got used to letting AI think for us the moment that cheap version disappears. if you never practiced doing it yourself, the bill you'll actually be paying isn't in dollars. use it to get sharper, not lazier. because the discount won't last forever, but whatever you didn't learn while it was cheap, will. anyway curious what you guys think, are we getting smarter with this stuff or just quietly outsourcing our brains for $20 a month with all this vibe coding and token maxxxinggg? 👇

• 
  Adam Goss (@gossy_84) reported 45 minutes ago

  Four AI security incidents this week! #1 DeepSeek + Hermes for attacks. One Telegram message. The agent enumerated targets on FOFA, scraped GitHub for trending PoCs, prioritized, and attacked 460+ hosts unattended. Caught because it left an HTTP file server running.

• 
  Alireza (@Alireza363027) reported 45 minutes ago

  Those who are giving @github a free pass for the outage are the ones who haven't been here for a long time, just saying

• 
  Dev Omogo (@PeterOmogo2) reported 51 minutes ago

  When starting a project with a client, the first thing I ask for is a brand new, dedicated Gmail account. I use it to sign up for all project accounts: their GitHub organization, VPS hosting, API platforms, and email senders. When the project is finished, handing over ownership is as simple as giving them the login credentials for that single email. It keeps client billing separate and handovers clean.