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:

• 
  Micky Thompson (@mickythompson) reported 54 seconds ago

  @thdxr I use opencode from ~/GitHub folder and that contains multiple repos (packages, monorepos, and open-source projects). I do this because I often reference repos to emulate patterns in a project. Does that mean worktrees and more will not be available unless I switch to working from 1 repo? Is not working from a repo a bad practice in opencode?

• 
  Crypto Headlines (@CryptoHe4dlines) reported 4 minutes ago

  🙏 $SOL Noah Prince just took one of the hardest jobs in Solana. Today @redacted_noah joined @DriftProtocol as Head of Protocol. This isn’t just another post-exploit hire. It’s who they hired that matters. Noah isn’t a Twitter protocol commentator. He has real mainnet scars. Most notably, he was one of the key people behind Helium’s $HNT full migration to Solana – moving a live network with users, governance, token mechanics, oracles, hotspots, and a massive amount of state from a custom L1. Very few builders in Solana have shipped anything close to that level of complexity in production. Before that, he was CEO and co-founder of Strata Protocol, an early Solana infrastructure project. His GitHub handle is ChewingGlass. It’s not just a meme – it’s a pattern. He consistently chooses the hard problems: Strata, then Helium’s migration, now Drift’s rebuild. After years at Helium, Noah could have taken an easier role. Instead, he’s putting his name on one of the messiest protocol rebuilds in Solana DeFi. That’s a real signal. Drift doesn’t need another growth narrative. It needs someone who actually understands technical debt, security assumptions, governance risk, and mainnet pressure. Noah fits that profile. There are plenty of people who can explain how things should work. Far fewer are willing to touch the broken machine and make it work again. Noah is in the second category. This is the type of builder Solana needs more of — people who take the nasty, risky, protocol-level problems and ship anyway. Rare builders matter more than perfect narratives. solana:DriFtupJYLTosbwoN8koMbEYSx54aFAVLddWsbksjwg7

• 
  Bhanu Nagar (@bhanu4417) reported 8 minutes ago

  @jackfriks @Cloudflare @supabase there is a way to bypass it that i use for my shareable profile links that if the data isnt confidential make a 2nd github account create a public repo push the data as json there and i use slug for shareable pofile like wacheit/profile/developer something like it with the timestamp thats it,now it fetches from github repo no server load at all

• 
  Dan "18pF flip-flop" (@dcominottim) reported 8 minutes ago

  @SyntaxError2505 Yeah, but it isn’t that simple. For instance, compression is the Fedora default for both Workstation and Atomic Desktops, but it’s currently broken in both in different ways — if you use manual partioning in the former, the installer doesn’t apply it to fstab, and in the latter it’s a missing kernel argument. (I reported the Anaconda bug for the Workstation case and it was fixed in upstream a couple days ago.) The kernel had a bug that only got fixed in 7.1 (yet to be released) in which small files that are stored inline in inodes and have been marked as incompressible will forever be marked like that and never be candidates for reevaluation. Cool bit: that incompressible flag won’t be fixed by upgrading the kernel; you’d have to mess with low level stuff to manually fix it for existing files/inodes. A feature/part of systemd (don’t recall which now, but I bookmarked the GitHub issue) automatically enables full quotas if the detected filesystem is btrfs, which destroys performance and cause severe stalls if you have lots of snapshots. One of use SUSE btrfs developers commented in the thread, and the fix is not to use quotas at all and use squotas if feasible (the same dev says in the same comment that squotas have its own quirks and that full quotas aren’t fixable because he tried it already and it’s fundamentally incompatible with btrfs’ design that allows fast snapshots). And there are countless things like that 20 years later, and you have to trust that all or most userspace components will be aware of most of those things if btrfs is detected… so…

• 
  Rainer Gerhards (@rgerhards) reported 8 minutes ago

  @ajambrosino @wholemars it's basically pretty cool, but not very reliable. That's actually a shame. Else I could also use it for tasks that really matter. There are github issues open.

• 
  Kleber Tiko (@klebertiko) reported 8 minutes ago

  @mattpocockuk I used yours with one good rule...every agent and context window must avoid hit 40%. If needed run /handoff with the summary and tracer-bullet tasks to next session. So i can run /clear and startover next tasks. My tracer bullet use github mcp server to create issues to track.

• 
  Bob McElrath (@BobMcElrath) reported 10 minutes ago

  @Italianclownz @barackomaba @BarackObama My analysis harness uses transformers directly and reimplemented your kernels, so I can dump intermediate tensors (hence the MSE error measurements in the github issue). I did a bunch of research on quantization methods and built this harness for it.

• 
  ./can (@shcansh) reported 14 minutes ago

  Giving an AI agent direct write access to your repository is a significant shift in workflow trust. GitHub now lets Copilot Pro, Pro+, and Max subscribers fix broken GitHub Actions runs with 1 click. The agent spins up its own cloud environment, investigates the failure, and pushes the fix directly to your branch. Will developers actually trust an agent to commit code directly to their branch, or is this going to result in messy, automated *** histories? #GitHubCopilot

• 
  m-ret (@mretsal) reported 16 minutes ago

  @GithubProjects We can't push to production on Friday because github is down.

• 
  October Ø (@ralphaelofDeFi) reported 19 minutes ago

  @Trae_ai Pls respond to the problem on the ide GitHub. We can’t login

• 
  Lummox (@Lummox_eth) reported 23 minutes ago

  HERMES AGENT CROSSED 140,000 GITHUB STARS IN 3 MONTHS AND JUST BECAME THE MOST USED AGENT IN THE WORLD. Most AI agents forget everything between sessions. Hermes writes its own skills from experience. Next time it runs the skill, improves it, and gets faster. Independent benchmarks show agents with 20+ self-created skills complete similar tasks 40% faster than fresh instances. Qwen 3.6 where the 35B version outperforms last year's 120B models at one third the memory footprint. DGX Spark with 128GB unified memory running everything locally at $0 per month after hardware. The setup takes 30 minutes. LM Studio plus Qwen 3.6 27B for the model server. One install script for Hermes. One config connecting them. Set context window to 65,536 tokens or nothing works. After one month of daily use your skills directory has 20 to 50 learned workflows. Your Hermes is genuinely different from anyone else's.

• 
  ./can (@shcansh) reported 24 minutes ago

  The real test for GitHub Copilot's new one-million-token context window in VS Code is going to be developer behavior around AI credits. If using extended reasoning and huge context eats your budget fast, most devs will stick to defaults out of anxiety. Is anyone actually going to manually dial their reasoning level up and down throughout the day, or will we just wait for IDEs to automate this routing? #GitHubCopilot

• 
  treysync (@0xtreysync) reported 25 minutes ago

  I decided to copy down (literally copy-paste) a Skill file from GitHub. My management told me I need to approve ANYTHING we get off the internet so we don’t endanger our systems. I have no words.

• 
  YummyNZT (@yummy_nzt) reported 25 minutes ago

  🚀 BUYING $DOGE RIGHT NOW TO FLIP IT 3X HIGHER IN 3 MONTHS Massive panic selling absorption by major players happening at this level right now. Historically, this accumulation leads to huge pumps 📅 Aug-Sep 2018: 3x+ pump driven by Dogecoin-Ethereum bridge launch and forking hype. 📅 October 2022: Pumped from $0.06 to $0.15 following Elon Musk's acquisition of X. 2026 Season: What structural catalysts could trigger a massive short squeeze and send us straight to the moon this time? 📈 🔹Spot Dogecoin ETF Approval Grayscale, Bitwise, and 21Shares have already submitted official 19b-4 filings to the SEC for spot Dogecoin ETFs. 🔹Radical Supply Emission Cut (GitHub Proposal #3776) Core developers are actively debating a major proposal to slash block rewards from 10,000 down to 1,000 DOGE. Massive supply shock loading. 🔹Solana Integration & DeFi Bridges Active development is underway for full-scale integration into top DeFi ecosystems via trustless cross-chain bridges. 🔹Official US "Digital Commodity" Status & Utility Major e-commerce giants are expected to announce DOGE integration as an official payment method this summer. If even ONE of these catalysts gets officially confirmed, we are getting a rock-solid fundamental reason for a massive programmatic pump. Have you bagged some DOGE yet? 💰

• 
  Saylor (@seylorra) reported 31 minutes ago

  @TheAhmadOsman honestly i just want sm120 to work with vllm without a 4 hour github issue hunt. a rocm sanity check or json config isnt too much to ask.