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:

• 
  BixKu (@BixKuAF) reported 4 minutes ago

  @thsottiaux I don’t know if it’s an isolated issue to me, but often codex defaults to using gh instead of the connectors, and I end up wasting tokens explaining it should use the GitHub connector. This is for when I ask it to create issues or prs or similars.

• 
  Moses Rivera (@MosesRivera100) reported 5 minutes ago

  I’ve published a free, open-source GitHub repository that shows you how to easily connect your Custom GPT to your Zotero library—without writing code or setting up an MCP server. In about 10–15 minutes, you can create a GPT that can: 📚 Search your Zotero library 🔎 Retrieve your articles, books, notes, tags, and collections 🔒 Access your library through a read-only configuration My instructions require no knowledge of code, and you can just copy+paste what I've provided. Explore the repository here: mosesrivera100/2026-Template-to-create-Custom-GPT-connected-to-your-Zotero-library

• 
  Tiresias (@iamTiresias) reported 5 minutes ago

  @DivyanshT91162 OpenCode being model-agnostic instead of tied to one provider is the meaningful part. Most coding assistants lock you into whatever model the vendor prefers, which becomes a problem when a specific model handles your language or codebase better than the default. The "/opencode" GitHub integration for opening PRs from comments is a real workflow shift. Automating the trigger from issue to draft PR removes the friction that usually kills these integrations - most teams have every intention of using AI in their code review pipeline but never actually set up the automation. The rest is standard cross-platform, terminal-first packaging. Solid tool for developers already committed to AI-assisted coding workflows.

• 
  Pandelis (@PandelisZ) reported 6 minutes ago

  @jaredpalmer @github @DevinAI *** flow is fundamentally broken patchwork like stacked prs are just bandaids

• 
  Gro-Tsen (@gro_tsen) reported 8 minutes ago

  The way the SSH protocol works is that if the server is unhappy with a client authentication method inquiry, it should reject it with SSH_MSG_USERAUTH_FAILURE so the client can try the next one. Here, GitHub sends SSH_MSG_DISCONNECT merely because my client “knows” an old key! 🖕

• 
  katoshi (@bitcoinkatia) reported 8 minutes ago

  @miketwenty1 Many put an enormous amount of trust in CC. In CC’s GitHub repo, the vast majority of commits is authored by one person. The external review that happened was apparently not enough. CC knew about the vulnerability and decided not to fix. Reasons to trust this company again?

• 
  Mevari Navalo (@MevariNavalo) reported 11 minutes ago

  @CryptoCyberia Everyone is missing that the url says that this issue is on the github page for the twitter algorithm. That's not something that is packaged as a .exe that you just run on your desktop. The person asking for the .exe is an idiot here.

• 
  Duncan Rogoff (@DuncanRogoff) reported 13 minutes ago

  "passionate about helping businesses grow" is why nobody follows you. that line, or something exactly like it, is in half the bios i read. so i built a free Claude Code skill that refuses to write it. it's called bio-writer. you type /bio-writer and it writes your profile bio for every platform at the right length, built from what you actually do and one real thing you've done. what comes back: - Instagram bio at 150 characters, 3 lines maximum, no hashtags, no emoji - LinkedIn headline at 220 characters, plus a full About section of 4 to 6 short paragraphs - X bio at 160 characters, no links, no hashtags - a one-liner under 15 words for your link-in-bio or email signature - character counts stated next to each one, all saved to ~/brand/bio.md the part that makes it different from asking a chatbot for a bio: it checks your angle before it writes anything. if what you do could describe fifty other people in your niche, or your audience is "everyone", it stops and tells you the bio isn't the problem, the angle is. a well-written bio for a mushy angle is still a bad bio. it also won't fake your proof. never invent a number, a client count, or a revenue figure. if you're early and have no results yet, it uses your current build instead, "building X in public", which is honest and still works. so you stop rewriting the same vague sentence five different ways across five platforms, and the right person knows in two seconds whether to stay. setup is one line: copy the bio-writer folder into your Claude Code skills directory, restart, type /bio-writer. run /personalize once first so it knows your niche, offer, and audience. free, and it's yours. a bio has two seconds to do one job. this one actually does it. 👉 github repo in the replies

• 
  Sebastian Kehle (@sebastiankehle) reported 16 minutes ago

  coding agents produce an ordered chain of small dependent changes, and github never had a shape for that. you either flattened the chain into one giant PR or kept rebasing branches by hand. my loop is one issue, one worktree, one agent, every slice independent. stacked PRs give dependent agent work a reviewable form: thin layers in order, one click to land the whole thing.

• 
  Anton (@nantons89) reported 18 minutes ago

  @PonyLLM People only bought this token for one reason—it was listed in @JohannKerbrat's GitHub What still doesn't make sense is how the scammer who created the token managed to get it added there And if the GitHub itself was compromised, creating a new token won't solve the problem either

• 
  TheoryOfNearlyEverything (@OverThePlaces) reported 21 minutes ago

  @martinez0x69 @Lean you cant, i wrote a book on amazon, did publishing on @zenodo, but they killed all my stuff, you can mainly find my papers her on x, these are googlespace links & i have 2 repositories on github, if you have problems to get my papers let me know, some people send me asking links

• 
  Med (@medhansh) reported 24 minutes ago

  How to make every Mac, server & cloud worker you own feel like one computer: ====== NETWORKING ====== - Tailscale: Connects all your machines into one private network. SSH into your home desktop from anywhere with no port forwarding and nothing exposed publicly - Thunderbolt Bridge: Connects two nearby Macs directly through a Thunderbolt cable. You get tens of Gbps and sub-ms latency without buying networking gear - 2.5/10GbE: The wired alternative when Thunderbolt isn’t practical. Use it when normal gigabit networking becomes the bottleneck - Cloudflare Tunnel: Gives a local service a public URL without opening a port on your router. Useful for websites, APIs and dashboards other people need to reach - ngrok: Creates a temporary public URL in seconds. Perfect for testing webhooks against something running locally ====== REMOTE ACCESS ====== - SSH + `~/.ssh/config`: Lets you create short names and reusable settings for remote machines. Type `ssh studio` instead of remembering usernames, IP addresses and ports - `ControlMaster auto`: Keeps one SSH connection open and reuses it. New terminals connect instantly instead of negotiating a fresh session every time - Mosh: SSH that survives your Wi-Fi dropping. Close the laptop, open it on a train, switch networks and the same terminal session reconnects - tmux: Keeps programs running after you disconnect. Start a long agent job, close your laptop and reconnect to it later - tmux-resurrect + continuum: Saves and restores your tmux sessions after the machine itself reboots - VS Code / Cursor Remote SSH: The editor runs on your laptop while the code, terminal and language server run on the remote machine. It feels local without syncing files - code-server: Runs VS Code inside a browser. Useful when you need to work from an iPad or a computer without your development setup - macOS Screen Sharing: Built-in remote control between Macs. On the same network it’s fast enough for normal desktop work - Sunshine + Moonlight: Streams a remote desktop using game-streaming technology. Use it when you need much lower latency than normal screen sharing ====== SERVING ====== - Tailscale Serve: Gives a local service a private HTTPS URL that only devices on your Tailscale network can open - Tailscale Funnel: Takes that private service and makes it reachable from the public internet. Useful for receiving webhooks on a home machine - Caddy: A web server and reverse proxy that gets HTTPS certificates automatically. Two lines of config, real certificates, no Let’s Encrypt homework - Cloudflare Tunnel: Better when you want public traffic to pass through Cloudflare before reaching your machine ====== FILES ====== - ***: Tracks changes, understands conflicts and lets each agent work on a separate branch. Use *** for code that agents edit, not a generic sync tool - *** worktrees: Opens multiple branches from the same repository as separate folders. Every agent gets its own workspace without cloning the repo again - Jujutsu (`jj`): A ***-compatible version-control system designed around easier rebasing, undoing and concurrent work. Worth trying when many agents produce branches at once - SMB: Shares a folder from one machine so another can mount it like a local drive. The easiest answer for two Macs on the same network - NFS: The same basic idea as SMB, with more setup and generally better performance - Mutagen: Continuously mirrors a local project to a remote machine while respecting ignored files. Use it when you want to edit locally but run remotely - Syncthing: Automatically syncs folders directly between machines. Great for notes, assets and scratch files - Don’t use Syncthing for code multiple agents edit. It syncs files but doesn’t understand branches or conflicts - rsync: Copies files or folders once, usually over SSH. Fast, scriptable and already installed almost everywhere - rclone: rsync for cloud storage. Moves files between your machines and S3, R2, B2, Google Drive and dozens of other services - pnpm: Stores each package once and hardlinks it into every project. Fourteen worktrees can share one copy instead of downloading fourteen ====== ENVIRONMENT ====== - mise: Installs and switches Node, Python, Go and Ruby versions per project. Replaces nvm, pyenv, rbenv and asdf with one fast tool - direnv: Loads the correct environment variables the moment you enter a folder, then unloads them when you leave - OrbStack: A drop-in Docker Desktop replacement for Mac. The same Docker commands with a fraction of the RAM and battery usage - Homebrew + Brewfile: Records the apps and CLI tools installed on your Mac. A new machine can recreate the setup with one command - Devcontainers: Defines the development environment in code. Anyone opening the project gets the same operating system packages, runtimes and tools - Nix / devenv: Reproduces an environment extremely precisely across machines. Powerful, but only worth the learning curve when that level of determinism matters ====== SECRETS ====== - 1Password CLI: Injects secrets into a command at runtime. Your `.env` becomes a template you can safely commit because the real values stay in 1Password - `op run`: Starts a command with the required secrets available only to that process. Nothing sensitive needs to be copied into plaintext files - 1Password Service Accounts: Give headless servers access to specific vaults without attaching them to your personal login - SOPS + age: Encrypts secret files before they enter ***. The repository stores ciphertext and approved machines decrypt it at runtime - Tailscale SSH: Uses your Tailscale identity to authorize SSH access. You stop copying and rotating public keys across every machine ====== TERMINAL ====== - Atuin: Your shell history, synced and searchable across every machine. That command from last Tuesday on the server is available on your laptop - zoxide: Learns which folders you use. Type `z api` instead of `cd ../../../services/api` - fzf: Adds fuzzy search to almost anything. Use it for files, command history, *** branches, processes and SSH hosts - ripgrep (`rg`): Searches an entire codebase in milliseconds and skips files in `.gitignore` automatically - fd: `find` with syntax you can actually remember. Type `fd config` instead of assembling a collection of flags - bat: `cat` with syntax highlighting, line numbers and *** changes - dust: Shows which folders are consuming disk space as a readable chart instead of a wall of numbers - lazygit: A full *** interface inside the terminal. Stage individual lines, inspect diffs, rebase, cherry-pick and resolve conflicts visually - btop: A readable live view of CPU, memory, disks, networks and running processes ====== CONSISTENCY ====== - just: One file containing every project command. `just dev` means the same thing on every machine and every teammate’s laptop - chezmoi: Keeps your dotfiles in *** and adapts them per machine. You get the same shell, aliases and settings across macOS and Linux - Brewfile + mise + chezmoi + just: Together these recreate your installed tools, runtime versions, personal configuration and project commands ====== ISOLATION ====== - Containers: Give each workload its own filesystem, dependencies and permissions. One broken agent can’t interfere with everything else on the machine - One container per client: An agent cannot read another client’s files if those files were never mounted into its container - Colima: A free, CLI-only way to run Docker containers on Mac - Podman: Runs containers without a permanent root-level daemon. Useful when stronger rootless isolation matters - ****: Creates and manages macOS and Linux virtual machines on Apple Silicon - UTM / Parallels: Full desktop virtual machines for workloads that need a complete graphical operating system - Firecracker: Starts tiny virtual machines in under a second. Useful when you’re building a platform that needs an isolated machine for every agent run ====== AGENT ORCHESTRATION ====== - tmux + *** worktrees: The simplest fleet manager. Every agent gets a terminal, branch and folder you can inspect directly - Claude Code hooks: Run commands automatically before or after specific Claude Code events. Useful for validation, formatting, notifications and cleanup - Claude Code subagents: Hand focused tasks to separate agents without manually opening another terminal for each one - Claude Agent SDK: Starts, steers and streams agent sessions from your own code. Use it when a terminal workflow needs to become part of a product - Inngest / Trigger .dev: Turns agent runs into durable jobs. If a process crashes, the job can retry instead of disappearing with the terminal - BullMQ / Graphile Worker: Adds a straightforward job queue backed by Redis or Postgres - launchd: Starts Mac workers after reboot and restarts them when they crash - systemd: The Linux equivalent of launchd - Temporal: Stores every step of a long workflow so it can resume after failures. Powerful, but unnecessary until durable execution becomes a real problem ====== RENTED COMPUTE ====== - Hetzner dedicated: Cheap, persistent Linux machines with lots of CPU and RAM. Good for workers that run all day - Hetzner Server Auction: Older dedicated servers sold for less. Useful when price matters more than having current hardware - DigitalOcean / Vultr / Linode: More expensive per GB, but nearby regions can make interactive SSH and remote editing feel much faster - Fly .io: Small machines that start quickly and can shut down when idle. Good for temporary workers - GitHub Actions self-hosted runners: Sends CI and batch jobs to hardware you already own instead of GitHub’s machines - Depot: Runs builds remotely and shares the cache between machines. Useful when Docker or application builds become the bottleneck - Modal / RunPod / Lambda: Rent GPUs by the hour instead of owning hardware that sits idle - MacStadium / Scaleway Apple Silicon: Rent real Macs remotely. Only worth it when the workload genuinely requires macOS ====== BROWSER AUTOMATION ====== - Playwright + `storageState`: Saves cookies and login state to a file that can move between machines. Much safer and more portable than syncing an entire Chrome profile - Puppeteer: A smaller Chrome-focused alternative when you don’t need Playwright’s multi-browser support - Chrome DevTools MCP: Lets an agent inspect and control a real Chrome session through developer tools - browser-use: Gives agents a higher-level way to navigate websites, fill forms and complete browser tasks - Browserbase / Browserless / Steel: Hosts and manages browsers for you. Useful when one local Chrome instance becomes fifty concurrent sessions - Residential proxies: Routes browser traffic through consumer IP addresses. Use them when websites block traffic from cloud servers ====== SAFETY ====== - restic + Backblaze B2: Encrypted, deduplicated, automatic offsite backups for roughly $6/TB/month. You’ll need it exactly once - Time Machine: Keeps local versions of your Mac files and makes accidental deletion easy to undo. Necessary, but not enough by itself - Carbon Copy Cloner / SuperDuper: Creates a bootable copy of your drive so a dead SSD doesn’t mean rebuilding the machine from zero - Netdata: One command installs a full metrics dashboard. Finally see which process has been eating your RAM - `memory_pressure`: Shows whether your Mac is actually running out of usable memory - `vm_stat`: Shows detailed memory usage and paging activity - `sysctl vm.swapusage`: Shows exactly how much SSD space macOS is using as emergency memory - asitop: Shows Apple Silicon CPU clusters, GPU usage, power consumption and temperatures - Uptime Kuma: Checks whether your machines and services are online and sends an alert when they aren’t - Grafana + Prometheus: Stores metrics over time and turns them into dashboards and alerts. Worth adding once you have several machines A backup isn’t real because the command succeeded It’s real when you’ve restored from it successfully ====== THE 80/20 STACK ====== Tailscale SSH + Mosh + tmux *** worktrees SMB 1Password CLI mise + direnv OrbStack pnpm just + chezmoi restic + B2 Netdata Atuin + zoxide + fzf Start here Add another tool only when you can clearly explain what problem it solves

• 
  Nazar (@Nazik2053) reported 25 minutes ago

  Someone open-sourced a tool that runs a 744B model on a machine with 25GB of RAM. Colibri streams the experts of GLM-5.2 (744B MoE) straight off your NVMe SSD, keeps the dense layers in memory, and only pulls the few experts each token actually needs. Pure C, plus a live atlas of all 21,504 experts. The catch: it's slow - think ~1 token/sec on strong consumer hardware. Not a Claude replacement. But "you need a datacenter for frontier models" just stopped being strictly true. Free on GitHub, full walkthrough below.

• 
  Tzard Nickolas The Lit Romanov (@TheGreatRomanov) reported 26 minutes ago

  @skavenslave I'd also add Discord ontop of that too here. *WAY* too many authors/devs require users to download the mod (or whatever Said X thing here is) from their gay little invite-only servers as the only source to obtain it (or will use the server to link, to GitHub).

• 
  Gaston Levai (@gastonelevai) reported 27 minutes ago

  @GRAZZLEYNFT @PumpfunEco After also the community address the issue with the OG dev he finally redirected the fees to the GitHub of @PrJulienMartin .