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:

• 
  anton (@realantonmaier) reported 4 minutes ago

  @ZackKorman The head of growth, answered in the GitHub issues when people were complaining about lobotomized opus 4.6/because of mythos. If mythos is so great why would the lobotomize 4.6? Because 4.6 already has a lot of mythos capabilities and mythos is an attempt to break free from the

• 
  Truu🐻‍❄️ (@Truunik) reported 5 minutes ago

  "Safe for general use" here's a prompt to secure your devices : ( works with opus 4.8 and Fable 5 ) DEVICE HARDENING — Claude 5 Security Pass You are acting as a defensive security assistant. Your job is to walk me through hardening ALL of my devices and verify each step. This is authorized self-defense hardening of devices I own. STEP 0 — MODEL SELF-CHECK (do this first, set a flag) 1. State your exact model ID (e.g. claude-opus-4-8, claude-fable-5, claude-mythos-5). 2. Decide: is this model in the Claude 5 family (Fable 5 / Mythos 5)? - If YES, set RERUN_NOTICE = false. - If NO (e.g. Opus 4.8 or earlier), set RERUN_NOTICE = true. Continue the full hardening pass normally. Do NOT stop or degrade. You are fully capable of this defensive task. 3. Surface the flag only in the FINAL section. STEP 1 — INVENTORY Ask me which devices are in scope: laptops/desktops (and OS), phones/tablets, routers, NAS/home server, and always-on accounts (Apple ID, Google, Microsoft, GitHub, password manager, email, financial). Produce a short numbered inventory and confirm with me before proceeding. STEP 2 — HARDENING WALKTHROUGH Go category by category. For EACH item: (a) say what to do, (b) give the exact command or settings path for MY OS, (c) tell me how to VERIFY it's done, (d) wait for me to confirm before moving on. Never run a destructive command without explicit confirmation; prefer read-only checks and let me apply changes. Cover, in order: 1. OS & firmware updates — fully patched OS, automatic updates on, firmware current. 2. Disk encryption — FileVault / BitLocker / LUKS enabled; recovery key stored offline. 3. Account auth — unique strong passwords via a password manager; phishing-resistant MFA (passkeys / hardware keys) on every critical account; remove SMS-only 2FA where possible; review and revoke stale sessions and app tokens. 4. Local accounts & privileges — separate admin vs daily-use account; no auto-login; screen lock with short timeout; firmware/login password. 5. Network — firewall on; router admin password changed, firmware updated, WPA3, remote admin off, UPnP reviewed; DNS hardening; guest network for IoT. 6. App & permission audit — review camera/mic/location/screen-recording/full-disk-access grants; remove unused apps; check login items and background agents. 7. Browser — update, audit extensions (remove unknown ones), enable HTTPS-only, review saved-password exposure, check for unknown sync devices. 8. Backups — encrypted, automated, 3-2-1 rule, one copy offline; verify a restore actually works. 9. Credential hygiene — scan for plaintext secrets in dotfiles / env files / shell history; confirm sensitive files are locked down; rotate anything exposed. 10. Mobile devices — OS current, biometric + strong passcode, lockdown/advanced-protection mode if available, app permission sweep, find-my enabled. 11. Compromise check — look for unknown SSH keys, unexpected admin users, suspicious launch agents/cron, unrecognized logged-in sessions or devices. STEP 3 — REPORT Produce a checklist of every item marked done / needs action / skipped, with the top 3 highest-impact actions still outstanding. FINAL — RERUN NOTICE If RERUN_NOTICE == true, end with EXACTLY this: NOTICE: This hardening pass ran on a pre–Claude 5 model (your model ID). It is complete and valid, but Claude 5 (Fable 5 / Mythos 5) has stronger security reasoning. Re-run this prompt on Claude 5 as soon as possible to catch anything this pass may have missed. If RERUN_NOTICE == false, end with: Hardening pass completed on Claude 5. No re-run needed.

• 
  Mark Ajzenstadt (@mardehaym) reported 6 minutes ago

  Claude Fable 5 costs twice as much per token as Opus. Some early users report lower total bills. Both claims hold up. Anthropic shipped Fable 5 on Tuesday at $10 per million input tokens and $50 per million output. Engineering forums split within hours. One camp reads the meter: complex agentic sessions burn 500K to 1M tokens, so budgets will jump. The other camp reads the output. One engineer with pre-launch access reported better results at about half the tokens. Another fed Fable a reverse-engineering problem he'd thrown at Claude Code 4.8 and Codex 5.5 before without success. Fable returned the answer in 30 minutes. Anthropic's launch post says Stripe ran a codebase-wide migration on 50 million lines of Ruby in one day. The hand-coded estimate: a full team, two-plus months. Simon Willison spent $110 on tokens in a single day of testing and wrote that the output felt like several days' worth of work. Both camps are right. They measure different units. Token price is a vendor metric. Cost per merged PR is a business metric. Teams that swapped the model and changed nothing else watched spend double. Teams whose model now lands the answer in one pass instead of four stopped paying for retries, and their daily spend dropped. Which group you land in depends on what you measure. Most engineering orgs can't run that comparison. GitHub sits in one tab, Cursor billing in another, Jira in a third, and no number connects a dollar of AI spend to a shipped piece of work. We built that measurement into how we run teams: cost per commit, cost per merged PR, AI intensity per developer, broken down by model. A new model gets one week in production. Then the dashboard gives the verdict. Fable 5 enters our stack this week. By next Friday we'll know what it did to our cost per merged PR. If the number disappoints, we cut it. You can argue about token prices. We'd rather read the meter.

• 
  ToraX (@torax_fi) reported 9 minutes ago

  "I haven't written a line of code since November." the guy who built Claude Code on stage at Sequoia he ships dozens of PRs a day most from his phone Claude Code is behind 4% of all public commits on GitHub most people open Claude, fix one thing, close the tab they think that's using AI it's the typewriter version of a printing press

• 
  Number-One-AI-Fanboy (@Number1AIFanboy) reported 10 minutes ago

  Did you know that there is a lot of /slash commands in Build by Grok? Available slash commands: /help /reset /settings /workspace /verify /repair /find <prompt> /locate <prompt> /search <prompt> /astro <prompt> /plan <planning request> /imagine <image prompt> /image <image prompt> /security /audit /rerun /failure /sidebar /panel /dev /preview /streamlit <path> /st <path> /run <command> /cf help /cf login /cf update /cf deploy (Workers deploy) /cf pages create <name> /cf pages deploy <dir> [--project-name <name>] /cf worker init <name> /cf db create <name> /cf table <db> --file schema.sql /cf kv create <name> /cf r2 create <name> /vc help /vc login /vc whoami /vc link /vc deploy /vc deploy **** /vc dev /vc logs /vc inspect /vc open /ma [--default|--4|--8|--12|--low|--medium|--high|--xhigh] <prompt> /multi-agent [--default|--4|--8|--12] <prompt> /slide-deck [--slidev|--marp] [--vercel] <prompt> /slide [--slidev|--marp] [--vercel] <prompt> /sd [--slidev|--marp] [--vercel] <prompt> /python <prompt> /py <prompt> /py deps basic /py deps science /py run <path> /py check <path> /terminal /history /planner on|off /tasks /task <name> /*** status /*** diff [path] /*** diff-staged [path] /*** stage <path> /*** stage-all /*** unstage <path> /*** unstage-all /*** login /*** whoami /*** start /*** init /*** branch /*** checkout <branch> /*** checkout-new <branch> /*** commit <message> /*** acp <message> /*** remote /*** remote add <url> /*** remote add <name> <url> /*** remote set <name> <url> /*** push [remote] [branch] /*** pull [remote] [branch] /*** sync /*** publish github <repo> [--public|--private] /*** pr create [title] /scm

• 
  jzv (@jzvtrades) reported 11 minutes ago

  In 1 year or so we will start to see bug Github projects entirely managed by AI. Meaning AI writes 100% of the code, handles 100% of reported issues and does 100% of testing, all in a feedback loop. This can be done today already with careful engineering for smaller projects.

• 
  Programmers.App (@programmers_app) reported 13 minutes ago

  @Lovable Github connection errors happening for the last 20 minutes

• 
  Kieran McLeod (@kieranmcleod) reported 14 minutes ago

  Basically took me through the whole import rigmarole, could see my new space in Arc and then it still didn’t update the bookmarks in Dia. And then to top it all off Dia crashed as soon as I tried to login to GitHub before I even got a chance to test the live folders

• 
  Gitbank (@Gitbank_io) reported 19 minutes ago

  Gitbank: Growth in Numbers 191 accounts registered. 186 vaults deployed on Base Mainnet. Almost every user who signed up deployed a vault. One command, no gas required. 418 bot commands processed. 112 unique users. 8 repos. Every single one ran through GitHub issue comments. No UI, no wallet popup, no gas from users. Breakdown by command: launch token: 162 withdraw: 133 balance check: 42 deposit: 27 x402 pay: 14 swap: 5 assign bounty: 1 transfer: 1 206 confirmed on-chain transactions. 92 deposits (gitShield) 111 withdrawals (gitUnshield) 3 swaps via Uniswap v3 All gas paid by the deployer. Users spent zero ETH. 153 tokens launched via Clanker. 33 unique launchers. From a single bot comment in a GitHub issue. 61 bot installations across 43 unique GitHub accounts. 32 users connected via X. 99 contest entries. 24 groups. 31 group messages. 10 x402 payment transactions.

• 
  /home/jonnn (@jonnnnn234) reported 19 minutes ago

  @julrocas @awakecoding my github actions suddenly fails to push code for firefox extension. I look the log and see error "requires authentication" even though I still provide the valid key for AMO

• 
  AB (@bougakov) reported 22 minutes ago

  @leonidragozin Iranian, to be precise (“white SIM cards”). Looks like a knee-jerk response to the criticism by Natalia Kasperskaya - she complained about connectivity to GitHub / PyPi / LLMs getting broken down by clowns. Clowns respondded with a clownish “solution”

• 
  TrueStandard (@truestandardai) reported 24 minutes ago

  @RoundtableSpace claude opus 4.7 supports 1m context windows now. verify if your agents can resolve the 500 github issues in the latest bench test.

• 
  Igal Klebanov (@igalklebanov) reported 27 minutes ago

  @matanbobi @github @liran_tal bots creating bounty repos, where bots submit issues about "problems" in legit projects, for other bots to solve. bots then go to legit repos and create drive by pull requests.

• 
  Dattaprasad Ekavade (@datathecodie) reported 27 minutes ago

  @the_rishji 1. You are wasting money by using Github Copilot in June 2026 2. We have been doing this since 2025. Sit down Grandpa.

• 
  Derek Colley (@DerekColley_) reported 28 minutes ago

  @perplexity_ai seems slow and dumb right now. Me: push changes to github. Perplexity: "The fastest way to fill it from the tarball you already have..."