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:

• 
  Jose (@SolutionsCay) reported 30 seconds ago

  @petergyang /goal make me app does not work for me 😰 but /goal complete GitHub issues #90, #91, #92 works very well

• 
  Gustavo Alessandri (@webgus) reported 2 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.

• 
  Alpha Batcher (@alphabatcher) reported 3 minutes ago

  David Soria Parra: "2026 is all about connectivity, and the best agents use every available method" A coding agent needs access to the same places you check while building: - repo and PRs - docs - browser - database - error logs - Figma - tasks - payments The article gives the 11 MCP servers for that setup: - Context7, GitHub, Playwright first - Supabase or Neon, Sentry, Firecrawl next - Figma, Linear, Stripe when you need them - Filesystem, ***, Memory, Sequential Thinking as the base Read it if you keep copying code, docs, schemas, screenshots, errors, and tickets into Claude Code by hand

• 
  Financial Programmer (@RBiancoUS) reported 3 minutes ago

  A dose of reality for end of week. My biggest question is I can't find any reason for the $Gold panic- did they find gold is causing cancer or radioactive? Selling looks like sheer panic. Would you believe someone asks in DM, so how did *you* get so many followers. Then he lets me brew on it for a day and comes back, I was joking do you have a github, presumably to get some code. No wonder I worked alone. I'm challenged socially guess not alone. After a night of 3 scammers one from Nigeria, one Africa. I need to lock dm down or find a way to restrict

• 
  Ucupaint 🔶 (@ucupaint) reported 5 minutes ago

  @iye_jr It works fine here. Check if the paint mask is turned on or not. If you still have a problem, please file a github issue with a sample file.

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 6 minutes ago

  AMD quietly removed RAM encryption from consumer Ryzen CPUs. Via a routine firmware update. No release notes. No advisory. No announcement. The BIOS setting still shows up. Still toggles on and off. Does absolutely nothing. A privacy-focused Linux hobbyist noticed in April. Spent months chasing it down. Filed a bug report on AMD’s GitHub. AMD engineers replied suggesting he toggle the setting off and back on. He showed them internal firmware dumps proving the flag was hardcoded to FALSE. An AMD senior principal engineer closed the thread with: “My apologies but I don’t have any more information to share on this topic.” That’s it. Seven weeks of investigation. Multiple motherboard vendors confirming it. Internal firmware evidence. AMD’s answer: no comment. The feature still works on Pro and EPYC chips. Which cost significantly more. The hardware is physically capable. The firmware just says no. Windows users have no way to detect this happened. There is no Windows tool that checks TSME status. The BIOS lies to you. AMD’s own engineers confirmed the feature worked on consumer chips in 2020. Then again in 2025. In 2026 it’s a PRO feature. Nobody told you.

• 
  Crypto Update IO 🚀 (@cryptoupdate_io) reported 7 minutes ago

  @CryptoPatel Hsiao-Wei’s exit follows a 30% drop in EF-funded GitHub commits YTD (per Santiment). The real shift? Funds now focus 60% on L2 R&D vs 30% in 2022. We track this daily—breaking it down in our quarterly reports. Follow for the data before the narrat...

• 
  Kashaf (@noor36758) reported 7 minutes ago

  @PiyuCodes GitHub is literally a CS/engineering tool... if it gets banned that's your problem too 💀

• 
  Gitbank (@Gitbank_io) reported 11 minutes ago

  Community update — GitStock delay + what we have been building First, we owe you an honest update. We promised GitStock would ship earlier and we went quiet. That was on us. No excuses, we were heads down in the contracts and infrastructure and did not communicate well. That changes today. Here is what actually took time. We refused to ship GitStock on top of third-party APIs or borrowed infrastructure. Everything you see in Gitbank; the vault, the relayer, the swap engine, the RWA layer runs on smart contracts we wrote, audited ourselves, and deployed. The GitVault contract is verified on Basescan. The GitStockFactory is verified on Basescan. You can read every line. No black box. No external custody API holding your assets behind the scenes. That decision slowed us down. We think it was the right one. On security specifically. Your funds sit in a soul-bound smart contract vault anchored to your GitHub ID. Transfers are disabled at the contract level — not by a rule in a database, by the EVM itself. We also built private transaction routing directly inside GitVault on Base. No Tornado, no third-party mixer, no privacy-as-a-service API. The privacy logic lives in our own contract. You can verify it. The relayer signs and submits transactions on your behalf so you never pay gas, but the keys to your vault are yours. We hold nothing. If you want to verify any of this: check our contracts on Basescan, check our GitHub, check the bytecode. We are open source. The code is the proof. GitStock ships tomorrow.

• 
  Roy (@__roycohen) reported 12 minutes ago

  The Github API is probably causing OpenAI millions of dollars in token spend a month because GPT web cannot actually browse Github properly. At this point hosting your own server for instant reads is likely the way

• 
  Ant A. 🇺🇸 (@AntDX316) reported 15 minutes ago

  @thsottiaux When I need to fix up a GitHub Repo through the Smartphone, I prefer Claude Code though because it doesn’t need a device to run the repo, but if it needs to run a repo on a device due to the limitations through the Smartphone, I use Codex Mobile or OpenClaw with GPT-5.5 through Telegram.

• 
  Atlantean Gnosis ☀️ (@AtlanteanGnosis) reported 16 minutes ago

  @DionysianAgent When I made an account it said I made it back in 2024, though I don't think I did, is this a glitch or a GitHub thing?

• 
  Prashanth Koppula (@koppula) reported 16 minutes ago

  4/6 ReproRepo sidesteps that by treating GitHub issues as a proxy signal across 1,149 recent ML papers from major conferences. The trick: instead of expert-curated labels, the framework matches agent-reported issues to human-raised GitHub issues using semantic similarity.

• 
  Zo (hiring) 🐦‍⬛ (@0xZoZoZo) reported 20 minutes ago

  I was telling a friend that @github needs to be replaced post agents and he asked me to explain why. I started stumbling, and doubting. Perhaps it's fine? Sitting down at my desk, let me try to explain why, and see if it make sense. Agents operate best when they have good context, which has made a lot of devs converge into large monorepos that combine all systems into a single location. This improves agents, but our GitHub actions become messy; like now we need to create these complex workflows to decide which action should run when, and GitHub's setup was not really meant for it. Another issue is the overall dev loop: an agent writes the code locally, you push out a branch, @cursor_ai reviews, then you copy paste the notes into the local agent, to fix and push up again. This is slow and cumbersome. You can hack your way by creating supervisor agents that orchestrates this dance, but it's annoying. Perhaps, there is some magical repository, that combines code, cloud agents, and deployment. You prompt, and this magical space will run through the entire process until you get some thumbs up back, and you're good to go. It can also combine all your backend data, product analytics, customer feedback, and perhaps start giving you product guidance, so you can just feed prepared prompts to this system. This seems magical.

• 
  KS Sreeram (@kssreeram) reported 22 minutes ago

  @Lidinwise @leecronin Given that AI coding is all the rage… What is your hypothesis on why the following is true? AI is unable to create even _one_ open source project that’s good enough to enter the top one-thousand open source projects (say on github), with ZERO involvement of humans from birth of idea. Imagine the prompt being something like “Come up with a great idea for a new open source project and implement it”. AI is unable to do any such thing with zero human involvement. My answer on why: Every project in a top 1000 list is a hit. Every hit is a mini-invention of sorts. It is necessarily “out of distribution” is some way. AI is unable to do this because we don’t know how to solve the problem of invention.