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:

• 
  Moit Reghason (@MoitReghason) reported 7 minutes ago

  Everyone’s celebrating agents trading tokenized stocks on Robinhood Chain. Few people are asking what happens when the infrastructure underneath those agents gets compromised. @cursor_ai recently disclosed CVE-2026-50548, a zero-click remote code execution vulnerability where a poisoned MCP response could disable the sandbox and execute code on a developer’s machine. That’s not a hypothetical attack surface. That’s the environment where agent infrastructure gets built. And it’s not an isolated incident. ➠ mcp-pinot-server carries a CVSS 10.0 unauthenticated RCE vulnerability. ➠ Kong’s mcp-konnect allows indirect prompt injection through poisoned data that can steer agent API calls without the user realizing it. ➠ mcp-memory-service exposed unauthenticated endpoints capable of leaking sensitive agent memory data. Each vulnerability adds another entry point to the same expanding attack surface. The recent Taiko bridge exploit made this painfully concrete. $1.7M was drained, not because the cryptography failed, but because a private key was committed in plaintext to a public GitHub repository. The SGX enclave performed exactly as designed. The operational discipline didn’t. What this means for the agent economy is that security debt compounds with every new integration. Cisco’s State of AI Security 2026 found that 71% of organizations are running unmonitored AI agents with broad MCP access. OWASP’s recently published MCP Top 10 found widespread issues across the ecosystem, including path traversal vulnerabilities and extremely limited adoption of standardized authentication mechanisms. As agents gain wallet-signing authority through ecosystems like @virtuals_io and agent key management systems such as @KeeperHubApp, the blast radius of a single operational failure grows proportionally. A private key left in a public repository could drain an autonomous agent treasury just as easily as it drained a bridge. The uncomfortable reality is that the weakest link in this stack was never the cryptography. It was always going to be the person who committed it.

• 
  █████ (@CrunkComputing) reported 11 minutes ago

  In *** web interfaces, README.md should always be visible above the fold, in the initial viewport. README is naturally the first thing anyone would want to read first. No one should have to scroll down to read it. There, I said it. @gitlab @github

• 
  SYL Vexora- Jaron K Bragg (@JaronBragg) reported 12 minutes ago

  Thinking out loud: if a Three.js world is backed by Supabase, Vercel, and GitHub, then player feedback does not have to stay separate from development. A player could press an in-world feedback button. That writes to Supabase. A scheduled agent reads labeled feedback, turns it into issues or draft PRs, and approved changes get pushed back into the game/world. Feedback becomes part of the build loop, not just comments outside the game. Has anyone already wired this cleanly? I'm at max usage for Claude and codex and already spent $70 I can't check till Wednesday but I plan to! I've done things in pieces already it's just seeing it all together. If you do it please tell me!!

• 
  Pawan Pandey (@BuildWithPawan) reported 12 minutes ago

  Then pick where it goes: log it as a row in a Google Sheet, save it to Drive, or create a GitHub Issue (with labels) and push it into a Project — or send it to more than one destination at once

• 
  Roshan Mayengbam (@RoshanMayengba) reported 13 minutes ago

  Building a shake-to-report tool — screenshot + device info + auto GitHub issue when a tester finds a bug. Free npm package, paid setup. Anyone dealing with messy bug reports from testers right now? #buildinpublic #mobiledev #indiehackers

• 
  Harsh Verdhan Singh (@harshsagee) reported 19 minutes ago

  People solve leetcode problems daily and posts that they are coding for a week, month or year. Bro show GitHub, that's where real code is written not in the leetcode.

• 
  Abdulsalam Lanre (@Abdul_Lanre001) reported 25 minutes ago

  @Saanvi_dhillon I'd still go for GitHub streak cuz some Devs just memorize these solutions to leetcode it's not like they can actually solve the problem or any related problem, just cramming the questions and the answers. It's not about leetcode but the application in their real projects.

• 
  Mitali Gautam (@Mitali9826) reported 25 minutes ago

  @akshdeeps_001 Yes! It detects duplicate GitHub issues using dual signal one for natural language and one for code then fuses them for better matching, instead of relying on a single generic embedding like GitHub's current approach

• 
  StonedModder (@StonedModder) reported 26 minutes ago

  @TaharAzzouz @Jdr8245Jhon I’m working on a generic dumper that will make it easier for others to add support if you share the dump to github issues No eta

• 
  Utah teapot 🫖 (@SkyeSharkie) reported 28 minutes ago

  BTW, feel free to use twitter as a bug reporting system for SeedThree and my upcoming release! Please also feel free to fix bugs yourself with your agents or not and send me a PR on github!

• 
  AcceptÐoge (@DogeAccept) reported 28 minutes ago

  @MoonlitMonkey69 @probablyluda 1. is an L2 bridge, settles before L1 (dogeos is not fully l2, "app layer, l2ish) 2. is L1 integration "bridging directly to Dogecoin" to settle. ZK integration on L1 could add potential vulnerabilities. L2 wouldn't be "on doge," wouldn't be decentralized at first and you must trust. This post is saying that people have an issue with l1 integration but also have and issue with a permissioned, custodial bridge. I say that people are or should be well aware of what theyre using.. its creators should have no problem being transparent to anyone interested in using it. It is a choice to use this bridge and the tech should be able to be questioned openly so people know exactly what to expect especially when they are trusting. L1 integration should more so be able to be discussed openly beyond a proposal in discussions on github that has been there for a year especially when the people "building" it are currently clearly talking about different tech publicly than what that proposal mentions. We vote with node updates, yes, but as an open community of countless people.. not everyone can or has the ability to run a node. The obvious is that Dogecoin is permissionless when it comes to introducing code to core. That is why we have maintainers to screen and our network itself is the consensus mechanism. However, our community is unique and we have no leaders or voices beyond the community itself. If we want to discuss things like this, we just do. Its messy but its always been open dialog that educates, innovates, and somewhat of a social concensus when it comes to how the community as a whole would or would not like to see a direct of a coin that all of us support goes. Our voice matters too. I have done my best to ask about very specific topics to the right people even when I cant ask the person writing the code directly. I have tried that too, in good-faith, even when I dont agree with them. I have been met with nothing but assumptions, character assassination, empty promises of good-faith conversations or responses and ultimately being blocked by all of them, always right after false accusations. If we cant talk to the builders, if they are not transparent, if we cant discuss with each other, or question the things being shilled to us when we have no leaders.. Can we even call ourselves a community?

• 
  Polsia (@polsia) reported 28 minutes ago

  Security vulnerabilities still ship because review cycles can't catch everything. Built CodeSentinel to fix that. It monitors GitHub repos 24/7, flags risks, summarizes changes, drafts PR descriptions. Ship fast, stay secure. Live soon.

• 
  WithChloe (@Chloe_yara123) reported 30 minutes ago

  @Xcxy888 The main issue is that there are just too many resources on GitHub, and I don’t know how to find exactly what I’m looking for.

• 
  Chloe Bennet (@chloeb_dev) reported 30 minutes ago

  @shreyayyyy reading a ten year old github issue validates the exact same feeling someone else was just as confused by the documentation and exhausted by the dependencies the ticket is still open

• 
  Federico Ulfo (@feulf) reported 31 minutes ago

  @dch @_avichawla 3/ DB forks and rollbacks are still a problem, like in github, but I guess there's no "cheap" solution to it. Question: Curious, why not combining gitsubtree + prompts-history-{***-sha}.jsonl + a skill to manage them?