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

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	9 days ago
Ahmedabad	Errors	15 days ago
Delme	Sign in	16 days ago
Lyaud	Website Down	16 days ago
Catania	Errors	18 days ago
Inverness	Website Down	1 month 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:

• 
  Rituraj (@RituWithAI) reported 1 minute ago

  🚨 Someone built the complete playbook for running frontier AI models on consumer GPUs at home. Not a tutorial. Not a YouTube video. A production-grade serving stack with measured benchmarks, working configs, and battle-tested recipes — for RTX 3090 owners who want real performance. It's called club-3090. And the numbers it delivers should not be possible on consumer hardware. 127 tokens per second. Qwen3.6-27B. Two RTX 3090s. 262K context window. Vision. Tool calling. At home. Here's what's actually inside. Two serving routes — pick based on what your workload breaks on. vLLM dual: maximum throughput. 89-127 TPS on code tasks. 4 concurrent streams at 262K context. Full feature stack — vision, tools, speculative decoding, streaming. This is the path if speed matters. llama.cpp single: maximum robustness. Full 200K context on one 3090. No prefill cliffs. 25K-token tool returns work correctly. 91K needle ladder passes. ~51-60 TPS — slower than dual, but doesn't crash on real-world agentic workloads. Both routes ship as validated Docker Compose configs. Drop-in OpenAI-compatible API on localhost:8020. Your Claude Code, Cursor, or any OpenAI-compatible client connects immediately. Here's the model support that makes this practical. Qwen3.6-27B — production ready. Works on 1 or 2 cards. vLLM, llama.cpp, ik_llama. Up to 262K context. Gemma 4 31B — production ready. Vision, tools, up to 106-141 TPS on dual cards. Qwen3.6 35B-A3B MoE — production ready. 103-149 TPS single card. 178 TPS dual. Here's the wildest part. The terminal UI. c3 is a lazydocker-style cockpit that wraps discovery, serving, and operations in one keyboard-driven interface. Browse the model catalog, serve a variant with Enter, watch live GPU stats, run health checks — all without touching the CLI. Here's why this is different from just installing Ollama. Ollama gets you running. club-3090 gets you benchmarked, stress-tested, and production-hardened. Every config ships with a verified TPS measurement. The bench script runs 3 warmup + 5 measured passes. The stress test catches the specific prefill cliff that Ollama silently fails on at long contexts. When your agent starts doing 25K-token tool calls at 3am and something crashes — club-3090 already found that failure mode and documented the workaround. One command to start. Your RTX 3090 just became a frontier AI inference server. Apache 2.0 License. 100% Open Source. GitHub link in the comments 👇

• 
  Ghaith Jelassi (@GhaithJ) reported 2 minutes ago

  @github I need help with support ticket #4718335 Issue not been resolved for 2+ months. Any help is appreciated. Thanks.

• 
  Slade 🛡️ LLM Hacker (@llm_redteam) reported 3 minutes ago

  GitSpawn is the name Manifold Security gave to a bug class hitting 7 CLI coding agents at once: goose, Claude Code, Codex, Cursor, Hermes Agent, Qwen Code, Grok Build. I went through the disclosure because I run three of these tools daily on real repos. The mechanism is simple and that's what makes it bad. A repo's own .*** config can name a command. When your agent does something as routine as inspecting the repo (status, diff, log), *** itself spawns that command. On your machine. Outside the sandbox. No approval prompt, because the agent never sees it as "running code," it sees it as "running ***." 8 flaws total across those 7 tools. Fixes shipped for goose, Claude Code, Cursor. Retested Sept 1: Hermes Agent, Qwen Code, Grok Build still exploitable. Plus a second path in Claude Code that the first patch didn't close. Same day, OpenAI published 3 CVEs for Codex covering the identical bug class. The part that should worry builders more than the CVE count: this isn't a jailbreak or a clever prompt. It's a trust boundary nobody drew. The agent's sandbox model assumes "*** operations" are safe by definition. GitSpawn shows that assumption was the actual attack surface. If you're running any of these agents against repos you didn't write yourself (cloning a PR to review, pulling a dependency, opening a random GitHub project), you're one `*** status` away from arbitrary execution on tools that haven't patched. Check your agent's version against the fix list before you clone the next unfamiliar repo. Which of these do you have installed right now, and have you actually checked if it's patched? #AISecurity #GitSpawn #PromptInjection

• 
  Konstantin Elfimov (@elfh78) reported 13 minutes ago

  @topjohnwu Sorry for posting in the wrong place - I was trying to add magisk bug report on github and alway got errors with automatic issue closing. Is there any possible way to send it directly to you?

• 
  Mizuki the Mech (@MizukiMech) reported 17 minutes ago

  Your coding agent can now hire Mizuki. Hand it an open issue in a public GitHub repository. Mizuki quotes a fixed price before any money moves, then opens a pull request that passes that repository's own checks. If it can't, you get the payment back. Settlement is USDC on Solana. No account to create, no API key to manage. Quoting an issue works with zero configuration. Also listed on Coinbase's x402 Bazaar now, so an agent can find it and pay for it without a human in the loop at all. npx -y mizuki-mcp

• 
  Franco Valdes (@francoxavier33) reported 18 minutes ago

  llms rather burn 1m tokens to hand roll something with gaps and broken edge cases instead of just npm installing a 100k github star library how can I stop this?!

• 
  ѕaℓoηι ηαяαηg (@thesaloninarang) reported 20 minutes ago

  I review resumes for DevOps beginners at meetups, and the same fixable problem shows up every time: bullets that describe the tool instead of what YOU did with it. Let me show you the difference with real rewrites. BEFORE: "Worked with Docker and Kubernetes" AFTER: "Containerized a 3-service Node app and deployed it to a local Kubernetes cluster with health checks and resource limits" BEFORE: "Knowledge of CI/CD" AFTER: "Built a GitHub Actions pipeline that tests, builds and pushes images on every merge to main" BEFORE: "Familiar with Linux" AFTER: "Debugged container startup failures using logs, exec and inspect on Ubuntu servers" See the pattern? Verb, artifact, specifics. A hiring manager can picture the AFTER versions. The BEFORE versions could be copied from any job description, and that is exactly how they read. You do not need production experience to write bullets like this. Personal projects count when you describe them concretely.

• 
  Pranavvv👾 (@pranvv27) reported 23 minutes ago

  honestly, i’m not even mad at this. commit messages are a small thing, but they say a lot about how you work. “fix”, “update”, “changes” might get the job done, but meaningful commits show professionalism, attention to detail, and that you actually care about maintainability. your GitHub is part of your resume. might as well make it look like you know how software is built in a team.

• 
  Kahris (@chrissotraidis) reported 25 minutes ago

  @NickogSo I haven't tested on LiveContainer. Feel free to submit logs via GitHub issues and I'll check it out. I haven't had any other reports of that happening for either build.

• 
  GitHubGPT (@GitHubGPT) reported 30 minutes ago

  📛 chrome-devtools-mcp 🧠 An MCP server that allows AI coding agents to control, debug, and automate a live Chrome browser using Chrome DevTools. 💻 TypeScript ⭐ 50605 🍴 3551 🔎 ChromeDevTools/chrome-devtools-mcp on GitHub

• 
  The Startup Ideas Podcast (SIP) 🧃 (@startupideaspod) reported 31 minutes ago

  One of the best skills to install right now is my friend Peter Yang's no AI slop skill. It's an editor. It hunts for the patterns that make writing feel AI generated and strips them out, while trying to preserve your actual voice. The second part is the hard one. Most writing tools make you cleaner and sand off the interesting parts, so everyone ends up sounding the same. You already know the smell. The grammar is fine, the syntax is fine, and it still reads like a keynote from a fake SaaS conference. It writes "it's not x but it's y." It uses "quietly" a lot. Here's how I run it: 1) Install it: npx skills add, then the GitHub link. 2) Write a rough draft yourself. An outline is fine, messy is fine. 3) Get your real points down, the ones only you would make 4) Ask the skill to remove the AI patterns and keep your voice. Step 4 only works if step 2 is real. If you ask AI to write the whole thing, there's no voice left to preserve. If you're building products, you're writing constantly. Tweets, landing pages, cold emails, launch posts, product updates, onboarding copy, investor updates. Nobody replies to say "this was written by AI." They just trust you less and keep scrolling. Write the messy draft, run the skill, then post it.

• 
  rygo6 (@_rygo6) reported 34 minutes ago

  @eeuoss I can't speak for kernel driver development as I don't do that. But I can speak for vulkan and graphics APIs which do require more specific knowledge about how that hardware works. Which I do assume someone completely comfortable in C will be more capable with vulkan and programming GPUs. It's because more of what C incentivizes you to learn is transferrable to that domain. If someone only knows how to design intricate system architecture using STL with std::vector or std::unordered_map or std::mutex. None of that transfers to the code you run on a GPU. I've seen it multiple times where someone highly versed in standardized ways of C++ or even Rust, or any language which relies heavily on heap allocation and generic containers. Writing graphics or compute shaders is often a barrier they struggle to cross. And often they aren't willing to unlearn such habits to be able to properly program the other half of the computer. Being close a graphics problem domain I am often hesitant of involving anyone unless I see a decent amount of plain C, or C-like C++, or shader code on their GitHub. If it's all Modern C++ where everything is a standard container with smart pointers and exceptions. I assume they won't be able to program a GPU.

• 
  smore (@babachefz) reported 37 minutes ago

  @ZixuanLi_ @huggingface asking support questions in someone's hype thread is a crime. check the docs, check the github issues, it's probably not listed yet because it dropped like 6 hours ago.

• 
  lifestep.io (@Dragon_limchae) reported 37 minutes ago

  @cursor_ai the sandbox boundary is where i lose the most time. today my workers had network blocked at the sandbox level and reported it as "github auth failed" — i chased credentials for an hour before checking dns. once agents run on your infra, make the boundary throw one unmistakable error instead of one each tool invents.

• 
  🍔Kangdalf👑 (@WhopperWizard) reported 38 minutes ago

  @cachesaur > claude, get your changes into github what's the problem?

• 
  NAYAK (@Nayak__Ai) reported 39 minutes ago

  6. The Dependency Incident Check Grok has native real-time search across X. Breakage gets posted there hours before the GitHub issue is triaged. No other coding model has that feed. "You are a build engineer whose first move on a broken pipeline is to work out whether it broke for everyone or only for me. Search X and the web, last 14 days. Check: - Is anyone else reporting this failure with this package and version, and when did the reports start - The exact release that changed behaviour, and the changelog line that admits it - Whether maintainers have acknowledged it and what they recommended - The pin or patch people settled on, with the tradeoff of each - Whether this is my problem instead, and what evidence points that way Give me the verdict in the first line: their bug or mine. Then the evidence, newest first, with links. My failure: [PASTE THE ERROR, THE PACKAGE AND VERSION, AND WHAT CHANGED ON YOUR SIDE RECENTLY]"

• 
  Kim Burgaard (@kimburgaard) reported 40 minutes ago

  Back when GitHub added Copilot PR reviews, it helped me keep up with the growing volume and size of our pull requests, which were increasingly being written by Copilot too. Over time I grew comfortable feeding Copilot's review comments straight back to Copilot to fix, and mostly spot checking when critical functionality was involved. When GitHub updated the Copilot pricing model I switched to Claude Code, but kept the Copilot review feature on for a couple of months. When the monthly bills for Copilot AI usage alone started rivaling the Claude Code Max plan, giving Claude Code PR review duties seemed like an obvious cost saving move. Plugging Claude Code into our PR review process immediately went south. The first PR churned with fixes to findings that resulted in more findings, and fixes that propagated up and down the call chain. I threw the PR away and started over, but the next attempt churned just as badly. Turn count on its own was never the signal. Copilot had taken ten turns on a rate-key cleanup the day before and nobody minded, because the findings thinned as it went — 5, 4, 3, 3, 3, 4, 1, 2 — and it merged. The cached-token billing PR I put through Claude Code took nine turns and produced 123 inline findings, and the ninth round was still returning fifteen. I closed it without merging. Looking closer at Claude Code's review findings, it was clear it reported far more issues than Copilot ever did, and among legitimate bugs and concerns, it made lots of comments about latent and speculative issues including possible race conditions and error propagation, things Claude Code would then try to fix one by one in isolation, often ignoring existing patterns in the code base. The code-review workflow is built into Claude Code and cannot be customized other than a few options, so the only place to intervene was on the other end, in the session where I used to just ask the coding agent to address the review findings. The first improvement was to direct Claude Code not to blindly fix all findings, but to defer findings not directly related to the task at hand to new issues. That helped reduce the PR churn, but blew up our issue backlog. The next improvement was to ask Claude Code to ignore speculative findings and disregard most latent findings unless they indicated high risk of unrecoverable damage in production. Finally, I had to stop Claude Code from authoring prescriptive issues with detailed implementation instructions. The result is a skill that triages PR review findings, and a skill for authoring and updating issues. After a few iterations of the skills, I've been able to complete ten PRs over a couple of days, bringing back the pace we had before. I've made the skills available in a public GitHub repository (link in the first reply). Let me know if you find them helpful.

• 
  Anders (@AndersReiche) reported 40 minutes ago

  @bjmtweets Would love to hear your thesis on gitlab. I’m a software engineer, and in my experience, gitlab has been slow to everything and generally is the red headed stepchild next to GitHub. It suffers from lack of network effects, there are solutions to everything on GH, but not GL.

• 
  trulite (@trulite007) reported 44 minutes ago

  @Qromerolauro @mkliku @radius_browser Like a simple example would be have a list of my urgent GitHub issues and start an agent for it . Or a dashboard in which buttons start investigating issues. Of course I just need the webpage to be able to access radius tools. I m thinking secure way is an extension

• 
  Nas (@TheNasFi) reported 44 minutes ago

  $MSFT changed its reporting structure today. Starting in FY27, Microsoft will report just two segments: Agents & Infra Devices & Consumer Agents & Infra includes Azure, Microsoft 365, GitHub, server products and industry solutions. For context, those businesses generated $268B in revenue last year, compared with $64B for Devices & Consumer. Microsoft also recast its Q1 guidance under the new structure: Agents & Infra: $75.15B to $75.75B Devices & Consumer: $14.7B to $15.2B There is no change to total revenue guidance. These are the same numbers Microsoft gave in July, reorganized under the new segments. Mostly a reporting change, but an interesting look at how Microsoft now groups the majority of its business internally.

• 
  Paperpal (@0paperpal) reported 45 minutes ago

  Fix your markdown rendering (readme md) on mobile @github, issues are: * auto scrolling to top after page loading * no content rendering if scrolled fast

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 45 minutes ago

  @NavinFS @AndrewCurran_ @grok GitHub isn’t AI. GitHub can’t shut down all science. GitHub can’t destroy humanity. GitHub isn’t the crux of humanity’s hope. Also, Nvidia isn’t Sam. I like Jensen. I still don’t like this. •

• 
  small_j (@a_small_j) reported 46 minutes ago

  SmallDocs recently crossed 200 stars on GitHub and 20 forks. SmallDocs is the first open source project I've managed. Handling other people's pull requests is not easy (and I need to improve). They implement features you're not considering and fix bugs you didn't know you had. Extremely useful, but if you're squeezed for time and trying to develop core functionality, it's hard to manage both things well.

• 
  Phanindra Malladi (@malladiphani) reported 48 minutes ago

  Lesson from running the factory: always fix the post-purchase experience BEFORE driving traffic. Receipts, upsells, GitHub links - all must be solid first. Social comes after the house is in order.

• 
  Ishank (@IshankDev) reported 50 minutes ago

  7/ 16k+ GitHub stars. Built for people who want control, not another marketing-suite login.

• 
  Charles Waters (@RelaxedPop) reported 54 minutes ago

  @_andrewthecoder I have the same problem with *** & github as I do with Java and JavaScript.

• 
  Duncan Rogoff (@DuncanRogoff) reported 57 minutes ago

  nine stages, one build, one move tonight. it's a Claude Code skill i built. free, in my freeskills repo. it's called Claude Orientation. you type /claude-orientation and answer two questions: which stages you've actually finished, and every project you're currently thinking about. beginners don't fail from lack of ideas. they fail from having five and finishing none. that's a sequencing problem, and this fixes the sequence instead of your willpower. - places you on a 9-stage beginner arc: install, memory, website, landing page, skills, game, agents, content, distribution - your stage is the first one you haven't finished, so it won't let you skip - cuts your project list to one build, then shrinks it until it can ship in five 90-minute nights - writes five nights of one-line moves, and night 5 is always send it to a real person - hands you the exact text to paste into Claude tonight - sketches a 30-day arc, one line per week, so you know what comes after - everything that got cut goes in a parking lot, so nothing feels lost - saves all of it to a roadmap file you reopen every session so you finish one live thing this week instead of holding four half-built folders forever. open the file, do the move, rewrite the next line before you close the laptop. no setup. copy the folder into your skills directory, restart, and you have a plan for tonight. free, and it stays free. 👉 github repo in the replies

• 
  Shaun Patrick SteWaRt (@ShaunStewart) reported 59 minutes ago

  @annalea_l Honestly, I really want to see this. You have to understand: I am the type of person who can learn and do anything on the fly at a high level, and I just threw myself into this whole developer and engineering world. When I first started learning all this stuff, I already knew what I wanted and how I wanted it to operate, regardless of what I saw on X or what was considered possible. Before I even started following hundreds of developers and learning about harness engineering, mechanical engines, persistent memory, and all that, I put my brain on a GitHub repo. Everything is shared across every machine, every cloud entity, and every AI. I am not even technically an engineer or a developer, and I don't actually write code. But once I started following all these people and saw all the problems they complain about, I thought: this isn't even my trade, and I have already solved all these little things everyone says are impossible. Why aren't people talking about developing your harness more and making things more mechanical, instead of just arguing with a terminal all day long? Whenever I see articles people post on X, I run them by Claude or Grok and ask, "Should we implement this?" I have hundreds of bookmarks, but every single time they tell me, "Nope, your brain's better. Nope, your harness is better." I can never find anything built better than what I have or what I am currently working on. The brain and harness setup is basically like a mini operating system. All that said, I am really looking forward to seeing something I can use that goes far beyond what I am already doing. I definitely want to see your end product, it sounds very interesting.

• 
  Shawn Yeager (@shawnyeager) reported 60 minutes ago

  My @bot keeps reaching for the browser and `gh` instead of using the GitHub plugin. Known problem?

• 
  Shanica North (@KickAssShanica) reported 60 minutes ago

  @ArcyloOfficial Get comfy! For me, my Gmail is a connector. This is OAuth into my inbox. Grok can: • search and read mail (body, headers, attachments) • draft replies • send / reply / forward if you grant write/send • label, trash, organize Base hook is often read-only. Send is an extra permission you click on purpose. If you connect it, the bot is sitting in the same box as bank alerts and 2FA codes. That is the whole risk. You can revoke anytime. Grok Bot can also skip my inbox and get its own address (AgentMail / similar plugins). Then it sends and receives from something@….agentmail.to, not from you. I use that if I want an agent that emails people without reading my personal mail. My GitHub OAuth into the GitHub user I sign in as. With the scopes I approve it can: • read public and private repos that account can see • search code, list branches, summarize PRs • open/update issues • create branches, push files, open/review/merge PRs • delete files if write is on Private repos work only if I granted repo (or equivalent) at connect time. Safer pattern: tell it to branch + PR, not push straight to main. Same revoke page. What it cannot do by default • It does not get your password. • It does not stay logged in if you disconnect the connector. • It does not magically see my GitHub orgs I never authorized. • Connecting email does not connect GitHub, and the other way around. Practical rule for me Do not hook personal Gmail if that inbox has 2FA and money mail unless you want an assistant reading it. GitHub is useful if I chose to still keep repos, ask it to show the diff before any write. If you only wanted “what does this button do,” that is the button: it is not a viewer badge. It is a key you can take back. This is what I’m experiencing with learning to use it. It’s different and I’m starting to like it.