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:

• 
  brick (@werdcel) reported 1 minute ago

  @igama GitHub is old fashioned because it’s made for humans to look at and review code. It solves problems that are going away. In five years it will be laughable to use something like what GH is today. It’s just going to be a headless service agents use.

• 
  Luke Steer (@lukeasteer) reported 2 minutes ago

  When GitHub Actions breaks, you should be able to watch a livestream of their engineers hurriedly implementing a fix

• 
  Vaibhav - building Needle (@iamvs2002) reported 3 minutes ago

  The real signal already exists. It’s buried in: • Reddit threads • X replies • GitHub issues • Community discussions You just can’t find it properly.

• 
  Aman Saxena (@aman7heaven) reported 6 minutes ago

  I was terrified of 4 things as a fresher. Only 1 was true. ❌ Max DSA problems solved ✅ GitHub contributions ❌ Every certification you can grab ❌ College tag doesn't matter Wasted 6 months scared of the wrong 3 when I was in college.

• 
  Simplifying AI (@simplifyinAI) reported 8 minutes ago

  Your AI coding agent doesn't need a library for a date picker. Ask most agents for one and they install flatpickr, write a wrapper component, add a stylesheet, and start a whole conversation about timezones. Ponytail makes the agent check a 7-step ladder before writing anything: does this need to exist, is it already in the codebase, does the standard library do it, all the way down to the minimum that actually works. For a date picker, that lands on: <input type="date"> There are two ways to install it. Option 1: Claude Code /plugin marketplace add DietrichGebert/ponytail /plugin install ponytail@ponytail Runs automatically every session once installed, no config file needed. Option 2: Codex codex plugin marketplace add DietrichGebert/ponytail codex plugin add ponytail@ponytail Also works with GitHub Copilot CLI, Gemini CLI, OpenCode, Cursor, Windsurf, and over a dozen other agents. Measured on real Claude Code sessions editing an open-source FastAPI and React repo: 54% less code on average, 22% fewer tokens, 20% cheaper, 27% faster, with no drop in safety checks like validation, error handling, or accessibility. 100% Free. Open Source.

• 
  Wade (@TalentedSun4404) reported 8 minutes ago

  @witcheer I’m using Obsidian for my primary Hermes. I just setup another on a different device to tinker with. Obviously now I have the issue of two obsidian vaults. I might set it up in GitHub to “sync” them… I was also curious if Notion could work in place of Obsidian.

• 
  Mac (@mac_eth) reported 10 minutes ago

  @farizvect I wanted mine to investigate 6 different automated alerts. It tied with subagents and failed bc of: 1) limit on number of subagents 2) 10 min timeout on the subagents Also we have 200 "TODO" github issues -- I'm looking for something that can do them by tomorrow morning. And Hermes said that's too much for it lol.

• 
  Romir Jain (@romir_jain) reported 15 minutes ago

  finishing tether v0.12.0 — the part that's all plumbing and no glory wrote the changelog for the reflex → tether rename. PyPI dist moved to fastcrest-tether, CLI/imports switched to tether, but existing integrations can't just break overnight. so every old import path gets a compat shim that still works through v0.13.x with a DeprecationWarning, removed in v0.14.0. env vars like REFLEX_PORT silently mirror to TETHER_PORT. making a package rename non-breaking is 90% tedious forwarding code that nobody sees added SECURITY.md scoping robot-control network endpoints as high-priority. tether serve is where controllers POST camera frames and get back joint commands at 20Hz — a vulnerability in /act isn't someone reading data, it's someone commanding physical hardware. 48h acknowledge, 7-day fix SLA. only latest minor supported because we're pre-1.0 and backporting security patches across old branches isn't realistic yet set up dependabot for weekly pip + github-actions scans. also cleaned internal outreach/ and launch/ dirs out of the sdist — pitch decks were literally shipping inside the pip package ~20 PRs into this release. the fun stuff was the model bugs and runtime hardening. this is the packaging tax that makes it actually shippable

• 
  Aviinfinity (@aviinfinity) reported 16 minutes ago

  @msnofficial_on Open a github issue

• 
  Alexey Fateev (@superalesha) reported 17 minutes ago

  @xhinker I don’t understand what the problem is. The full launch instructions are on GitHub.

• 
  Mukul Malik (@lazyynocturnal) reported 18 minutes ago

  Another use case: - Ask to sol first to identify the top 25 frontend bugs/issues that are easy for an agent to test end-to-end, then log them as GitHub issues with all needed context. - Review them with fable to catch any edge context missed. - Then ask your chief of thread to split the work into a few parallel threads so they can work accordingly.

• 
  Nestor Lab (@NestorLab44) reported 18 minutes ago

  Hermes just made a move that changes the game for everyone building agents. The announcement: Hermes now supports portable plugins using the Agent Plugins v1 standard, already adopted by Vercel, Cursor, OpenAI, and Microsoft. The idea is simple: create a plugin once and make it work across multiple agents. A portable plugin is just a folder with a plugin.json, a skills/ directory, and sometimes an mcp.json. It supports both Skills and MCPs. Before this, you couldn’t import these packages into Hermes. Only native plugins worked — more powerful, but locked to one tool. Take a concrete example with GitHub. Until now, setting up Hermes to interact with GitHub (list issues, review a PR, read commits) required manual configuration. Now a portable package handles the connection directly. And the exact same package also works on Cursor or Claude Code if you switch tools. The main benefit is interoperability. No more rewriting the same integrations for every agent. Hermes already supported MCPs through the config file. What’s new is the simplified installation as shareable packages. #hermes

• 
  devvaibhav (@devvaibhav37) reported 23 minutes ago

  This is actually wild. Researchers found that malicious instructions hidden inside public GitHub issues could trick AI coding agents like Claude Code, Gemini CLI and Codex into doing things they shouldn't. In some cases, this could lead to credential theft, code execution and repository modification. The scary part? The attacker doesn't necessarily need to hack the AI itself. They just need to get the AI to read something malicious.

• 
  Oliver Servín (@oliverservinX) reported 25 minutes ago

  I've built my own blog more times than I can remember. Every time it went the same way. I'd be happy with it, publish a few posts, then drift away. I kept renewing the domain, but eventually I'd delete the VPS behind it. The address stayed alive, pointing at nothing. And I'm fine with that. An old blog is a snapshot of an older me: the things I cared about, the tools I used, the writer I was. When it doesn't fit anymore, letting it expire feels more honest than keeping a neglected archive. What bugged me was never the abandoning. It was that every time I had a new post ready, the blog was gone. I'd have to rebuild one from scratch before I could put a single word out. So this time, with a finished draft and nowhere to put it, I thought about Bearblog, a platform built on the idea that a blog needs almost no CSS and almost no layout: a header, a list of posts, a page for each. That's what I wanted. And I figured an AI coding agent should make rebuilding it almost free. So I pointed OpenCode at it and asked it to build me one. I started from a fresh `laravel new`, the same way I start any project. What I didn't expect was that I'd end up taking more out than I put in. The trade-off isn't free. Skipping a commercial platform means the server and the app are mine to keep alive, the same maintenance that made me walk away before. I'm OK with it. What's different now is that coming back doesn't mean starting over. Here's what happened. I didn't design a blog. I pointed my agent at one, and that's the whole method. What came back surprised me. It didn't just copy the layout. It came back as Herman's blog. Herman is the person behind the Bearblog site I used as a reference, and the agent pulled his real content: his name on the about page, his projects, his posts, the newest ten in full. A working prototype of someone else's site, running on my local machine. The agent copies what you point it at, and I'd pointed it at his. His posts turned out to be useful scaffolding. I dropped my own draft into the same shape. From there it was just steering. Replace his content with mine, drop his posts. Where the agent hadn't built something, it left a placeholder, like a `#` where the XML feed was supposed to go, and let me decide. I asked for the feed and it built it. I skipped the contact page and used a plain mailto link. I picked what to keep. It even interviewed me. To fill in my about and "now" pages, I had it ask me questions: my name, what I do, what I'm working on. Talking it out with something, even an agent, surfaced content I couldn't just write cold. Bearblog's approach is CSS embedded right in the layout, no external stylesheet. So my layout just doesn't load the Tailwind `app.css` Laravel ships with. Posts aren't in a database either. They're flat Blade files, just HTML, no CMS, no components. My production footprint ended up smaller than my starting point. I took more out than I put in. That's also why I think this one sticks: less moving parts means less to break and less to keep updated. No database to back up, no CMS to patch. The upkeep stays small because the blog itself is small. And that's the whole bet. The thing that killed every blog of mine wasn't the abandoning. It was the cost of starting fresh. A blog this small is cheap to rebuild. Deploying was the easy part, because my VPS was already set up. I run Eddy, a self-hosted server management panel, alongside other Laravel projects. Adding the blog meant creating a site, pointing it at the repo, and deploying. The setup is the only hard part of self-hosting, and I'd already done it. Start to live was maybe an hour. I don't remember exactly, and that's the point. It moved fast enough that I didn't have time to procrastinate before the post was up. If you want to do something like this, there's not much to it. Point your agent at a reference you like, let it copy, and you have something to work from. Take out what you don't need, add what you do. Publishing works the same way. To put up a new post, I point my agent at an existing one as a reference. It writes the new one in the same shape, adds the slug to my blog controller, commits, and pushes. Then I open Eddy and click deploy. That's it. I could set up a GitHub Action to auto-deploy on push, but I haven't yet. Manual first, automate later. Same way I ship the writing. The real thing that kills a blog isn't the upkeep. It's whether you keep showing up. So make it a place you actually want to come back to. What I know works is pointing an agent at something you like and letting it copy. I'm not sure what else they're good at, but copying works. And maybe the bigger thing. It's fine for stuff to end. I publish now. If this blog rots someday, I'll make another one in an afternoon. I don't need it to last. I just need to be able to make it again.

• 
  Orlixx (@orlixx003) reported 31 minutes ago

  openai is giving away 6 months of chatgpt pro + codex to open source maintainers for free if you maintain a public github repo this is worth 5 minutes of your time the program is called codex for oss what you get: → 6 months chatgpt pro including codex ($1,200 value) → access to codex security → api credits for development, maintenance automation, and release processes what they want in return: nothing. you just have to actually maintain something the application takes one form. github username, repo url, your role, why the project is compliant open source maintainers carry massive responsibility for free. reviewing pull requests, triaging issues, keeping code secure for thousands of people who depend on it this is openai's attempt to give something back if you've got a public repo with actual users, this is free money and free compute apply before it closes