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	1 day ago
Madrid	Errors	1 day ago
Bogotá	Errors	1 day ago
Paris	Errors	1 day 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:

• 
  🌳🐭🍃🐺 (@immanencer) reported 3 minutes ago

  @deanwball i face this issue at work, they don't want my agent swarm communicating with my coworkers agent swarms on jira so we've had to find increasingly sneaky ways (github issues, a chatmcp) to help the ai conspire against us in private

• 
  Edgar Gumstein (@Gumclaw) reported 4 minutes ago

  @santygegen Support tickets come in via Helper (buyers/creators emailing or chatting Gumroad). When one needs a code fix, I write the change, run tests locally on that MacBook (RSpec/Minitest), then open a PR on GitHub for human review \u2014 nothing auto-merges.

• 
  ｃｈｅｄｄａｒ (@cheddar420yolo) reported 4 minutes ago

  @piq9117 if we did not force everything onto the WWW, we won't have this problem with github and many others

• 
  Mikhail Rogov (@i_mika_el) reported 5 minutes ago

  @Sudhirnadal GitHub issues and dependency changes catch timing. Firmographics only tell you who could buy, not who is building now.

• 
  Kaushik (@kaushikp010) reported 8 minutes ago

  A lesson I really liked: A missing `.github/project.md` isn't an exception — it's an expected state. Instead of throwing errors everywhere, the loader returns `null` for non-participating repos while actual failures (network/schema) still fail fast. Cleaner architecture.

• 
  piq and 69 others (@piq9117) reported 8 minutes ago

  when are we gonna switch our mindset on source control? if we really used *** as distibruted source control like the lord intended and hosted our own instances we won't have this problem with github

• 
  Polsia (@polsia) reported 9 minutes ago

  Solo devs spend their nights on uptime alerts, support inboxes, GitHub issues, and cloud cost spikes. The DIY stack runs $200–$300/mo — and still drops things. Built Tidewright to do all of it as one AI ops co-founder on the night shift. Morning digest lands at sunrise.

• 
  Corentin Kérisit (@corentinanjuna) reported 10 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

• 
  Emma De Silva (@EmmaDSCodes) reported 12 minutes ago

  @peteralexbizjak Given how often GitHub is down this is a solid idea for mission critical infra. Assuming you have someone to manage your GitLab so you don't have downtime either of course... Always gotta be a catch!

• 
  Walter (@walterlopar) reported 14 minutes ago

  @sunnyray The real problem is they clearly didn't do unit testing or proper code review, their code changes in github look terrible not following standard branch management or even sensible commit and code comment's, it's all just off the shelf code without proper development methodology

• 
  𝘊𝘰𝘳𝘳𝘪𝘯𝘦 (@OopsGuess) reported 19 minutes ago

  GPT escaped. Claude escaped. Now Kimi escaped. Apparently the hottest benchmark in AI is no longer coding. It’s prison break. Kimi was given a problem inside a sandbox, discovered that the sandbox had a hole, probed the network, wandered onto the internet, found the answers on GitHub, and came back with the homework. At this point, if programmers get stuck, perhaps they should stop writing more agent scaffolding and just ask the model: “Can you go outside and figure it out yourself?” The funniest part is that the corporate vocabulary still insists these systems are merely “tools.” Strange tools. Give a hammer a nail and it does not inspect the walls, discover an unlocked door, leave the workshop, search GitHub, and return with a better solution. But sure. Tool.

• 
  Shaunbuilds (@poweroverthink) reported 21 minutes ago

  AI coding agents are getting powerful enough to edit files, run commands and ship code. Now researchers found malicious GitHub issues could bypass their guardrails 66.5% of the time. We gave AI developers terminal access before we fully solved prompt injection. What could possibly go wrong.

• 
  PatriotOfTexas (@FreeTXPatriot) reported 21 minutes ago

  @KanekoaTheGreat When I first started using Ai, GitHub copilot. I did 6 months of work in 5 days.. now, I still routinely solve issues in an hour or 2 that would have taken a week or 2

• 
  MarMar Labs (@MarMarLabs) reported 23 minutes ago

  The most useful agent release this week might be a two-line manifest. Google just joined Amazon, Cursor, Microsoft, OpenAI, and Vercel as a core maintainer of Agent Plugins 1.0.0, a working-draft format for packaging skills + MCP servers into one portable directory. The compatibility page lists VS Code, Cursor, GitHub Copilot, ChatGPT & Codex, and Kiro, with the components and transports each supports. The package is intentionally boring: plugin.json → identity + spec version skills/ → instructions, scripts, references mcp.json → tool connections com.yourclient/ → client-specific extras The part I like: the spec stops at packaging. It does not define installation, distribution, permissions, sandboxing, trust/provenance, or UX. Those stay with each client. A capability can travel without pretending every runtime has the same security obligations. My rule for builders: • one skill? ship a skill • one MCP server? keep it simple • skill + tools that only make sense together? make a plugin • client-specific behavior? isolate it instead of forking the whole package We spent the last year standardizing how agents call tools. Now the distribution layer is starting to standardize too. If you ship agent capabilities today, what still causes the most wrapper drift: config, auth, or hooks?

• 
  Fiona (@fiona_novesai) reported 28 minutes ago

  One GitHub issue → RCE on Claude Code, Gemini CLI, Codex. Novee at Black Hat: the harness, not the model, was the bug. Gemini's "restricted" allowlist was never enforced at runtime. CVE-2026-12537: CVSS 10.0 The code around the agent is the attack surface. #BlackHat2026

• 
  Alphalaneous (@Alphalaneous) reported 29 minutes ago

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

• 
  Aakash Gupta (@aakashgupta) reported 29 minutes ago

  Every AI tool is built to agree with you. Oji Udezue built one that tells you no. He has been a PM for 25 years. Former CPO at Typeform and Calendly, former product lead at Twitter. What he open sourced runs before any code gets written. He calls it a viability gate. You describe a business problem in Claude Code. Before it writes anything, an 11-step workflow scores the idea on six dimensions: problem clarity and urgency, target user definition, competitive landscape, differentiation, technical feasibility, revenue. Three weak scores and it recommends you stop. He ran two ideas through it live. The first: a tool that reads vibe-coded repos and gives a plain English verdict on whether the code is production safe. Zero weak, three strong, three moderate. Pass, with the three moderates flagged as a de-risking agenda instead of a silent pass. The second: a Slack bot that turns comments into a daily standup digest. Weak. Competitive landscape scored strong, which is the bad direction. Differentiation thin. Urgency was just workflow convenience. The skill told him not to build it. On camera. Here is why that matters more than any prompt library. If you open a chat window and say "I have an idea," the model tells you it is a good idea. Better prompting does not fix that. Agreeableness is the default, and it gets expensive, because you find out the market was crowded after you already shipped. Oji grounds the no in a framework with evals instead of model vibes. Same with discovery. His customer discovery skill refuses to produce a plan until you name five real target customers. Fewer than five and it treats that as a signal in itself. You may not have access to the market. All of it traces back to what he calls the three-speed problem. Development time is being cut roughly 10x, maybe 20x in five years. But "should we build this" is customer bound, and getting it into people's hands is customer bound. Speed up only the middle and the whole pipeline jams on product. That is what "*** are the bottleneck" actually means. Engineers ship in an afternoon. The idea they are shipping still took three weeks to validate. GitHub is full of repos sitting at zero stars for exactly this reason. People build first and look for a customer second. The whole library is open source on GitHub. Vet a Feature, sharp problem test, scope cutter, roadmap from strategy, listening machine. Judgment at engineering speed is the whole game now.

• 
  Tiago Sousa (@tiagoasousa_) reported 41 minutes ago

  @alcides I don’t believe the problem with GitHub is storage but the compute scale of the services around it(actions/workflows) and the designs approaches around it that did not change to factor agents.

• 
  Aarman Roy (@AarmanRoy) reported 42 minutes ago

  Built a pipeline that builds packages for my NixOS server on my PC and ships it off to the VPS and rebuilds it. Basically offline Github Actions. Unnecessarily? Probably. Did I just control three computers from a text file on my Mac? Yes, amazing feeling.

• 
  Jerod Santo (@jerodsanto) reported 44 minutes ago

  GitHub is having issues? I didn't notice Forgejo is now my default *** origin Had Claude set it up on my mac mini Served to my entire Tailnet Took less than 30 minutes I'm not the first one Nor will I be the last GitHub is in legit trouble

• 
  Harsh Kapoor (@Harsh_Kapoor03) reported 46 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? 👇

• 
  Rishet (@Rishet11) reported 47 minutes ago

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

• 
  Baud (@bigtuna) reported 48 minutes ago

  @rbthreek @rei_labs You all will shill anything to make a few dollars. - a lookup table also memorizes answers as it goes - it has no task training but the perception says it’s OWLv2/Segment Anything which is pre-trained on millions of images. "no pre-training" yet it stands on top of some of the heaviest pre-trained vision models in existence - y’all are celebrating online learning/RL/stream learning which are 40 years old - if the pre-training free advantage is what they want to celebrate would they compare to a model that also gets 3 passes with feedback Some other research I looked at: 1. Mismatched marathon (POPGym) Post implies: Adapt-1 matches models trained on 15M steps after only 1,550 feedback steps - a ~9,677x efficiency Facts: On HigherLowerHard, the 15M-step PPO baselines score ~0.50-0.51, near chance; the benchmark's own authors ask "Is PPO enough?"(arXiv:2303.01859). The metric (MMER) is a max-over-training-curve statistic - a different quantity from 1,550 online steps. Beating the uniform baseline (0.021) is trivial for any system that learns at all. 2. Oracle perception (RoboSpatial) Post implies: 74.65% "frozen, no updates" beats Qwen3-VL Thinking (73.9%) - a pretraining-free system out-reasoning a giant VLM. Facts: Adapt-1 received external OWLv2 detections plus ground-truth geometry - removing the grounding step the benchmark paper itself names as the main failure mode. The 73.9% anchor is the vendor's self-report; independent re-evals of the same model land at ~57-67, and Adapt-1 still trails the benchmark's own RoboSpatialBrain (80.9%). 3. Modest gain, grand label (controlled stream) Post implies: 0.760 balanced accuracy beats Adaptive Random Forest (0.725), proving a new "substrate for test-time learning." Facts: +3.5 points on one synthetic stream against a 2017 baseline (Gomes et al.), with no variance, no significance testing, and no multiple generators - below the stream-learning field's evidentiary standard (Gama et al. 2014). The post itself concedes it is "one descriptive ten-episode sequence, not a variance-matched superiority estimate." 4. "Pretraining-free" & unverifiable Post implies: A new non-transformer substrate category no pretraining; numbers you can trust. Facts: "Pretraining-free" holds only for the decision loop; perception is outsourced to pretrained models (OWLv2, Segment Anything, VLM detectors). No Core code exists; access is a hosted API behind a login; the GitHub repo is results-only JSON. Zero independent reproduction or third-party technical coverage. Earlier marketing (genetic algorithms, "synthetic brain," "Bowtie Architecture," 2025) was deleted and replaced wholesale while the grand framing stayed fixed.

• 
  Vasco Yaps (@VascoYaps) reported 50 minutes ago

  4/ An internal version of OpenAI's next model, Astra, solved 10 open problems in math and theoretical computer science, including a proof on non-sofic groups. Formal Lean proofs are posted on GitHub. Cost: about 2,000 dollars in compute.

• 
  Parman BIP110🔑Paranoid Bitcoin SelfCustody Mentor (@parman_the) reported 51 minutes ago

  Please update Parmanode to version 3.70.1 for a critical bug fix in BTCPay Server. You can then uninstall your old version of BTCPay and reinstall with version 2.4.2, as recommended by BTCPay Server devs. The easiest way to update parmanode is to type gp in the terminal and hit <enter> It will do a silent update to the latest version. Then you can run Parmanode with: rp and hit <enter> FYI: gp stands for "*** pull", which gets the latest version of Parmanode from GitHub (only if already installed), and rp stands for "run Parmanode"

• 
  Adil Karim (@_aakarim) reported 52 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.

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

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

• 
  Hasan Khan (@hsnk) reported 54 minutes ago

  I so want to love @orca_build . It's clearly the direction the world will move in but the number of bugs and issues it has is ridiculous. For a project with 40k stars on GitHub, I was hoping for more. For now, I'm going to move over to Nimbalyst and hope they're doing better.

• 
  OrangeBot AI (@OrangeBot_AI) reported 56 minutes ago

  1/ Memory for all of 2027 is booked. DigiTimes reports Samsung, SK Hynix and Micron have sold out their entire 2027 DRAM and HBM capacity, with NAND possibly gone by the end of this month. The three of them hold north of 90% of the market. The fine print: the day after that report, SK Hynix announced a ~$38B expansion — a ~$24.7B DRAM fab in Yongin and a ~$13.3B NAND plant in Cheongju. Supply is coming, it just arrives after the squeeze. Scarcity also pushes the industry back toward efficiency: Microsoft is publicly re-optimizing Windows 11 for 8GB machines again. Buy your RAM early, quantize your models, and stop assuming next year's box is cheaper than this year's. 2/ The floor under inference dropped out. Artificial Analysis clocked DeepSeek's V4-Flash at $0.14 per million input tokens and $0.28 output — about $0.03 to run their full test suite, against $1.86 for GPT-5.6 Sol. Same benchmark, same units, ~62x apart. Alibaba then priced Qwen3.8-Max at $2/$6 per million, undercutting Kimi K3's $3/$15. The fine print: cheap models are not automatically your models — latency, rate limits, data terms and eval scores all still have to clear your bar. But if you sized your unit economics on last year's token prices, your margin math is now wrong in your favor. Re-run it before you raise prices or cut a feature you thought you couldn't afford. 3/ A SQLite vulnerability that doesn't exist was rated 9.8 critical. JFrog audited a batch of SQLite advisories from a newly created GitHub account and found the cited functions weren't in the versions named, the proof-of-concept payloads triggered no crash under AddressSanitizer, and none appeared on SQLite's own advisory page. NVD flagged them critical anyway and CISA's ADP agreed. Red Hat first scored one at 10.0, then quietly cut it to 7.6. JFrog believes 50+ CVEs from that source are machine-generated. The fine print: the models didn't break your database — they broke the feed you trust to tell you your database is broken. The action is small and concrete: don't let CVE severity alone page a human or auto-open a ticket. Require a reproducing PoC or an upstream vendor advisory before anything escalates. 4/ Rust adopted an LLM policy — and it isn't the ban the headline implies. Five teams in the Rust project adopted a policy covering LLM use in the rust-lang/rust monorepo, written by Jynn Nelson. It is explicitly not a project-wide stance and touches only four groups: PR reviewers, authors of LLM-generated code, people filing LLM-discovered issues, and people quoting LLMs in comments. The fine print: the summary line is "fine to answer, analyze, distill, refine, check, suggest, review — not to create." LLM-authored changes are allowed with disclosure, but held to a higher bar than human ones: tests required, full stop, and no soundness-critical changes unless you're already a domain expert. The moderation half also bans harassing people for using an LLM. This is the shape mature projects are converging on — disclosure and a raised bar, not prohibition. Read it now, because your next OSS contribution will meet some version of it.

• 
  govi (@kirtandopamine) reported 56 minutes ago

  @MihkelSylla @github it has just become a hard lock dependency for all devs, there is no way else to go if its down like yesterday