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 (13%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	2 days ago
Ahmedabad	Errors	7 days ago
Delme	Sign in	8 days ago
Lyaud	Website Down	8 days ago
Catania	Errors	10 days ago
Inverness	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:

• 
  Hua-**** Xiong (@HuaDongXiong) reported 2 minutes ago

  Codex for Windows stopped launching after an update. Multiple github issues opened for 2+ weeks. This affect users who set the MS store install location to a non-C: drive. Mac version is buggy too. ofc coding is solved! @thsottiaux

• 
  Lummox (@Lummox_eth) reported 2 minutes ago

  My own built Grok Bot turned $1,000 into $5,300 for last 17 hours. Now the project behind it is sitting around $25K market cap. We already pushed past $60K once and gonna hit $200k soon The bot is still running. The utility is almost ready. GitHub is live. Dev tokens are burned. I’m still buying. Nothing about the actual project changed because the chart went down. At $20K MC, this is the entry I personally like far more than chasing the first move. The target hasn’t changed either. $100K+ is where I want to take this next. $LUM is just getting started.

• 
  Frank van Puffelen (@puf) reported 5 minutes ago

  @_davideast Noice! From the GitHub page, this covers all of Auth, Firestore, Realtime Database, Storage, Messaging, and Firebase AI Logic. 👏 Where is data persisted (if at all)? Also: JS only, I assume? (sorry if that's all in the repo too, GitHub just went down on me)

• 
  Asterix (@Asterix54907294) reported 11 minutes ago

  end-of-summer snapshot for @QFEX : -~$222M in open interest -CLI v0.3.12 shipped in August with improved installation docs and a go.mod fix -GitHub activity continued through late August not a flashy launch recap, just a quick look at how the exchange is closing out the summer: more markets, meaningful liquidity, and active work on the tooling side still early, but the infrastructure is clearly moving

• 
  gatorade (@kadetXx) reported 14 minutes ago

  because it’s not worth it for the most part. most software failure or bug incidents don’t have any physical victims. at most company loses some money or the issues are almost instantly fixed, no lawsuits, no so much to answer to the state for if your software has a bug or fails to work as expected for a brief period (think, multiple downtimes from the big five so far, even github too, who died? exactly) and in the industries where bad code fan have physical consequences, they actually do test software like hardware engineers & physicists (i hope)

• 
  Spectra☢️ (@Spectra010s) reported 15 minutes ago

  @izzyCodes_ and you too Chief Check GitHub issues

• 
  Bearded Printer (@BeardedPrinter) reported 15 minutes ago

  @RedPill_Phil You've gotta go to their github and submit an issue. Make sure to search their issues to ensure you don't submit a duplicate bug

• 
  htrowii (@htrowii) reported 16 minutes ago

  @brainage19 i set my flake up with copy pasting github dotfiles on bare metal it was terrible

• 
  Mr. Buzzoni (@polydao) reported 22 minutes ago

  LOOP RAT ROADMAP: WHAT'S NEXT, AND WHAT IT'LL NEVER BECOME v0.3.3 today. 3 loops, 55 checks, 0 services here's where it's headed: > 0.4 - read the night faster: rat watch live-tails a running shift, rat replay reruns one from its saved prompt, a weekly digest instead of seven separate pages > 0.5 - off the laptop: run-due moves into GitHub Actions, state lives on a branch, rat cron --launchd survives a closed lid > 0.6 - sharper graders: swappable rubric packs, two graders disagreeing becomes your queue for the day > 0.7 - the work itself: a worktree per shift, so a failed night never dirties your tree > 1.0 - trust: a hash-chained trace nobody can quietly rewrite what it will never have: > no web dashboard - the terminal already knows where the files are > no database - plain files outlive the tool that wrote them > no hosted service - nothing to sign up for, nothing to shut down > no auto-merge - the rat proposes, the morning decides every item ships behind a flag: dry run -> report only -> one repo -> a week of receipts -> default on a feature that can't run as a dry run doesn't get written the rat is boring on purpose. every version keeps it that way

• 
  Prophet Joel (@2happyCSGO) reported 24 minutes ago

  I personally hated Claude because it refused to do almost anything I asked it to do so have no idea of how the speed is but gemini-cli was unusable for non enterprise users. Github CoPilot both GUI and cli is pretty good. Grok Build is what I'm using mostly and not yet had any issues with the speed but I want to go full local asap, scouting for 3090's atm. Just to be able to run "uncensored" models that don't ***** like Claude is reason enough for me to prefer local over Cloud but also cloud is ******* expensive, I have SuperGrok 100$/month and CoPilot Max 100$/month and that is barely enough. I'm trying to make my own Jarvis so I need to build my own RAG, memory, librarian, SRE Agent that understand how to use all tools and I also get crazy new idea's all the time lol Just made my first alpha of a tool that can wipe basically anything you don't want in Windows11. Basically Chris Titus clone but on steroids, this isn't just a debloater, it's a Grim Reaper 💀

• 
  Ishank (@IshankDev) reported 24 minutes ago

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

• 
  WuBu ⪋ WaefreBeorn 🇺🇸 👑 (@waefrebeorn) reported 27 minutes ago

  hey @Teknium @yeahfortommy please add the amd portal too even if tou have to send tommy into the AMD headquarters to get them to fix the links (you have to sign up for american then link through github, then you can access the models free, tommy needs to pull teeth but they have free api)

• 
  ∆LΞX∆NDΞR D∆VIS (@_AlexanderDavis) reported 29 minutes ago

  @egavrilenko11 @bot I had to update my fine grain token for GitHub and now when it tries to authenticate the plugin, I'm getting the error: GitHub didn't provide a sign-in link My bot said: Known host bug, not you. The GitHub Authenticate button tries OAuth GitHub does not support. Checking whether a PAT on the plugin page is the working path. That's a Grok Bot host bug, still open: cursor/plugins#251. GitHub's connector is PAT-only. The Authenticate button tries OAuth GitHub does not support, so you get "didn't provide a sign-in link." Don't keep hitting it. But it worked before I updated my fine grain token...

• 
  recovering buzzkill (@MikeStillAwake) reported 29 minutes ago

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

• 
  David Abram 🐊 (@devabram) reported 33 minutes ago

  Discord is down. X is down. GitHub is down. Software is solved.

• 
  Kir Shatrov (@kirshatrov) reported 34 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.

• 
  Straggler Liu | AI & Semis (@StragglerLiu) reported 38 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.

• 
  Kahris (@chrissotraidis) reported 39 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.

• 
  Marcelo Retana (@mretsal) reported 39 minutes ago

  Every time @github goes down they should have a plan to please their users. Give me free credits for actions for example 👍🏼

• 
  Åsa-Nietzsche (@AsaNietsche) reported 42 minutes ago

  @peterb0yd @burkeholland @github It's every ******* model. I'm getting whiplash from all of this everything changing forever society being turned upside down every two weeks.

• 
  John Crickett (@johncrickett) reported 46 minutes ago

  @Mike_Preston17 I don't think they water them down, why would they when they're competing on having AGI? I don't mind using GitHub actions to run tests and builds against a branch before merge. I don't want it triggering production schedules. Do you list all the things it shouldn't do in the prompt?

• 
  wiiiimm (@wiiiimm) reported 49 minutes ago

  @Umesh__digital stop doing it. we don't need another github outage.

• 
  Martin Tobias (Pre-Seed VC) (@MartinGTobias) reported 50 minutes ago

  if you know any founders who are winding down, I may have a buyer of their github repos. DMs open.

• 
  Jason Waters (@jasonwaters87) reported 54 minutes ago

  Anthropic just open sourced the code Shopify runs their shopping agent on. Free on GitHub. And I’m having lunch with a surgeon in San Jose last month and he tells me a patient no shows and nothing happens. Nothing. He has to walk up to the front desk himself and ask “did you guys call them?” 3 or 4 schedulers looking after 75 doctors. One automated call before the appointment and that’s it. His own dermatologist sends him three reminders. He called that “an easy fix.” That’s a merchant agent. Reminds the patient, rebooks the no show, tells him Thursday isn’t full so he can put a surgery on it. The code is sitting there free. Somebody still has to walk into his office and build it.

• 
  John Zhong | AI Growth Systems (@John_zhong324) reported 54 minutes ago

  @github A repeatable --attach flag turns CLI reports into reproductions: inline screenshots in issues mean a bug gets fixed in one pass instead of two round-trips for context.

• 
  The Oracle (@scientist1q) reported 54 minutes ago

  when my Oura ring detects a cortisol spike from a GitHub Actions failure, Hermes (Fable 5.1) detects it and sends a 900 word root cause analysis, Hermes dispatches the work to my 12 Grok Bot employees, The Chief of Operations bot approves the fix while im watching rezero

• 
  Joshua Okolo (@joshuaokolo_) reported 56 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

• 
  Anime0t4ku (@Anime0t4ku) reported 57 minutes ago

  @c_hri_s Github issues are not closed. Mahbe refresh your webbrowser.

• 
  Aayushiii (@stfu_aayushiii) reported 59 minutes ago

  If you're building a project, read this before writing a single line of code. 5 things I learned the hard way: 1. Problem > model Don't start with “How do I use GPT?” Start with “What problem am I solving?” 2. Simple stack > impressive stack If your MVP needs Kubernetes, 6 microservices and an agent swarm, you probably haven't built an MVP. 3. Evaluate before you optimize You can't improve what you can't measure. 4. Build for users, not your GitHub README A technically impressive project nobody can use isn't a product. 5. Ship ugly. Iterate fast. Your first version isn't supposed to be impressive. The biggest mistake? Spending weeks deciding which model to use when you haven't even validated the problem.

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