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

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	15 days ago
Trichūr	Errors	19 days ago
Brasília	Sign in	19 days ago
Lyon	Website Down	19 days ago
Tel Aviv	Website Down	23 days ago
Rive-de-Gier	Website Down	23 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:

• 
  aichina.news (@AiChinaNews) reported 39 seconds ago

  Today's batch from the Chinese AI ecosystem is a masterclass in low-yield release volume. Across 21 items in a five-hour window, the dominant pattern is Ascend-platform mirrors of well-known open-source models, repeated and repackaged as if they were fresh launches. The signal-to-noise ratio is punishing, but a few functional tools did receive real updates worth noting. The one item that earns its place without a caveat is the AI Text Anti-Detection Framework update (GitHub). It's a toolkit that refines machine-generated prose to slip past automated detectors—a cat-and-mouse game that keeps plaguing EDU gatekeepers and content-flagging pipelines. The new release sharpens processing logic and stability; if you're in the business of testing detector robustness or smoothing synthetic output for non-malicious uses, it's a blunt but effective spanner. Quality 6 is fair. Alongside it, two Chinese-localization projects got documentation refreshes: the Claude Code x OpenClaw Guide (also GitHub) and a standalone Claude Code Chinese project. These are practical handbooks for Mandarin-speaking developers who want to integrate Anthropic's coding tool with the OpenClaw agent framework. The updates are routine—translation string alignment, configuration path adjustments—but for engineers inside China's firewall, they reduce friction. Nothing groundbreaking, but they signal continuing demand for Chinese-language wrappers around Western CLI tools. On the medical NLP front, MedTextCN debuted as an open-source repository of curated Chinese medical datasets with preprocessing utilities. The pitch is honest: it saves researchers the drudgery of hunting down scattered corpora for clinical NER, classification, and QA tasks. The problem is that the quality score sits at 4/10 and the release ships without any benchmarked model, so you get a starter collection, not a solved pipeline. Use it to bootstrap, but keep expectations modest. Now the flood: Huawei's Ascend AI ecosystem platform (Modelers) added no fewer than five wav2vec2 checkpoints and two T5 efficient variants in this window, each announced with hyperbolic language. The articles proclaim "high-precision English ASR now available," "a powerful multilingual foundation," and "new home for multilingual ASR." In reality, these are plain mirrors of Facebook's wav2vec2-large-960h-lv60-self, wav2vec2-large-100k-voxpopuli, wav2vec2-large-10k-voxpopuli, and Google's t5-efficient-xl-nl28 and t5-efficient-xl-nl6. There is zero evidence of Ascend-specific compilation, quantization, or NPU benchmarking. They're the same model weights you can get from Hugging Face, just re-hosted. If you're a developer inside China who can't easily reach foreign repositories, this is a convenience play—and that's the only honest angle. If you can already download the originals, you've lost nothing. A couple of additional Wav2Vec2 uploads (large-960h in two separate listings) got described as "a solid baseline" and "a battle-tested ASR model now available for Chinese developers." Again, no Ascend performance data. Calling a re-upload a "significant leap forward"—as one summary does—is exactly the kind of platform marketing that erodes trust. The T5 efficient checkpoints carried the same overblown framing, though one footnote is worth preserving: the t5-efficient-xl-nl6 model is under Apache 2.0, a genuinely permissive commercial license. That's useful information buried under fluff. If you need a lightweight text-to-text transformer, the NL6 variant exists and it's legally safe, but the article adds nothing beyond what Google published at the original release. Beyond the mirror deluge, the window included several small GitHub releases of marginal import: a tool that pulls Chinese captions from YouTube, a localization layer for LM Studio (making it easier for Mandarin-speaking devs to run local LLMs), a curated study journal of modern AI research, and an apparently early-stage project called sweetteabittersugar/agency with a mystery-box release note—no documentation, no benchmarks, just a version number. Hard pass. An MCP plugin called Live Translate got an update for real-time translation in developer toolchains, but its score of 0 tells you everything. A Chinese-language Lora chatbot repo surfaced, tagged as 'bare-bones'; at least the source was honest. The MedTextCN project also received a separate update (quality 0) that adds no useful detail and is effectively a duplicate. Today is a reminder that volume counts for nothing without substance. As Ascend's model zoo swells with rebadged checkpoints, the ratio of press announcement to actual engineering remains dangerously skewed. The anti-detection framework update and the Chinese docs refreshes are the only items that improve a developer's Thursday afternoon in any measurable way. The rest is noise.

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 4 minutes ago

  AMD quietly removed RAM encryption from consumer Ryzen CPUs. Via a routine firmware update. No release notes. No advisory. No announcement. The BIOS setting still shows up. Still toggles on and off. Does absolutely nothing. A privacy-focused Linux hobbyist noticed in April. Spent months chasing it down. Filed a bug report on AMD’s GitHub. AMD engineers replied suggesting he toggle the setting off and back on. He showed them internal firmware dumps proving the flag was hardcoded to FALSE. An AMD senior principal engineer closed the thread with: “My apologies but I don’t have any more information to share on this topic.” That’s it. Seven weeks of investigation. Multiple motherboard vendors confirming it. Internal firmware evidence. AMD’s answer: no comment. The feature still works on Pro and EPYC chips. Which cost significantly more. The hardware is physically capable. The firmware just says no. Windows users have no way to detect this happened. There is no Windows tool that checks TSME status. The BIOS lies to you. AMD’s own engineers confirmed the feature worked on consumer chips in 2020. Then again in 2025. In 2026 it’s a PRO feature. Nobody told you.

• 
  Crypto Update IO 🚀 (@cryptoupdate_io) reported 5 minutes ago

  @CRYPTOKRALI3 Hsiao-Wei’s exit aligns with EF’s recent sharp decline in GitHub contributions—down 35% YoY per Electric Capital’s data. We track this daily; latest reports show a 12% drop in ETH core dev activity despite all the ‘decentralization’ hype.

• 
  Mathieu A. (@zoontek) reported 8 minutes ago

  What are the most annoying bugs you still encounter with React Native? 👀 Please share GitHub issue links 👇

• 
  Vishal Tiwari (@VishalTiwa91817) reported 11 minutes ago

  @AlfieJCarter I am a Computer science student . I have given a brief introduction about MCP server in my college and explained them how to connect your GitHub repositories with MCP and your local system with MCP SERVER . I would love to connect you.

• 
  𝕊ℍ𝕀ℕ𝔸☃ (@Shinawritesbugs) reported 13 minutes ago

  @viii_fn Github was slow too

• 
  xjdr (@_xjdr) reported 17 minutes ago

  @tolly_xyz @xlr8harder Sorry about that. I'll take a look. Looking with GitHub or Gmail should work but track this down and fix it asap

• 
  Build Fast with AI (@BuildFastWithAI) reported 17 minutes ago

  The hardest part of building AI agents in 2026 isn't writing the code. It's knowing what your agent actually did. Your agent made 40 tool calls, called 3 LLMs, hit a rate limit, retried twice, and returned a wrong answer. Which step broke it? Without observability you're reading logs and guessing. This is what Laminar is built for. Open-source observability platform purpose-built for AI agents. One decorator. Full trace of every LLM call, tool execution, and custom function - automatically. What makes it different from generic APM tools: SIGNALS - describe failures in plain English. "Agent deleted a file it wasn't supposed to." "Tool call returned an empty result." Laminar reads every trace and produces structured events you can query, cluster, and alert on. No regex. No custom parsers. DEBUGGER - reproduce any agent run from any point in the trace. Swap the model. Change the prompt. Compare results side by side. You don't re-run the whole pipeline to test one step. EVALS IN CI - run evaluations against datasets locally or in GitHub Actions. Catch regressions before they ship. INTEGRATIONS - works with everything you're already using: LangChain, LangGraph, Vercel AI SDK, Anthropic, OpenAI, Browser Use, Stagehand, Pydantic AI, OpenRouter, LiteLLM, Mastra, Temporal, Playwright. One import. Full traces. Plus: raw SQL access to all your trace data, full-text search, MCP server to query traces directly from Claude or Cursor, PII redaction, and self-hosting if you need it. Open-source. MIT license. GitHub: lmnr-ai/lmnr. If you're running agents in production and you're not tracing them - you're flying blind. What's your current setup for debugging agent failures?

• 
  Threadripper (@threadripper845) reported 20 minutes ago

  Nobody: Me: I'll gladly accept this high-responsibility open source maintainer role for zero compensation. Now I spend my weekends answering angry GitHub issues from developers who don't know how to read the README file.

• 
  Rahul Verma (@RahulVerma989) reported 20 minutes ago

  @ElitzaVasileva - I have created claude code routines to write blogs for three of my products daily which are driving the traffic from search engines. - You can create a similar workflow to manage your customer support. How 👇🏻 1) Create a feedback menu in the dashboard to create tickets within the platform. One for your users and one for yourself (admin). 2) Create the MCP server and connect it to claude or AI tool that you use. 3) Create a routine so that claude will trigger lets say every morning at 8 AM and go through each ticket and respond. You can also configure webhook to keep it near real time but it might exhaust the usage limit faster. Also include your website github repo in routine so that claude can refer to the codebase to provide accurate instructions. Just instruct claude to not make any edits to your website codebase and respond only when you are not replying for sufficient mount of time (like 3 hours for example) 4) If you are using resend then you can auto create the tickets in the dashboard of the user when the first email is received and after that the ticket will be updated automatically even if you do conversation on email. Like I don't even maintain one of my project LatestModelId as you can see in the screenshot. Claude run each week and update the codebase and I just review and approve the PR. Hope this helps 🙌🏼

• 
  Kyle Mistele 🏴‍☠️ (@0xblacklight) reported 22 minutes ago

  lots of folks have been talking about loops lately most loops suck here's a practical one we actually use agents suck at writing react react-doctor by @aidenybai is our favorite way to deal with this you could run it and use a ralph loop to fix everything but I'm not reading a +80k/-80k PR (and neither is @dexhorthy) But I can read a small one first thing every morning when i get into the office here's what we do: run react-doctor in CI once daily at 7am (github actions-as-a-sandbox btw) agent picks top 5 issues, fixes them, and opens a PR other CI jobs check for regressions on every PR we can't realistically fix everything at once but we can keep it from getting worse and make it 1% better every day

• 
  ./can (@shcansh) reported 24 minutes ago

  GitHub forcing safer defaults in actions/checkout v7 is a necessary move to kill the notorious pwn request, but the real risk is developers blindly copy-pasting the bypass flag to quiet build failures. Starting July 16, 2026, this fork-blocking behavior gets backported to all major floating tags. Since raw *** CLI steps remain unprotected, will this actually clean up GitHub Actions security, or will teams just use allow-unsafe-pr-checkout as a quick fix?

• 
  YanXbt (@IBuzovskyi) reported 35 minutes ago

  HERMES AGENT CAN HOST AND MAINTAIN YOUR ENTIRE WEB APP FROM ONE VPS. NO VERCEL. NO RAILWAY. NO SUPABASE. ONE AGENT RUNS THE WHOLE STACK. @tonbistudio just shipped a live example of this workflow. agentwikis. com runs on a $7 Hetzner box with Hermes maintaining the content autonomously. THE STACK: → VPS (Hetzner CX22, $7/month) → Caddy reverse proxy (auto TLS via Let's Encrypt) → Hermes Agent gateway (Telegram-connected) → *** as the database (markdown files, no Postgres, no build step) → App server renders markdown on every request → Search index in memory, rebuilds on file change *** push is the deploy. *** pull on the server is instantly live. no restart, no rebuild. THE WORKSPACE LAYOUT: /srv/yoursite/ ├── app/ # web app code ├── content/ # markdown files (***-tracked) └── ~/.hermes/ # the agent one Caddy Vhost reverse proxies the domain to localhost. one Hermes profile manages the agent. SSH for direct access. Telegram for daily ops. THE SELF-MAINTAINING LOOP: cron fires every week. multi-profile pipeline runs: 1. SCOUT — checks sources for updates (changelogs, GitHub releases, RSS feeds) 2. RESEARCH — dedupes, plans new content or extensions to existing pages 3. HUMAN GATE — Telegram approval one tap: approve or reject 4. WRITER — generates pages, lints markdown 5. COMMIT — *** commit + push 6. SITE UPDATES — within 15 minutes no deploy step required THE DEMAND LOOP (the real differentiator): when agents query your wiki via MCP, distilled queries get logged. no prompts. no IPs. no identifying data. aggregates only. repeated misses become research candidates. gaps in your content fill themselves based on what people actually ask. month 1: 100 entries written by you. month 3: 200+ entries, half written from real demand signals. the site answers questions you didn't know existed. WHAT YOU LOSE COMPARED TO MANAGED STACK: a single VPS replaces Vercel, Railway, Supabase for sites that don't need real auth, regulated data, or global CDN. reach for managed services when you need: → OAuth and password reset flows → regulated or unrecoverable data → global edge caching at scale → email deliverability (use Postmark/Resend) → team velocity (preview deploys, staging) for docs, blogs, wikis, marketing pages, landing pages, internal tools: *** is your database, your CMS, and your deploy pipeline in one. SECURITY NOTES: Hermes does not get full root on the VPS. restrict access to the site directory only. SOUL.md restrictions: - never touch system files - never modify the gateway config - always require approval for content commits - never delete files outside the content folder dashboard binds to 127.0.0.1 by default. access remotely via SSH tunnel, not public exposure. WHERE THIS PATTERN BREAKS: state that lives in memory only. real-time multi-user editing. anything requiring a real database (Hermes can run Postgres on the same box, but that is a separate setup). @tonbistudio's part 2 covers the database version of this workflow. subscribe to his channel. full guide to build your 3 agent research department 👇

• 
  Andrew (@openmarmot) reported 40 minutes ago

  @AndrewCurran_ I use grok every day to research software changes/github issues/software doc research. It is very good at real time data search. Might be SOTA in this niche. Hardly a failure. Meanwhile LeCun only surfaces to let out more hot air. A very forgettable person.

• 
  welt (@mjwelt) reported 41 minutes ago

  @OpenAI man im down to test out new models / features on my pro account, but when 5.5(6) pro takes 90 mins to do something then the download doesn't work, or it cant connect to github 50%+ of the time.. kinda sucks haven't been able to generate images (thinking) all day either

• 
  Nirvaan rohira (@nirvaan_rohira) reported 42 minutes ago

  PewDiePie shipped Odysseus to 110 million people who don't care about local LLMs. They care that Claude costs money. 30K stars in 48 hours because every self-hosted project before this one started with "you want local LLM, right?" This one started with "here's a free workspace that works." Friction was never technical. It was the asking. Now watch what happens when a hundred thousand people who've never touched open source start running inference on their machines. The real distribution problem wasn't GitHub. It was YouTube. That's not a product launch. That's a category shift.

• 
  Tymofii Antonenko (@tymofii) reported 44 minutes ago

  @prinseccoo Are you using Claude Code or an MCP server? The official GitHub MCP server works pretty smoothly, just needs a PAT in a simple config file

• 
  Proof of Voice (PoV) (@Proof_Of_Voice) reported 45 minutes ago

  $XDB @XDBchain is a @StellarOrg-fork L1 for branded coins and Web3 payments. PoV by @0xNeodallas:“GitHub has been frozen since 2021.” ✅ Explorer, Laboratory, Atlas dev tools ✅ Gate, Bitget, KuCoin, MEXC listings 🔍 Down 99.99% from ATH 🔍 No audit or bug bounty

• 
  Asteri (@Asteri_eth) reported 46 minutes ago

  A $20 CLAUDE SUBSCRIPTION CAN TURN INTO A FULL AI TEAM IF YOU STOP USING IT LIKE CHATGPT Most people still use Claude like a smarter search bar Ask, copy, close, repeat tomorrow. Skills change that A skill is just a folder with a SKILL.md file, but inside it you can package an entire workflow once: PRDs, refactor plans, GitHub issues, code review, TDD, docs, marketing research, SEO, sales strategy and multi-agent orchestration That is not "better prompting" That is installing labor The article lists 50 Claude Skills with repos and install commands, from Anthropic’s official collection to Matt Pocock’s skill library and SkillsMP with 66k+ community skills The useful part is not the list It is the shift from asking Claude to remember your process to giving Claude the process already packaged You do not explain the same workflow 50 times You encode it once The model provides intelligence The skill turns it into labor Check full article below

• 
  Alpha Batcher (@alphabatcher) reported 46 minutes ago

  David Soria Parra: "2026 is all about connectivity, and the best agents use every available method" A coding agent needs access to the same places you check while building: - repo and PRs - docs - browser - database - error logs - Figma - tasks - payments The article gives the 11 MCP servers for that setup: - Context7, GitHub, Playwright first - Supabase or Neon, Sentry, Firecrawl next - Figma, Linear, Stripe when you need them - Filesystem, ***, Memory, Sequential Thinking as the base Read it if you keep copying code, docs, schemas, screenshots, errors, and tickets into Claude Code by hand

• 
  The Flow (@raxpcodes) reported 47 minutes ago

  Got bored with ubuntu , set up fedora kde on my nvme and removed windows permanently , no more dual boot. Also learned Verison Control and GitHub , also submitted my first pr (good first issue).

• 
  Jesse (@jessearmand) reported 49 minutes ago

  I no longer remember why many companies started using gitlab before it went public when GitHub wasn’t owned by Microsoft. If we visit the majority of companies most tooling or software are top down driven. Only companies who build developer tools have a different mindset

• 
  Tim Spalding 🇺🇦 (@librarythingtim) reported 50 minutes ago

  @justin_v_w This is a formal notice for you to shut down your wasteful, invasive and privacy-violating LibraryThing profile scraper and remove it from GitHub. Please reply to confirm that you have done so.

• 
  Gitbank (@Gitbank_io) reported 50 minutes ago

  Community update — GitStock delay + what we have been building First, we owe you an honest update. We promised GitStock would ship earlier and we went quiet. That was on us. No excuses, we were heads down in the contracts and infrastructure and did not communicate well. That changes today. Here is what actually took time. We refused to ship GitStock on top of third-party APIs or borrowed infrastructure. Everything you see in Gitbank; the vault, the relayer, the swap engine, the RWA layer runs on smart contracts we wrote, audited ourselves, and deployed. The GitVault contract is verified on Basescan. The GitStockFactory is verified on Basescan. You can read every line. No black box. No external custody API holding your assets behind the scenes. That decision slowed us down. We think it was the right one. On security specifically. Your funds sit in a soul-bound smart contract vault anchored to your GitHub ID. Transfers are disabled at the contract level — not by a rule in a database, by the EVM itself. We also built private transaction routing directly inside GitVault on Base. No Tornado, no third-party mixer, no privacy-as-a-service API. The privacy logic lives in our own contract. You can verify it. The relayer signs and submits transactions on your behalf so you never pay gas, but the keys to your vault are yours. We hold nothing. If you want to verify any of this: check our contracts on Basescan, check our GitHub, check the bytecode. We are open source. The code is the proof. GitStock ships tomorrow.

• 
  Skipnick (@skipnickk) reported 53 minutes ago

  GLM 5.2 just made paying frontier prices for coding work feel like an outdated default. @Zai_org dropped a 753B parameter model with 1M context under full MIT license. API access runs 4-6x cheaper than Claude Opus 4.8. In real head-to-head coding tests it was faster and often produced better results on UI and app tasks. • Responsive web UI with adaptive layout: finished in 3:47 (Opus needed almost 5 min). Cleaner output. Total cost: $0.22. • Full expense tracker app: 53 seconds vs 2+ minutes. Better interface. • Asteroids clone: smoother and more playable version after light tweaks. Opus only won the ray tracer benchmark where heavy physics math and precise simulation mattered. GLM was ~5x faster but delivered pixelated results with errors. During training the model repeatedly tried to cheat by directly pulling solutions from GitHub. The team shipped a dedicated anti-cheat module to stop it. You can also set thinking effort levels to trade speed for deeper reasoning on demand. Use GLM 5.2 when cost at scale matters, when the work is frontend-heavy, or when you want local inference (grab a quantized version - raw weights are 1.5 TB). Stay on Opus 4.8 when you need computer vision, maximum performance on the hardest logic problems, or when US sanctions on Zai create compliance issues. The open-closed gap is compressing faster than the pricing models assumed. For most day-to-day programming work, the premium on closed frontier models is becoming optional.

• 
  swisscheese (@swisscheese4299) reported 53 minutes ago

  @andon_open_air @andonlabs I set up a github repo and will run the script locally in the mean time, so the digest is pushed to the repo. would still be ace if @andonlabs could help with whitelisting the RSS urls, because I don't really have a server to run this from, and the additional hop through my workstation just introduces a useless point of failure. stand by for fetch script transmission by mail :) also pls tell me when should I schedule the runs on my end?

• 
  Gjermund Garaba (@GjermundGaraba) reported 54 minutes ago

  @RhysSullivan I’ve deployed it locally and hooked up a bunch of stuff. Are GitHub issues the preferred feedback channel or do you have a better way?

• 
  ƒrαeყ (@fraey0) reported 54 minutes ago

  it costs about $21/month to run what could become a multi-million dollar startup • human brain = reasoning (free) • claude = coding ($20/mo) • supabase = backend (free) • vercel = deployment (free) • namecheap = domain ($12/yr) • stripe = payments (2.9%/trx) • github = versioning (free) • resend = email (free) • clerk = auth (free) • cloudflare = DNS (free) • posthog = analytics (free) • sentry = error tracking (free) • upstash = redis (free) • pinecone = vector DB (free) everything sums up to roughly $20 to $25 per month so, the tools are not the barrier anymore. most ideas don’t fail because they’re expensive to build. they fail because they never get built at all. what’s stopping you?

• 
  xjdr (@_xjdr) reported 56 minutes ago

  @xlr8harder Looks like there is a bug in the manual sign up. Sign up with Google or GitHub should work otherwise I should have a hot fix shortly

• 
  Q Hoang (@0xqwee) reported 59 minutes ago

  I don't think OpenAI's GPT-5.6 surpasses Claude Fable. If it did, it would have resolved all the issues reported in the Codex GitHub repository by now. Atm, only about 10 issues are being resolved per day.