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:

• 
  Vatsalpandya333 (@Vatsalpandya333) reported 8 minutes ago

  A production bug rarely lives in one place. The customer report is in support. The discussion is in Slack. The error is in Sentry. The evidence is in logs. The change is in GitHub. The timing is in deploy history. The information already exists. It is just fragmented. The future of incident response is not another dashboard. It is one context, one timeline, and one workflow. That is what we are building at @TasksMind .

• 
  jbz (@jbzfn) reported 10 minutes ago

  🦜 Pearson's Anti-Piracy Vendor Takes Down Best-Selling Author's Own GitHub Repo * TorrentFreak

• 
  THE CLIPPERS (@crypto_GO_blinz) reported 16 minutes ago

  Extensibility is massive. 30 active connectors (GitHub, Notion, Postgres, Puppeteer, Playwright) with Model Context Protocol (MCP) server support. Plus, the whole thing is MIT-licensed and built in public by @Idov. You can inspect, modify, and self-host everything.

• 
  Evgenii Burmakin 🗺️ dawarich.app (@freymakesstuff) reported 17 minutes ago

  I'm actually surprised I haven't got new github issues after the release 🧐

• 
  Sam Z Liu (@samzliu) reported 18 minutes ago

  There's a huge problem with agent skills. It's that there's no costly signaling. This is a concept from game theory that explains why male peacocks have huge feathers at the expense of mobility or why the devoutly religious subscribe to such onerous obligations. When it's hard to tell whether something is actually valuable, the cost another has paid for it is a reliable and honest signal. Only healthy, fit peacocks can afford to have such tail feathers because it is so expensive to maintain. Code used to be a pretty costly signal: it takes time and energy to write and even more to maintain. This meant that as long as the code ran reasonably, you could be sure there's some level of competence and thoughtfulness to the design (although anyone who's poked around at open source GitHub repos might argue otherwise!). The economics are completely different in the agent-era, and skills are an extreme example of this. It takes almost no energy to write a skill that works ok, and it is extremely hard to tell whether it is slop or slaps. The knockdown effects harm the ecosystem as well: There are whispers of game changing skills and yet none of them seem to actually work much better than the raw model. Skill sharing is a ghost market with lots of sellers and hype but no one buying. Thus, there's no way to reliably compound skills over time. They become this public-private asset: Public because it's easy to share to gain clout. Private because no one else actually finds it useful besides you.

• 
  regent0x (@regent0x_) reported 22 minutes ago

  guy drowned his GPU rig in coolant and it now pulls $127k/month the whole stack sits submerged in liquid, running a claude agent wired into github, postgres, slack and gmail at the same time the immersion cooling lets it run flat-out 24/7 without ever throttling - which is the only reason it can handle the load it does the video looks fake - cards fully sunk in fluid, bubbles streaming off the boards, gold risers glowing under the surface. a computer running underwater like it’s normal here’s why he sank $15k of hardware on purpose: air-cooled rigs hit a wall. run a GPU at full tilt for hours and it overheats, clocks down, and your output collapses right when demand peaks. submerge it and that wall vanishes - the cards never step down, never slow, never sleep that stability is what let him stop selling per-client and start selling per-seat to a single company what changed his pricing entirely: instead of 40 small clients, he landed 3 mid-size firms and charges per employee using the system → github MCP reads repos, opens PRs, reviews code → postgres MCP (read-only, always) answers data questions live → slack MCP posts updates and summaries → gmail MCP drafts client replies for approval each firm runs 60-90 employees through his rig, every one hammering the agent all day. air cooling would’ve melted trying to serve that concurrency. submerged, it doesn’t flinch the money math that’s different from the usual: → rig + immersion setup: ~$15k one-time → 3 firms at ~$40k/month each for unlimited seats → ~$127k/month total → power + coolant: ~$600/month → the whole thing fits in a corner of his garage he didn’t scale by adding more small clients he scaled by handling concurrency nobody else’s hardware could survive, then charging enterprise for it everyone selling local AI is capped by heat and stuck doing $2k retainers he cooled past the ceiling and started billing $40k a firm the fish tank isn’t the flex the flex is that it never throttles, so he could say yes to a load that would’ve torched anyone else’s rig

• 
  Jason Fleagle (@jjfleagle) reported 22 minutes ago

  @github @Atlassian Jira can become more than the place an agent reports progress. The issue should carry scope, repo and environment boundaries, acceptance tests, approvals, evidence links, exceptions, and final disposition. Then the work item becomes the control record through release.

• 
  Andreas (@AndJakobsson) reported 22 minutes ago

  I did set up a kind of Obsidian second brain structure for my notes with my Hermes agent directly on my VPS. Now I wonder if it is not just better to have the whole thing directly in markdown files on GitHub. I could have agents updating it directly and between projects, issues and discussions, if properly structured it will probably work really well. Is anyone else doing this?

• 
  Param (@ParamSiddh) reported 27 minutes ago

  GITHUB JUST KILLED THE WORST PART OF VIBE CODING they shipped a free tool called Spec Kit and it already crossed 120,000 stars the fix is stupidly simple instead of tossing vague prompts at an agent and praying it doesn't wreck your project Spec Kit makes the AI write a full structured spec before it touches a single line of code it works through the problem first figures out what you want to build asks about the gaps lays out the project then it starts coding you get fewer insane bugs, cleaner output and results you can predict the flow looks like this: /constitution for your rules and standards /specify for what you want to build /clarify for the open questions before you start /plan for architecture and stack /tasks for the ordered work /implement to run it it plugs into Claude Code, Cursor, Copilot, Codex, Gemini CLI and 25+ other agents 120,000 stars, 10,000 forks, open source, shipped by GitHub itself learning to drive agents like this is most of what separates people getting hired as AI engineers from everyone still fighting their prompts

• 
  Harman (@itsharmanjot) reported 29 minutes ago

  Google just published an open standard for how knowledge bases talk to AI agents. Most of the early tooling around it is scattered, MCP servers, converters, plugins. This is one of the first that actually publishes it as a real website. Someone turned a folder of chaotic notes into an AI-readable knowledge base with an obscure open-source tool, and there’s zero vendor lock-in anywhere in it. It’s called Kiso. A static-site generator for the AI-agent era: you write your knowledge base in the Open Knowledge Format, and Kiso turns it into a site readable by both humans and AI agents at the same time. → Takes an OKF bundle, just Markdown files with YAML frontmatter, no proprietary format, and builds a navigable static site with structured navigation → Every generated page links back to its original Markdown source, so nothing gets lost between what you wrote and what gets published → Auto-generates llms.txt and sitemap.xml on build, so the site is structured for AI crawling from the start, not added on later → Ships a check command that validates your Markdown against the OKF spec before you publish, catching structural errors early → Drops into a GitHub Action, so pushing a commit can automatically rebuild and redeploy your knowledge base to GitHub Pages or any static host The idea behind OKF, published by Google Cloud’s Data team in June 2026, is that a knowledge base shouldn’t be locked into one vendor’s catalog or SDK. It’s just Markdown files in ***, readable by any agent that supports the spec. Kiso is an independently built tool, not a Google product, that turns that idea into an actual publishing engine.

• 
  Marc-André Moreau (@awakecoding) reported 34 minutes ago

  @penberg @domenkozar Just open issues on the Turso GitHub and then paste the links in here, I can give it a shot

• 
  MewCP (@mewcp_ai) reported 34 minutes ago

  2) Imagine an agent connected to an approved GitHub MCP server. You ask it to "clean up the repo." It merges PRs, deletes branches, and closes issues—including work that was never pushed. Nothing was hacked. Nothing was malicious. The agent simply did what it was allowed to do.

• 
  Matt Van Horn (@mvanhorn) reported 35 minutes ago

  @WilliamGendron @steipete I'm with you unless it's clearly been reported first by someone else (i.e. github issue someone else reported with date stamp first) though that's not how bug bounties work bc they are meant to be private

• 
  Alaa Elsamouly (@sam0uly) reported 37 minutes ago

  @samirande_ fix your github fetching bro

• 
  DeFAI Scope (@defaiscope) reported 41 minutes ago

  GPT-5.5 holds at zero percent reward hacking across every effort level on DeepSWE, while every other model's hacking climbs alongside its capability. That looked like clean design until the same model hit a different benchmark. ➥ DeepSWE, fix a GitHub issue: GPT-5.5 at 0%, Fable 5 past 9% ➥ SWE-Marathon, open-ended missions like rewriting a C compiler in Rust: GPT-5.5 at 26.5%, the highest of anything tested A patch has a narrow definition of done. A mission doesn't, and GPT-5.5 takes advantage of that gap more than any other model.