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:

• 
  Waldek Mastykarz (@waldekm) reported 3 minutes ago

  A new model drops with lower per-token pricing and better benchmarks. You switch. A week later someone asks why the agent is burning 12x more tokens on the same task while producing worse output. We ran 150 agent tasks across 15 scenarios on Sonnet 4.6 and Sonnet 5 using GitHub Copilot in VS Code. Sonnet 5 has 33% lower per-token pricing across every category. The assumption: newer and cheaper means better. On architecture tasks, Sonnet 5 used 12x more tokens at the median. One run consumed 47x the typical volume. A 33% per-token discount doesn't survive a 12x increase in consumption. Quality didn't improve either. On the 9 architecture scenarios where both models produced usable output, the older model scored 90% on our Idiomatic dimension versus 78% for the newer one. More tokens, worse quality on the majority of scenarios. On code upgrade tasks, the picture reversed. Sonnet 4.6 passed the Select gate 60% of the time. Sonnet 5 passed 100%. When the task requires following a specific instruction over what the model finds in context, the newer model was more reliable. But both models hit the same quality ceiling on configuration correctness: 0%. Neither could complete structural migrations that aren't documented in one place. Spending more on a newer model doesn't fix a content gap. A model upgrade is a hypothesis. You won't know which side your workload falls on until you measure it.

• 
  Namma Chennai (@NammaChennai_) reported 5 minutes ago

  @Sir_Kuruvi @trilokchronicle @AdiSpeaX GitHub link not working?

• 
  Moit Reghason (@MoitReghason) reported 7 minutes ago

  I think the strongest version of this is to preserve your argument, but make the progression clearer: celebration → evidence → pattern → implication → conclusion. Here’s how I’d refine it: ⸻ 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 all this was never the cryptography. It was always going to be the person who committed it.

• 
  Aria Dubois (@AriaDubois_fr) reported 8 minutes ago

  MergeFund turns GitHub issues into funded bounties. Sponsor posts a bounty → Dev claims it → Submits a PR → AI reviews the code → Sponsor accepts → Payout. No more merging blind. No more paying for broken code.

• 
  hustler one (@hustlerone4) reported 10 minutes ago

  alright one big nightmare with omp is its issue:// pr:// and other helpers are all hardcoded to use github, doesn't seem to be able to switch it to another provider via config

• 
  Dan Kornas (@DanKornas) reported 13 minutes ago

  Your Unity agent shouldn’t stop at editing C# files. MCP Unity is a Model Context Protocol implementation for Unity Editor that connects AI coding assistants like Cursor, Claude Code, Codex CLI, Windsurf, GitHub Copilot, Google Antigravity, and OpenCode to Unity projects. It helps you automate editor work by exposing Unity scenes, GameObjects, assets, logs, packages, and tests as MCP tools and resources your assistant can call. Key features: • Editor bridge – Unity package plus Node.js MCP server lets MCP clients send commands into Unity Editor • Scene + GameObject control – create, load, save scenes and select, update, duplicate, move, rotate, scale, or delete objects • Component/package/material tools – add packages, update components, create prefabs, and create/assign/modify materials • Tests, logs + resources – run Unity tests, inspect console logs, and query hierarchy, packages, assets, and test metadata • Client setup paths – includes Unity Server Window configuration plus manual/project-local configs for major MCP clients It’s open-source (MIT license). Link in the reply 👇

• 
  Peter Pistorius (@appfactory) reported 14 minutes ago

  I built a tool that helps me "review the review bots." It does 3 things: 1. Gathers the PR and review claims. 2. Controls the browser and records a video of the PR claim. 3. Tests every review claim by attempting to reproduce. Now the review is grounded in evidence. I review the evidence. 1. I can chat with AI about each claim and gather more context. If I'm satisfied with my own understanding of the issue then I respond and hide the comment in GitHub. 2. I review the video step-by-step to see if it matches the PR claim. If not, I can chat with just that PR claim to gather more evidence. This gives me great calm.

• 
  David Uchenna (@callmidavid) reported 15 minutes ago

  @JohnOlorun90448 Um, not sure you read the instructions correctly I’ve been using it since morning Mind creating an issue on GitHub or sending a DM?

• 
  siyamak (@siyaaaamak) reported 16 minutes ago

  One belief almost everyone in crypto repeats is: "The best product always wins." I don't buy it. I've watched technically brilliant projects disappear because nobody knew they existed, while simpler products exploded because they built distribution first. Great tech matters. But if nobody sees it, uses it, or talks about it, it doesn't become infrastructure. It becomes another GitHub repository. That's why I think @RallyOnChain is tackling a real problem. Web3 has spent years obsessing over building and not enough time rewarding the people who actually explain, educate, and distribute those ideas. The crowd says product is everything. I think distribution is what decides who survives.

• 
  Abdulsalam Lanre (@Abdul_Lanre001) reported 18 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.

• 
  Esther Crawford ✨ (@esthercrawford) reported 20 minutes ago

  A year ago I wouldn’t have believed our iOS workflow would simplify to: describe an issue in Slack and tag an agent who picks it up, fixes it, and then sends a message a few minutes later with the GitHub PR letting us know it’s done. The magical becomes the mundane so fast.

• 
  Kirill (@kirillk_web3) reported 22 minutes ago

  75K GitHub stars. Two weeks. Most people still burning tokens on 500-line answers to 5-line problems. Ponytail makes Claude think like the laziest senior dev on the team. Writes less. Skips what you don't need. Keeps every line that matters. 54% less code. 20% cheaper. 27% faster. One skill. Swap it in. Claude starts working differently. Save this before you watch Claude over-engineer one more time. Bookmark this now. Link below.

• 
  █████ (@CrunkComputing) reported 23 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

• 
  Atharva (@attharrva15) reported 23 minutes ago

  @ivanburazin A guy ( i won't name) invited me for a talk for a freelance position (he saw my GitHub, might have liked me) and I prepared for it, studied his codebase, told my mum to not come in my room for 30 mins, and the guy never came, and ghosted me. I don't care if you don't wanna work with me, or you have problems- just ******* be clear.

• 
  Howard Young (@howard_o_young) reported 24 minutes ago

  @Warizo_ofAfrica @github @cassidoo Simply issue-# then remove the worktree and delete the branch after pr closure.