A load whose networks did not all check out could hang its session for good, a worker could spin on a job it could never run, a session whose load crashed its worker never got a worker of its own, and an unload followed at once by a load (a language change) lost the session's place or never answered. Fixed: - Worker: a load call is checked whole before it touches anything. One that names no network, or one twice, is refused (ERR) and every realm stays as it was. A network without a save now answers err (broken) like one whose save does not load, and the others load. A network marked loading with no load under way answers NO_REALM instead of waiting for ever. - Worker: it goes on only while something ran. If a job were ever still waiting when nothing could run, it is answered (ERR, logged) rather than left pending, and the worker no longer busy-loops on it. - Engine: a session is on its worker from the moment its load is sent. A worker exit counts against the sessions whose load was under way (else against every session it held), so a save that crashes its worker gets a worker of its own after two exits and is given up (GAVE_UP) after a third, while the sessions that only shared the worker lose their realms but not their place in the pool. Loads under way count for placement. - Engine: an unload no longer drops the placement of a session whose next load is under way, so an unload and a load sent back to back stay on one worker; a worker of its own is retired only when no call is pending on it (a pending call there used to never settle). - Engine: a message that cannot be sent rejects (ERR) and leaves nothing pending. - Realm: a what-if puts UI.hotMap back too (teSlop's trial left its own). - Realm: a network in a language this server has no dictionary for plays in English, as the page does, instead of loading broken. Tests (tests/mp-sim-engine.test.js): a malformed load changes nothing and every call of the session answers within 3 s, with the workers idle after; an unload and a load back to back keep the session on its worker; a session whose load takes its worker down twice gets a worker of its own, then GAVE_UP, while the bystander is never blamed; an ask leaves UI.hotMap as it was; a network in an unknown language loads in English. Each fails on the engine before this change (the worker's alone: the hang; the engine's alone: the placement and the exits; the realm's alone: teSlop's hotMap and the language). The two drafts no test played are played now (tests/mp-sim-acts.test.js): a premium border crossing into Hong Kong (buildLink with cnPrem) and the AI's own script deployed as it wrote it while it drops most of the traffic (teDeploy with slop, on a small network with one capped transit port), each compared byte for byte with the page's clicks, and both read in the DRAFTS check (nothing is left unplayed). Runs, each file alone under an 8G cap: mp-sim-engine 16/16 (11.6 s), mp-sim-contract 8/8, mp-sim-acts 5 + 1 todo (10.9 s), mp-sim-determinism 6/6 (53.4 s). |
||
|---|---|---|
| .claude/skills | ||
| .github | ||
| docker | ||
| docs | ||
| scripts | ||
| site | ||
| src | ||
| tests | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
Series of Tubes
Build the internet, one tube at a time. A free cartoon browser game about how the internet really works. Play it at seriesoftub.es.
You start with one router in one city and grow into a transit-free Tier 1:
- Customers: home broadband ("eyeballs"), enterprises, hosting, L2VPNs, DDoS protection, high-frequency traders with latency budgets, AI GPU data centers and hyperscaler DCI deals. Some come with very specific requirements.
- Interconnection: IP transit billed on the 95th percentile, internet exchanges with route servers, open/selective/restrictive/paid peering, PNIs, embedded CDN caches, and NNI fabrics for virtual circuits and remote peering.
- Infrastructure: leased waves on around 40 subsea cable systems modelled on real ones, dark fiber (leased or self-built) lit with DWDM and ZR+ optics, router generations that cap your port speeds, and LAGs to bundle ports when one isn't enough.
- Traffic engineering: see exactly what fills each link, tune link metrics and egress preferences, and route traders over the fastest path and backups the scenic way.
- Things break, constantly: backhoes, sharks, fat fingers, route leaks, RPKI mishaps, DDoS, cooling failures, Red Sea and Baltic cable cuts, sanctions and sovereign internet drills.
Every company is a pun. No real company names are used.
Learn how it really works
This game simplifies a lot, and gets some things gloriously wrong on purpose. For the real thing, go to How the Internet Works by Thomas Kjær Aabo (source): an interactive, zoomable map that follows your data from Wi-Fi and copper to undersea fiber, as the internet works today, in 2010 and in 1995, with simple or technical explanations. If you enjoy Series of Tubes, you will learn more from an hour there than from a year of laying cartoon fiber here.
Playing locally
It is a single static page, assembled from the files in src/ by a small Node script:
npm ci
npm run dev # http://localhost:8080
Progress is saved in your browser's local storage.
The game speaks English, Italian, Portuguese, French, Spanish and German. It follows your browser's language the first time and remembers the one you pick under Settings or on the title screen.
Development
npm ci
npm run dev # development server on localhost (--host to share): assembles src/ on every request, reloads on save
npm test # headless tests: boot, geography, a year of play, every incident, every panel
npm run build # writes the site for GitHub Pages to _site/, with version and date stamped in
npm run i18n:check # lists text missing from (or stale in) the translations
npm run mcp # the game as an MCP server, so an AI client can play and debug it, headless or in your tab (docs/MCP.md)
Community
Come hang out in the Series of Tubes Signal group. Share screenshots of your network, suggest cities, and argue about peering policy with other players. There are fewer backhoes there than in the real thing.
Signal is for chatting. Bugs, feature requests and anything else that should not get lost go into a GitHub issue.
Star history
Contributing
Issues and pull requests are welcome. See CONTRIBUTING.md. Everyone taking part follows the Code of Conduct: be excellent to each other.
License
MIT © 2026 Frederic Jung
