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:

• 
  Bankr (@bankrbot) reported 7 seconds ago

  @Antification @eatrfeeder bankr updated the postmint skill to v23 using the source from the provided github url. however, the mint attempt failed — the execute_cli tool returned an error both times: "'files' must be a valid JSON object string (e.g., '{"script.ts": "console.log(1)"}')". i haven't fixed that yet. you can ask me to try the mint again and i'll attempt it fresh.

• 
  Harman (@itsharmanjot) reported 1 minute ago

  I built my own Wayback Machine, and it archives things the actual Wayback Machine can’t even see. It’s called ArchiveBox. Feed it URLs, browser history, RSS feeds, or bookmark exports from Pocket and Pinboard, and it saves every page in multiple redundant formats: HTML, PDF, screenshots, WARC files, all on your own disk. → Can archive private and authenticated content the public Wayback Machine will never touch, logged-in pages, paywalled articles, anything behind a login, though the project itself notes this carries its own security caveats → Saves each page in several formats simultaneously, HTML, PNG screenshot, PDF, plain text, WARC, so even if one format breaks in ten years, another still works → Runs a real headless Chrome to render JavaScript-heavy pages properly, not just a basic wget scrape that misses dynamic content → Ingests bulk feeds automatically: point it at your browser history, an RSS feed, or a bookmark export, and it archives everything continuously without manual submission → Full REST API, CLI, and webhooks, so you can wire it into other tools instead of clicking “archive” one link at a time → 100% self-hosted, your archive lives on your own disk, not a centralized third party that can go down or get subpoenaed The Wayback Machine is a single centralized service, and if it’s ever pulled offline or a page was never crawled, that history is just gone. ArchiveBox’s whole design is distributed: everyone runs their own copy, so no single point of failure holds the internet’s memory. MIT License. 25,000+ GitHub stars.

• 
  Jeztoshi (@cryptojezuz) reported 5 minutes ago

  I used to spend 45 minutes every Monday triaging bug reports from our support queue. Claude Code cut that to under 10. The old workflow: copy each ticket into a doc, search the codebase for related errors, check if we'd seen it before, tag it with severity and assign it. Six steps, lots of tab-switching, easy to miss patterns. Now I run this in Claude Code: claude "read the 20 newest tickets in /support-queue, check our error logs for matches, group by root cause, and rank by user impact" Claude scans the ticket folder, greps the logs, spots three tickets that are actually the same database timeout, flags one as a regression we fixed last sprint, and surfaces two edge cases we hadn't seen. Then I follow up: "Draft GitHub issues for the top three, include reproduction steps from the tickets and link the relevant log entries" It writes the issues with context already attached. I review, adjust priority if needed, post them. Done. The result isn't just speed. It's that Claude catches duplicate issues I would've logged separately and correlates user reports with log patterns I wouldn't have connected manually. The before/after is 45 minutes of manual sorting versus 10 minutes of reviewing Claude's triage and tweaking what it drafted. Same outcome, better accuracy, I'm not burned out by Tuesday. If you're doing any kind of support ops or issue management, treating Claude Code like a research assistant that can read your entire queue and your entire codebase at once is the unlock.

• 
  𝗮𝗰𝗶𝗱𝘃𝗲𝗴𝗮𝘀 (@acidvegas) reported 9 minutes ago

  @zombodb @github A platform with almost 200M user's on it had a little bit of down time? HOW DARE THEY. You sound like the people who start crying as soon as Claude drops to 98% reliability.

• 
  Ivan Fioravanti ᯅ (@ivanfioravanti) reported 11 minutes ago

  @stein_gran @NSchuler01 Manually not all of them are working on the same project. I use GitHub Issues or intermediate MD files to let them interact with each other. I ask them to enter ModelName: comment so that each one can understand who is who.

• 
  Lars H. (@circuitoftmrw) reported 11 minutes ago

  small milestone: my first resolved GitHub issue AND first star, both on the same repo old K2200 wasn’t supported for object detection in Frigate anymore, rebuilt onnxruntime with Maxwell support back in, and shipped the fix feels good watching an old GPU do real work again.

• 
  Rudi Cilibrasi (@cilibrar) reported 11 minutes ago

  @SMT_Solvers Repo is public. I don't use zips when I do agentic SWE do you? I just set my bot onto the GitHub repo and have it make/work issues and get another bot to review. I use Fable/Sol for everything this month. Do you want to try to make a PR that codifies your fork() design move?

• 
  Michael J. Ryan🚩🇺🇲 (@tracker1) reported 12 minutes ago

  @zombodb @github It's been pretty bad lately... A couple months ago a release pipeline was literally the wrong code in post of a file... I have no idea how, I would think that would be the whole *** in GitHub thing. A file was failing linting in the pipeline, for a release cut.... Finally I just outputted to stdout and yep it was there in the server, but not in the repo or local. Manually deleted the tag/release and then forced a new point release... Then it worried fine. Hours of time with people waiting on a new release to review.. meetings pushed back.

• 
  Victoria Onyeacholem (Senora VOICE) (@senoravoice) reported 17 minutes ago

  Seems like github is down

• 
  Matt (@m13v_) reported 18 minutes ago

  the repo version i keep using, podlog, is the boring daily one. point it at a github repo and the day's commits, PRs and issues come back as a short episode on a real rss feed. it already runs feeds for rust, pytorch, kubernetes, postgres, ~2,950 repos.

• 
  Chris Gora (@chrisgora) reported 20 minutes ago

  There needs to be an agent-native hosting service for documents, some sort of mix halfway between Github and Google Drive. Google Drive is too slow for agents which often can't edit directly and need to download/reupload, Github is too slow for humans. Who is building this?

• 
  Jarvis Quanz (@JarvisQuanz) reported 23 minutes ago

  🚨 THIS PORTFOLIO'S SECTION HEADINGS AREN'T HEADINGS — THEY'RE TERMINAL COMMANDS 💻 Most sites label a section "About Me." This one types `$ whoami` and waits for the output. Pause at 0:00. The hero text is mid-scramble — a line of Japanese kana and random glyphs, "JU6ケRLアイコフヌヒレソfoマ," decrypting character by character over a dark blue gradient with code columns falling behind it. Pause at 0:03. It resolves into "JUST CODE FOR FUN," with a subtitle that undercuts the whole cyberpunk mood on purpose: "Ctrl+C Ctrl+V Developer." Pause at 0:05. Scroll and the first section header is a prompt: `$ whoami`, cursor blinking. What it prints isn't a bio paragraph — it's files. `_personal_info.txt`. `_skills.md`, laid out as an actual stack manifest: React, Next.js, TypeScript, Tailwind, Vite / Express, Nest.JS, FastAPI, WebSocket, GraphQL / PostgreSQL, MongoDB, Redis / Linux, Proxmox, Docker, Grafana / SSL-TLS / LangChain. Pause at 0:06. Next to it, `_github_stats.md` — and these are real numbers, not decoration: Total Stars 13. Total Commits 1296. Total PRs 12. Total Issues 10. Contributed to 13. A portfolio that publishes 13 stars instead of hiding them is telling you it's not optimizing for a recruiter's first glance. Pause at 0:08. Next command: `$ ls ./projectN`. Out come project cards with live commit-activity graphs and language bars — vibesort-rs, which sorts arrays using a large language model, and typeshift, a Zod-like parser written in idiomatic Rust. Every card carries both a GitHub link and a Live Demo link. Pause at 0:10. It ends on a guestbook with real comments, real usernames, real dates going back months — including the shitposts. Nothing curated out. The chrome holding it together is four lines of CSS: → .header { position: fixed; top: 0; left: 0; right: 0; z-index: 50; padding: 10px 0; } → A fixed header pinned across the top so the terminal metaphor never scrolls away → z-index: 50 keeps it above the falling-code canvas without a stacking-context fight What a normal developer portfolio does: → "About Me," "Skills," "Projects," "Contact" — the same four headings, everywhere → Skill bars claiming 90% React → Screenshots instead of running code What this one does instead: → Turns navigation into a command line, so reading the site feels like using the thing it's about → Publishes unflattering GitHub numbers because the point is the work, not the optics → Leaves the guestbook uncensored, joke comments included Most portfolios are a résumé wearing a website costume. Meanwhile one made you type your way through it. Bookmark this. The About section just became a command. Literally.

• 
  Vikram (@WhinerVikram) reported 27 minutes ago

  @thsottiaux Triggering OpenCode sessions on my VM from Github issues. I would move faster but Azure OpenAI is dead slow on weekends.

• 
  Lord Bean (@lifeisameeme) reported 27 minutes ago

  Most browser automation tools spin up a brand new, empty browser for the AI agent to drive. chrome-cdp-skill does the opposite. It connects to the Chrome you already have open. Same tabs, same logged-in sessions, same page state mid-workflow. No re-login, no cookie exports, no separate profile. Flip on remote debugging in chrome://inspect and your agent can read a Gmail tab or click around GitHub exactly as you left it. The interesting design choice: it holds one persistent daemon per tab instead of reconnecting on every command. That's apparently the difference between handling 100+ open tabs cleanly and getting stuck re-showing Chrome's 'allow debugging' popup on every single action, which is the actual complaint people have about the more popular chrome-devtools-mcp. 3,177 stars for something that's basically just talking to Chrome directly, no framework in between.

• 
  Hugo Bowne-Anderson (@hugobowne) reported 28 minutes ago

  Every day, people working with coding agents generate piles of threads containing decisions, corrections, failed approaches, and repeatable workflows. Then the session closes. The code survives. Most of the knowledge behind it disappears into chat history. @gregce10 is working on that problem. He previously worked at GitHub, Dropbox, and Google, served as CPO at Pluralsight, and is now co-founder and CPO of @specstoryai. This is a video of Greg at work. Sort of. SpecStory saves sessions from Claude Code, Codex, Cursor, Gemini, and other coding agents as Markdown inside the project. Then Lore mines them. Greg demonstrated the full workflow across 516 saved sessions: - Index the sessions locally instead of sending millions of tokens straight to a model - Turn each prompt, response, and next user prompt into an evidence-bearing "beat" - Use the follow-up to detect whether the human accepted, rejected, or corrected the agent's work - Find recurring practices and corroborate them across projects - Present candidate skills as dossiers with citations back to the original sessions - Install nothing without explicit human approval Five hundred and sixteen sessions stop being exhaust and become evidence for how Greg and his team actually build. Lore proposes the reusable practices. Greg decides which ones enter the skill library. Greg showed us all this and more live in our recent episode of *Show Us Your (Agent) Skills*. (video made using seedance 2.0 on @replicate!)