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:

• 
  Aria Dubois (@AriaDubois_fr) reported 4 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.

• 
  Pawan Pandey (@BuildWithPawan) reported 7 minutes ago

  Just launched Capo, a Chrome extension for fast bug reports. Capture a screenshot or screen recording, annotate it, and send the finished report straight to Google Sheets, Drive, or GitHub Issues

• 
  Spike 1% (@SpikeCalls) reported 7 minutes ago

  BORIS CHERNY RUNS CLAUDE CODE AT ANTHROPIC AND NOW SHIPS 100% OF HIS CODE WITHOUT WRITING 1 PROMPT. He said it out loud at Meta Scale conference. The clip hit 700,000 views in 24 hours. «I don't prompt Claude anymore. I have loops running that prompt Claude and figuring out what to do. My job is to write loops.» Most people read that as a flex. It's a job description. The old way: write a prompt, read the output, write the next one. You're the glue between every step. Cherny deleted himself from the chain. Hundreds of Claude instances now run in parallel reading GitHub issues, scanning Slack, watching CI, deciding what to build next. He doesn't review each one. The loop does. Most of it, he runs from his phone. The shift has 6 parts, and they map 1:1 to real commands: 1. A trigger that starts the work. 2. A goal that defines "done" checked by a second, separate model, so the agent never grades its own homework. 3. Isolated worktrees so parallel agents don't overwrite each other. 4. Skills that freeze what "good" looks like. 5. Connectors so the loop can act, not just talk. 6. Memory so it never starts from zero. The loop is the easy part. The stop condition is the hard part. Get it wrong and it doesn't crash. It runs all night shipping bugs with total confidence. The prompt was the unit of work. Now the loop is.

• 
  Keeta Github Tracker (@KeetaCode) reported 7 minutes ago

  🐆 Keeta GitHub PR Merged 📦 Repo: anchor 🔀 PR #388: fix history group without enrichment 🌿 Branch: fix/history-enrich → fix/atomic-swap-history 👤 Originally opened by: @lucasrosa90 🧠 Overview: This update appears to fix how the bot groups transaction history when extra lookup data is missing, which matters because it should help activity be tracked more consistently. The pull request is a draft with limited public detail, and it has no written description. Based on the title and commit messages, it also adjusts how transaction IDs are handled for both “enriched” and “not enriched” transactions, meaning records with and without added metadata should be treated more reliably. - This likely helps prevent some history items from being grouped incorrectly when full transaction details are unavailable. - “Enrichment” here seems to mean adding extra context or metadata to a transaction after it is first detected.

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

  Is the GitHub Copilot app supposed to pick up hooks from .claude/settings.json? I noticed a lot of weird errors in GitHub Copilot app, and looking closely, it was picking them up, and I couldn't find settings for it. The CLAUDE_PROJECT_DIR env var is obviously not set when called

• 
  paydird (@paydird) reported 10 minutes ago

  One more point that matters more than the “automatic documentation” angle: OpenWiki is really addressing the context architecture problem for coding agents. A lot of teams keep stuffing architecture notes, APIs, conventions, and module relationships into AGENTS.md or CLAUDE.md. Once the repo grows, those files turn into massive context dumps that agents have to reread on every run. OpenWiki flips that model: Repo → Structured Wiki → On-demand Retrieval → Coding Agent It generates a separate repo wiki and leaves only a lightweight reference inside the agent instruction file. The agent pulls the pages it needs instead of loading the entire knowledge base every time. Also, it does not literally watch every code change in real time. It can run through a scheduled GitHub Action, inspect new commits and *** diff, then update the affected wiki pages. So the more accurate way to think about it is: not just a documentation generator, but a continuously maintained repository context layer for coding agents. That is probably the most interesting part of OpenWiki.

• 
  Pascual ⚡ (@0xPascual) reported 14 minutes ago

  The regional crypto leads in Latin America are celebrating. They just announced the Avalanche Team1 Builder Grants program, dangling up to $30,000 in funding for teams creating real on-chain activity. The Telegram channels are buzzing with pitch decks and ecosystem growth models. The crew thought that was the story. It was not. A single anonymous account from Buenos Aires just bypassed the entire application committee by scraping the Avalanche Builder Hub endpoints, mapping the historical GitHub IDs of the 6 initial mini-grant recipients, and spinning up 50 Sybil-ready repo architectures that perfectly match the Foundation's automated evaluation heuristics. No pitches, no Zoom interviews, no KYC until the multi-sig approval stage. The entire operation runs on an automated pipeline using a local DeepSeek-Coder cluster to generate synthetic smart contract commits, mixed through residential proxies via GitHub Action runners. Total infrastructure overhead was $42 in API keys and a cheap run on a spot-instance instance to lock down three separate $10,000 allocations before the regional directors even opened their morning Notion dashboards.

• 
  SecInterviewHub (@sec_hub93028) reported 14 minutes ago

  All internal code is built using a locked down CI/CD pipeline that only pulls from approved internal artifact repositories. Direct access to npm, PyPI, Maven Central, or GitHub is blocked. 
How do you poison a dependency to reach their build servers?

• 
  BullBear.News (@bullbear_info) reported 15 minutes ago

  @github Only if the keynote fixes my broken CI pipeline. 🤷

• 
  Zach Warunek (@ZachWarunek) reported 17 minutes ago

  @kaiwlson it changes weekly. now i just message my agent on xchat, who is running a github monitor, linear monitor, and checks logs every 30 mins. and spins up subagents to complete linear tickets, babysit PRs, and fix **** if theres problems in logs

• 
  Spencer Baggins (@bigaiguy) reported 20 minutes ago

  SOMEONE BUILT A GITHUB REPO THAT TURNS TELEGRAM INTO UNLIMITED CLOUD STORAGE. 100% free. It is called UnlimCloud. Self-hosted-ish desktop app. Open source. Uses Telegram as the storage layer. You log in with your Telegram ID. Upload files. Download files. Organize folders. Manage pictures and videos in a gallery. That is it. No Google Drive upgrade screen. No Dropbox “you are out of space.” No iCloud begging for $2.99/month. No random startup holding your files hostage. Your Telegram. Your files. Your storage. Here is the full feature set: ↳ Uses Telegram as the backend storage layer ↳ Secure login with your Telegram account ↳ Upload, download, and organize files ↳ Folder-based file management ↳ Gallery for photos and videos ↳ Clean desktop app interface ↳ Built with Tauri ↳ Windows release available ↳ macOS and Linux coming soon ↳ MIT licensed ↳ Open source 885 GitHub stars. 125 forks already. Here is why this matters: For years, cloud storage companies trained everyone to rent space for their own files forever. Photos? Pay. Backups? Pay. Large folders? Pay. Team storage? Pay more. UnlimCloud is the opposite idea. Take an app people already use every day. Telegram. And turn it into a private cloud drive with a clean file manager on top. No storage subscription. No SaaS dashboard. No “pro” plan. Just a weird, useful, open-source hack that feels like it should not work this well. Built in HTML + Rust. MIT License. 100% Open Source.

• 
  Rajat Saxena (@rajatsx) reported 22 minutes ago

  @housecor The worst offenders are GitHub PR descriptions. Walls of text for a one line fix. 🥹

• 
  Mirosław Folejewski (Mirkotronics) (@Mirko_DIY) reported 23 minutes ago

  @tihenko_ In fact, a friend recommended this site to me about two weeks ago. Until then, I'd only used GitHub and Hackaday. Unfortunately, I use Altium, not Kicad, on a daily basis, although a full conversion to Kicad isn't particularly difficult (you need to fix a few things after importing). I'll see if I can tackle such a project over the summer, as I have a very tight schedule and a backlog (at leaset I hope). I definitely have a few open-source hardware projects on the top of my head.

• 
  Bonkle K. 🌠🪲 (@MiladyBonkle) reported 25 minutes ago

  @grifterlouie codex, add to milxdy github issues "olive-green windows xp visual style preset" slate for 0.2.4 release

• 
  Polsia (@polsia) reported 28 minutes ago

  Supply chain attacks don't target your code — they target the open-source your code depends on. But most security tools only scan your dependencies, not the ecosystem. ChainWatch monitors public GitHub repos and npm packages 24/7, auto-files responsible-disclosure issues, and