GitHub 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:

• 
  Harsha Kotcherlakota (@DPortkey) reported 5 seconds 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

• 
  recovering buzzkill (@MikeStillAwake) reported 8 minutes ago

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

• 
  Benjamin Crozat (@benjamincrozat) reported 12 minutes ago

  From now on, I will assume that GitHub is always down and I'd like to be notified when it's briefly not.

• 
  tonis (@totovoto) reported 14 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.

• 
  Ishank (@IshankDev) reported 16 minutes ago

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

• 
  Frank van Puffelen (@puf) reported 21 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)

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

• 
  Jeremy W (@basicBrogrammer) reported 24 minutes ago

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

• 
  gatorade (@kadetXx) reported 24 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)

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

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

  @izzyCodes_ and you too Chief Check GitHub issues

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

• 
  Yuvraj Singh (@Yuvraj_Singh317) reported 29 minutes ago

  Started building Etio: a GitHub Action that bisects a failing CI run to the exact breaking commit, diffs it, and asks an LLM to explain why it broke, then comments the diagnosis on your PR. No Docker, no server- runs on your own Actions minutes. Open source, WIP.

• 
  Josh Hamilton (@nearbycoder) reported 30 minutes ago

  @theo If GitHub is down does it fall back to a cached version I’m guessing?

• 
  Mr. Buzzoni (@polydao) reported 31 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