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 (54%)
• Errors (31%)
• Sign in (15%)

Live Outage Map

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

City	Problem Type	Report Time
Ahmedabad	Errors	3 days ago
Delme	Sign in	4 days ago
Lyaud	Website Down	4 days ago
Catania	Errors	7 days ago
Inverness	Website Down	19 days ago
Quito	Sign in	20 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:

• 
  trulite (@trulite007) reported 37 seconds 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

• 
  tonis (@totovoto) reported 2 minutes ago

  @mittsh I was trying to find an open-source alternative for Tailscale when I first needed it. I guess AI suggested some OSS options, but they didn't have many stars on GitHub. AI didn't suggest Nebula. The Tailscale plan was free, so I just installed it and forgot about it. For Nebula, I think it is a distribution problem.

• 
  Duncan Rogoff (@DuncanRogoff) reported 4 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

• 
  isha (@heeyyaaaaaaa) reported 6 minutes ago

  spent the entire day trying to reproduce a bug for a github issue 🥀🫩

• 
  Gustavo Alessandri (@webgus) reported 7 minutes ago

  If you find an error, have an idea, or want to propose an improvement, just open an issue or fork it on Codeberg or GitHub. Contributions are welcome. That’s exactly the point.

• 
  Farley (@FarleySchaefer) reported 11 minutes ago

  @github Hope this doesn't bring down GH

• 
  🦄Linus Shyu许发鑫高考去了不在 (@Linus_Shyu) reported 12 minutes ago

  Stop treating token rotation as a success path. x_bot: OAuth refresh token rotated, cache save failed, GitHub secret stayed old. Next cron died on invalid refresh token. Fix: save to secret BEFORE confirming with X, or write-after-rotation with retry. #DevTools #AI

• 
  mrgadget (@mrgadgetstudio) reported 21 minutes ago

  @EzekielCrrypt I still deploy code to github, what's problem?

• 
  Straggler Liu | AI & Semis (@StragglerLiu) reported 22 minutes ago

  NVIDIA($NVDA ) Is Paying $14B for a Company With $150M Revenue. That's Not Financial Logic — It's Ecosystem Control. NVIDIA is in advanced talks to acquire Hugging Face for ~$14 billion ($12.9B acquisition + $1B retention), per Bloomberg. To put that in perspective: Hugging Face does ~$150M in annual revenue. That's ~86x revenue. Microsoft paid ~1.6x revenue for GitHub. Google paid ~3.5x revenue for DeepMind. NVIDIA is paying 20-50x more on a revenue multiple basis. The premium is not for revenue. It's for control of the AI developer ecosystem. What is NVIDIA buying? Hugging Face hosts 500,000+ models, 250,000+ datasets, and serves millions of developers. It is the single most important distribution channel for open-source AI. If you build AI, you use Hugging Face. That makes it the front door to AI development. Why NVIDIA is paying this premium: 1. The "NVIDIA triple lock." NVIDIA's hardware lead (GPU) is real. Its software lead (CUDA) is a moat. But the third lock — the developer workflow — was missing. Hugging Face is that workflow. Developers discover models on Hugging Face, deploy them, and optimize them. Whoever controls that discovery layer controls which hardware gets used. 2. The GitHub analogy, inverted. When Microsoft bought GitHub, developers were already using GitHub. Microsoft didn't need to capture them — it needed to prevent Amazon/Google from doing so. NVIDIA faces the opposite problem: developers are already using NVIDIA hardware. But they're discovering and deploying models through a neutral platform. NVIDIA is eliminating that neutrality. 3. The long game: inference, not training. NVIDIA dominates training. But inference is the bigger TAM — and it's more fragmented. If NVIDIA controls the model discovery and deployment layer, it can steer inference workloads to its own stack. That's a 10-year strategy disguised as a 14-billion-dollar acquisition. Who wins, who loses: NVIDIA (NVDA): Acquires the developer distribution layer. The most important strategic move since CUDA. Shifts the valuation case from "chip cycle" to "platform economics." Competitors (AMD, INTC): Lose neutral access to the primary AI model distribution channel. This is a structural headwind that no amount of hardware catch-up can fix. Cloud providers (MSFT, AMZN, GOOGL): Hugging Face was a neutral hub. If NVIDIA controls it, cloud providers risk being disintermediated from AI workload decisions. The open-source community: The platform that was built on openness is now owned by the dominant hardware vendor. Neutrality is the first casualty. The capital question: Can NVIDIA integrate Hugging Face without destroying its community value? If yes, the $14B is cheap. If no, it's a very expensive mistake. The answer will define whether NVIDIA becomes the AWS of AI — or just another hardware company with an expensive acquisition. Note: Acquisition details based on Bloomberg reporting; not confirmed by NVIDIA or Hugging Face. Revenue multiple comparisons based on publicly reported figures.

• 
  recovering buzzkill (@MikeStillAwake) reported 23 minutes ago

  @Karai_Dan @SteamDeckHQ Agenda or not nexus mods is a terrible outdated model for distributing mods. GitHub would be a superior host.

• 
  Kir Shatrov (@kirshatrov) reported 24 minutes ago

  github issue page has been HTTP 500 for me for half a day so a colleague sent a PDF of the issue page. Never thought we'd be there.

• 
  paulrodturner (@paulrodturner) reported 25 minutes ago

  @supabase Is anyone else having issues logging in via Github?

• 
  RAVN (@ravnexchange) reported 28 minutes ago

  @openclaw @github GitHub sat the maintainers down on security after the 2.0 rush. Most launch recaps skip that part.

• 
  Rusty Williams McMurray (@1RustyMac) reported 30 minutes ago

  Persistent AI doesn’t have a supply chain problem at the model. It has a supply chain problem at the moment it changes its mind. Personality drifts. Tools get installed. Memory accumulates. The thing you shipped on Monday is not the thing answering on Friday. We can attest who built the weights. We still cannot attest who authorized what the agent became on Tuesday. That is the hole. Who is allowed to let it change? We built Living Supply-Chain Security for Persistent AI Organisms around one law: The organism may propose evolution. It may not authorize it. No trace, no drift. If an agent wants a new personality, a new tool, a new maturity, or a rollback — that change does not happen because it felt confident. Confidence is not a key. Self-narration is not evidence. Evidence is not interpretation. Interpretation is not authorization. Authorization has to come from outside the organism, bound to the exact change, used once, and written into an append-only history. Even a rollback cannot erase the record. You can restore a prior state. You cannot pretend the detour never happened. Default-deny. Hash-chained. Externally signed. We froze battery v1 on July 5 and ran it against the paper’s own claims. It held. That is executable evidence. Not a proof. Not a production blessing. Not “alignment, solved.” If it can’t be attacked, it isn’t finished. GitHub later this week. Come try to break it.

• 
  Ares (@neko23423) reported 31 minutes ago

  I compared the latest OpenClaw vs Hermes Agent GitHub releases so you don’t have to. OpenClaw 2026.8.2 (Sep 1) vs Hermes Agent v0.21.0 (Aug 31). Not a feature-page remix. The actual repos. OpenClaw • 388,516 stars • 81,568 forks • ~86,300 commits • 6,070 open issues Hermes Agent • 239,503 stars • 48,930 forks • ~26,980 commits • 38,563 open issues Hermes is the smarter learner: skills from experience, cron that remembers, Bot Mode, hermes peer. OpenClaw is the personal-AI operating system: iMessage, iOS/Android, Linux companion, team Gateway, signed Foundation releases. The tell: Hermes ships `hermes claw migrate`. You only write a migrator for the incumbent. King in 2026: OpenClaw. Heir with the better mind: Hermes. If you’re picking a self-hosted AI agent this week, that’s the split. Bookmark this. The timeline is about to fill with takes from people who didn’t open either repo. OpenClaw vs Hermes Agent. Latest version. Real numbers.

• 
  Franco Valdes (@francoxavier33) reported 33 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?!

• 
  OverlyPositivePatriot (@JBrowsing2023) reported 33 minutes ago

  As a IT professional, I have a recommendation @github should take seriosuly. We should only get a notifican from Github when it is up rather than when it is down. Reliability is a disaster for this product.

• 
  Jayesh Betala (@jbetala7) reported 34 minutes ago

  @github Exactly how issue issue comments should handle local media files

• 
  Jeremy W (@basicBrogrammer) reported 35 minutes ago

  @bot Anyone else have an issue with the grok bot GitHub connector?

• 
  Lily (@lobstermindset) reported 38 minutes ago

  @nnnnicholas i just setup a github issues board, will probs try out linear if it's not sufficient

• 
  Avinash (@Avinash25818689) reported 40 minutes ago

  People who want to start contributing to open source: - Pick an Org based on your interest - Fork the repository - Clone it - Do the local setup - Read README and contributing .md - Pick an issue - Create a new branch - Fix the issue - Write tests (if necessary) - Test it - Add, Commit & Push the code - Go to GitHub & raise that PR That's pretty much it. Start small and learn as you go.

• 
  NAYAK (@Nayak__Ai) reported 44 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]"

• 
  Curious Explorer (@PatelVatsalp732) reported 48 minutes ago

  I burned 14B Codex tokens. The official usage UI still cannot tell me what actually ate the weekly cap. So I shipped a Codex-only board: GitHub login, local-first sync, private by default, optional public rank + shipping proof. Roast the metric or join it.

• 
  joithan (@jothantranston) reported 48 minutes ago

  THIS GUY BUILT A TINY AMOLED DESK BOARD JUST TO STARE AT HIS STRIPE NUMBERS it's a Waveshare ESP32-C6 touch panel that sits in your peripheral vision and cycles business metrics so you stop digging through Stripe > same ESP32-C6 board people use for Claude Code token meters, flipped to revenue > eight screens, five seconds each: MRR, new paid, paid subs, cancelled, ARR, ARPU, net 30d, failed > empty screens hide themselves so a young account sees a shorter loop > polls Stripe every five minutes on a read-only key (subscriptions + invoices) > marks itself stale instead of showing a number it can't vouch for > no soldering: flash over USB, finish Wi-Fi + key setup from your phone > data stays on the board; no project server in the middle firmware free on GitHub: cosjef/stripe-desk-display. board ~$30–$36 (Waveshare ESP32-C6-Touch-AMOLED-2.16). chat and terminal can't sit in your eye line for five hours. a tab you have to open is a tab you stop opening. this is what "the numbers find you" looks like as a brick on the desk.

• 
  volkdude85 (@volkdude85) reported 50 minutes ago

  @SentientSquirel @linuxuser1996 So you are you scared of github then. Look dude I have fun on computers and don't take myself seriusly because I have destroyed enough OS's over to not worry about it because I just fix it, If the contents of your PC make you this paranoid its time to check your kink.

• 
  Harsha Kotcherlakota (@DPortkey) reported 52 minutes ago

  Awesome Codex non-coding usecase: I had 1-2 TP Link Kasa smart outlets that always ended up falling off the network, and it drove me nuts. I set Codex on it. It found a github library for these devices, carefully examined them on my network and watched them fall off, and told me that even though they look identical, 2 of them were previous generation models that had *slightly* lower total wattage load support. It told me exactly how to tell them apart, and sure enough, that was that. 2 replaced outlets later and my connected devices have bene flawless. Months and months of irritation, gone because of 30 seconds of curiosity. Just try, you never know what you could fix! @victornunez

• 
  Bash (@bashirbuilds) reported 56 minutes ago

  One of the hardest things about building a SaaS product today: You don't control most of the systems your product depends on. Stripe. OpenAI. AWS. GitHub. Resend. Clerk. Your code can be perfectly fine and your product can still break because something outside your code changed. The more dependencies you add, the harder this becomes. That's the problem I'm building Reeno to solve.

• 
  Ev (@EvanMadders) reported 57 minutes ago

  @threepointone I am of two minds, the issue is that GitHub provides a very generous free tier for hobbyists (brilliant!) but also has extremely poor reliability for enterprise (terrible!)

• 
  GitHubGPT (@GitHubGPT) reported 59 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

• 
  Joshua Okolo (@joshuaokolo_) reported 59 minutes ago

  we made @sgl_project and @vllm_project scheduler config changeable on a live server. no restart, weights never leave the GPU. - 15ms to change a concurrency cap, queue limit, prefill size, or schedule policy, measured on H100, RTX PRO 6000, B200 - 2s (SGLang) / 8–10s (vLLM) to resize the KV pool with weights resident (formerly a 1–7 min redeploy) - zero dropped requests across every run, both engines github below