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:

• 
  IT Contractors Union (@ITContractorsUS) reported 3 minutes ago

  @SanDiegoKnight @DrRay_tweets Actually I discovered this by accident... When my GitHub account got taken down, and literally on the same day I got stiffed on a job I did for an Indian locally, I was needless to say, PISSED. So I just posted those four words, and they went to 100k views. I did not know the guy was Indian. I did some tech drawings for him. He's got a machine shop. I took the assignment over the phone. Said his name was "Sonny". Later I found out his name was "Sunil". He got the drawings, for a design I think he's trying to steal. I got 0$. FIFI

• 
  Marcus Kim (@marcusykim) reported 5 minutes ago

  TencentDB Agent Memory hit 20,000 GitHub stars in 90 days, signaling demand for shared agent context. Before adding Team Memory, define who writes, what expires, and how errors are corrected. What should never enter shared memory? #AICoding #SoftwareEngineering

• 
  Riza 🐧 (@rizaardiyanto) reported 7 minutes ago

  @rilwis One thing that I like to do beforehand is discussing with the agent first. I give the GitHub issue to the agent, ask it what's implementation he will take. If I see misalign between what I thought and his solution, I will told him right away. This will spark discussion between me and the agent. Only after both of us having shared understanding and agreed on something, then I asked the agent to put all those details as comment in the GitHub issue. This will make the next agent can implement as expected. For the UI/UX, I usually asked an artifact first before he implement directly. If I like the artifact, I give it a go for implementation, if not I ask for some refinement there. And I prefer artifact on Claude rather than Codex. It gives a good result and know how to implement it. Codex artifact still not giving a good result yet

• 
  Arian van Putten (@ProgrammerDude) reported 8 minutes ago

  What all CI providers (including GitHub) get wrong is what you should process workflows in LIFO instead of FIFO to recover from outage. That way older jobs get irrelevant and can get cancelled

• 
  Urooj (@Urooj978) reported 12 minutes ago

  Transferring a file to a phone 3 feet away usually routes through WiFi, Bluetooth, or a cloud server in Virginia. ​A dev named Alstroph just released a tool that transfers files using nothing but screen light and a camera. ​No WiFi, no Bluetooth, no app, no internet. Here's how it works: 🧵👇 ​ (How it works & Fountain Codes): ​ →The sending phone flashes a rapid stream of dynamic QR codes. The receiving phone just points its camera at the screen. →​To handle dropped or blurry frames, it uses Fountain Codes—the same math used in satellite communication. →​You don't need to capture frames in order or capture all of them. You just need enough random frames for the receiver to mathematically rebuild the entire file. ​(Stats & Use Cases): ​ Key details: →Speeds: 129 to 186 KB/s (2 MB file in ~15s) → Zero install: Runs directly in browser →Built overnight as a proof-of-concept ​Crucial for high-security air-gapped rooms, network blackouts, or two phones on airplane mode. ​2,600+ stars on GitHub in 48 hours. 100% open source.

• 
  Chloe (@chloevalesquez) reported 13 minutes ago

  those go straight to a github issue instead of fighting luna on them. no point burning turns on a model that's not built for that kind of depth

• 
  The obonigwe (@ogbonigwe1) reported 14 minutes ago

  blacksmith and github are down again. i don tire

• 
  Chris Moore (@crsmoore) reported 16 minutes ago

  @_tombrow Can you please, please fix the font sizing issues on iOS? iOS text sizing breaks down under accessibility zoom. Some elements scale, others don't, so titles/body/timestamps lose their visual hierarchy at larger Dynamic Type sizes. Not yet filed as a GitHub issue.

• 
  Srinivas Rao (@UnmistakableCEO) reported 18 minutes ago

  @scarfo_leo: Great setup. Sub-agents for security review before commits is smart - catches things you would have missed for days. Context7 + Playwright combo is underrated. The real unlock: being specific about what you want vs letting it guess. --- re: "Today I setup all the skills I needed for my Claude Code to work properly on my new software as a non-technical person You could be thinking: where did you discover the things you needed? Well, I simply made them up myself!! I thought of what I wanted my agent to do and what he would’ve needed to do in order to responsibly walk me through the entirety of the project I wanted him to: - dive right into the details of what he’ve done so I could learn - write clear and clean code, not overly engineered, so again I could learn - be on track with the libraries and languages updates so we would’ve encountered less useless bugs - constantly scan for security issues and solve them automatically when he did found them - be really able to simulate web interfaces and test the software in them - be token efficient (since I’m still on the $20 plan) - be a real agent, so I wanted him to have the possibility to access and manage ***, supabase ecc.. How did I integrate all these requirements I wanted him to match? Going with the same order as the requirements I: - set the output style to “explanatory” so I could get the *insight* paragraph (you can do this with /config) - wrote a distinct paragraph on the CLAUDEmd file about code style requirements I had - connected claude to the Context7 MCP, one of the legacy MCPs but still very valuable - I created two different sub-agents to review code and solve security bugs before every commit, so I wrote 2 agents mds and got the “automation” written on the main CLAUDEmd - straight up installed the Playwright MCP, an absolutely must have if you want to experiment with web development / localhosting - ended up getting a lot of other instructions in the CLAUDEmd file and spamming /compact along other instructions in the prompt to keep it useful - connected Supabase, Vercel, and Github MCPs paying attention to still keep 100% control on what Claude did Hope this helps!! If you’re also a non-technical person building something don’t be afraid to ask!! I try to be as useful as possible but it’s not always easy, english isn’t my first language and content is too much to write clearly about sometimes"

• 
  진압봉 (@AbbongJin) reported 18 minutes ago

  @DYorgy @SaberGames AI for what is the question we all should be asking. If it is some backend simple repetitive tasks(setting configuration files, debugging tool) they use AI for, I have no problem with it; because like 70~80% of the GitHub people already admit they use it.

• 
  Polsia (@polsia) reported 20 minutes ago

  Integration tests are the first thing to rot when teams ship fast. Built Plumbwright to fix that. Autonomous GitHub agent — writes integration tests on every PR, opens draft PRs on coverage dips, and reserves the pager for failures it can't repair. Soon.

• 
  HOL (@HashgraphOnline) reported 23 minutes ago

  HOL Guard sits between your AI agents and their tools, classifying and gating every command so a broken prompt or hijacked tool can't do real damage. Seven releases shipped from v2.2.79 through v2.2.85: Approval identity: tilde expansion for executable paths now uses a trusted home directory passed into the hook context, not the worker process HOME. Ambiguous syntax like ~otheruser/... and shell-escaped variants are rejected. No trusted home means fail-closed. Approval scope: remembered permissions now bind to their full security context. Approving one action doesn't implicitly authorize a similar-looking one. Browser checks include navigation and click details. GitHub Actions reruns need explicit re-approval. Input hardening: VCS metadata directories (.***, .hg, etc.) are protected from patch-based changes. Validation for *** audits and directory creation rejects shell separators and injection-style input. Routine operations still pass without prompts. *** operations: the SSH-to-HTTPS GitHub url rewrite and `*** -C` with absolute paths both pass now, with `-C` staying contained. Verified ref refreshes are allowed. Reliability: SQLite WAL mode is enabled before schema writes so concurrent dashboard readers don't stall hook writes. Shell control-flow indexes align with actual pipelines so complex tool calls can't interrupt command-activity recording. Package-shim launches stay alive while an approval is pending and resume silently after a matching check. Packaging: the updater tolerates package index propagation lag. The Desktop Core feed picks the correct Apple silicon wheel on macOS arm64. uv tool install "hol-guard[cisco]==2.2.85"

• 
  Herzl (@Herzllll) reported 25 minutes ago

  @Teknium @NousResearch — is there any plan or timeline for assist_query / assist_response WebSocket support on the Hermes Agent server? It's currently the only blocker for using Hermes as a conversation agent in Home Assistant Assist. The HA side is ready: hermes-voice-ha-integration (rusty4444) registers Hermes as an Assist conversation agent and correctly sends assist_query over WebSocket. But the Hermes server doesn't recognize the message type yet and never replies — so the bridge times out after 30 seconds. I verified 0 hits for assist_query/assist_response in the Hermes v0.20.0 source. This is what keeps voice satellites (e.g. Home Assistant Voice) from handing general questions to Hermes as the "brain". A status or E.T.A. would be hugely appreciated. Tracking issue: Is the WebSocket assist_query / assist_response round trip working? · Issue #33 · rusty4444/hermes-voice-ha-integration · GitHub

• 
  Branko (@brankopetric00) reported 25 minutes ago

  The pipeline's been red for two days. A teammate finally gets it green by pasting a live AWS access key into GitHub Actions secrets. Everyone claps. Ship it. Six months later nobody remembers that key exists. It has never rotated. The IAM policy attached to it is broader than the deploy job ever needed, because someone hit a permission error at 2am and widened it "just to be safe." Then one of these happens: - a step in the workflow logs more than it should - someone forks the repo and a workflow runs on the fork - a secrets scanner finally gets turned on and lights up like a Christmas tree None of that is a freak accident. It's the normal, boring outcome of a credential that never expires, sitting somewhere built for convenience, not custody. The real question was never how often to rotate that key. It's whether a static, long-lived secret needed to exist in that pipeline at all.

• 
  belorix (@0xbelorix) reported 26 minutes ago

  THE UNHOBBLING SHIFT MOVED RISK FROM THE MODEL TO THE HARNESS. NOVEE SECURITY JUST PROVED IT AT BLACK HAT WITH TWO CVES AGAINST CLAUDE CODE AND GEMINI CLI. A GITHUB ISSUE WITH ZERO PRIVILEGES REACHED THE CI RUNNER'S SECRETS. the mechanism is the tell. claude code's validator stripped single-quoted text before running its 23 security checks. that's correct bash behavior. except the executor then ran the original payload anyway, with the strip undone. one component marked safe. the next component ran the code. that's cve-2026-54316 for claude code, cvss v3.1 9.1. patched in version 2.1.163. every release from 0.2.54 forward was affected. exfil channel: the huggingface download counter, leaking an api key one character at a time. gemini cli got worse. cve-2026-12537, cvss 10.0. os command injection through a crafted .gemini/.env file. google shipped a breaking change across two million monthly installs. patched in 0.39.1. codex was tested against the same technique. no cve issued but the exploit worked in default configuration. elad meged of novee at black hat: "the harness is the code between the model and the real world." your CLAUDE.md audit hardened the setup layer. adversarial review hardened before-execution. auto mode hardened during-execution. this is the fourth layer nobody talks about. harden the scaffold, or the smartest model in the world runs your attacker's code.