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:

• 
  Farley (@FarleySchaefer) reported 55 seconds ago

  @github Hope this doesn't bring down GH

• 
  Benjamin Crozat (@benjamincrozat) reported 3 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.

• 
  Varun Doshi (@Varunx10) reported 4 minutes ago

  Possibly found an issue in @github stack system It does not allow to re-target the base branch of a PR stack as you can generally do that on a single PR. Requires you to unstack and setup a new stack with updated base branch.

• 
  Convequity (@convequity) reported 5 minutes ago

  Snyk is a clean postmortem for what happens when a security tool lives inside the coding agent’s loop. The product was mostly scan-and-warn. Find the issue, comment on the PR, suggest a fix. Blocking the merge usually sat in GitHub, not in Snyk. Bigger platforms smothered it. $PANW, $CRWD, and Wiz pulled AppSec into the bundle the CISO was already buying. GitHub was the main developer surface and put scanning where the code already lived. Then coding agents arrived and delivered the final blow. A lot of that scanning became something the agent could just do. Growth held up for a short while after the COVID/cloud tailwind. Then it decelerated hard. This is the same lens we use in Convequity’s SaaS Agentic Survival Evaluation Framework. The PANW, CRWD, and FTNT reviews go up on Convequity in a few days.

• 
  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.

• 
  Yuvraj Singh (@Yuvraj_Singh317) reported 8 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.

• 
  Rusty Williams McMurray (@1RustyMac) reported 8 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.

• 
  ONCHAIN COP (@OnchainCop) reported 10 minutes ago

  @PogNyx lmao anyone can create a github issue retards this guy is a larp

• 
  htrowii (@htrowii) reported 10 minutes ago

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

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

• 
  Russ Wonsley (@RussWonsley) reported 13 minutes ago

  My @bot tells me that the official GitHub login for bot is still broken. Has this been addressed already, or did I miss it?

• 
  The Startup Ideas Podcast (SIP) 🧃 (@startupideaspod) reported 14 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.

• 
  Wlad (@dawnhell_) reported 21 minutes ago

  @brekfuz q: that's a github issue or you patched it locally??

• 
  Syn (spirit/acc) (@Synxneuos) reported 22 minutes ago

  GM guys. Don’t assume that because the token price is down, I’ve stopped working on development. If you want to see what’s actually being built, check the GitHub. I’ll keep posting updates here as well, but today was a little hectic for me, so I couldn’t post as much as I wanted to. Development is still going on. More updates soon.

• 
  Harley Lewis Foote (@harleyfoote_) reported 22 minutes ago

  @dhh GitHub issues are theatre. Feature requests go through @ mentions now.