No description
Find a file
jvanvik c5c7ea9508 Server-run engine: a restored network plays on exactly as before
A network loaded from its checkpoint drifted from the one that never stopped:
after a checkpoint on day 1, 2 or 5 its R differed at once (bizDem at Ashburn
6426 against 26, then cityDem, citySrv, tNet), and from the next day S too
(cash, eyeball growth). Three causes, each shown by a probe:

- R after a day is the R of the day's last routing, made before the day's end
  changed S (customers who left or signed, moods, bills, transit history) and
  routed from the memory of the R before it. srvLoad routed the saved S again
  from R's own memory: another R, which the next day reads (sfOf for eyeball
  growth, the peering share). Every compute() in the realm now keeps, for the
  R it makes, S as it routed it (one JSON per top-level key, 0.8 ms big) and
  the memory it started from. rt carries that routing point (pt: the memory,
  the keys that changed since, the keys S did not have then), and srvLoad
  routes that S again from it: the same R, byte for byte. The old restore test
  checkpointed after day 10, where a failure or event routed again at the end
  of the day and nothing changed after it: it passed by luck.
- The sales desk's tried offers (UI.slTried, an offer that did not fit waits a
  week) live outside S. A fresh realm forgot them and the desk tried other
  offers. rt carries them (sl); a day mark keeps them and the in-place restore
  after a throw puts them back (before, a parsed S dropped them).
- A save and a reload give some keys back in another key order (a customer's
  defaults go last, the intern's week tally in its own order), and the week's
  report lists the tally in that order. At a checkpoint rt carries the live
  text of each such key (ord, srvGate's round trip, about 8 ms), taken on load
  only where it holds what sanitize() made of the save. A fresh realm after a
  timeout takes the mark's own text the same way (live).

The plain game drifts across a save and a reload too (jsdom: from the first
day after it; the page routes a reloaded S with an empty R and keeps no desk
memory): a game property, so the engine carries what is missing.

The envelope keeps its shape {s, uidN, rt, last, day}; rt keeps R's own route
memory, so an older checkpoint loads as before (close, not exact). Big network:
the checkpoint grows from about 42-49 KB gzip to 54-79 KB (rt 7-29 KB; the
whole R would be 375 KB), srvSave from 2-2.5 ms to 7-8 ms, a load by one
routing. A day with its mark costs the same (big 39.8 -> 37.8 ms, busy
90.0 -> 88.8 ms, within noise: the day mark joins per-key JSON now, which pays
for the routing point).

Tests: the restore test checkpoints after days 1, 2, 5 and 10 of the scenic big
network and of the same network busy (intern on every order, the desk signing
on its own, failures, events, an attack), those after days 2 and 10 right after
an action and a what-if (sent to the copies too), each compared byte for byte
at once and 10 days later (SIM_LONG: after every day to 30, 60 checkpoints). It
fails on the old engine, and without any one of the three parts. The retry test
plays busy networks (fails without the desk memory in srvRestore). The market
checkpoint compares bytes too; canon() is gone.
2026-11-09 20:16:38 +01:00
.claude/skills Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
.github Clear the open code scanning alerts 2026-11-09 12:36:08 +00:00
docker Container image: releases only, a token by default, lean layers; every action pinned 2026-11-05 20:14:04 +01:00
docs Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
scripts Server-run engine: a restored network plays on exactly as before 2026-11-09 20:16:38 +01:00
site Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
src Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
tests Server-run engine: a restored network plays on exactly as before 2026-11-09 20:16:38 +01:00
.dockerignore Container image: releases only, a token by default, lean layers; every action pinned 2026-11-05 20:14:04 +01:00
.gitattributes Docs and guard rails: GitHub Pages only, where code goes, updated skills 2026-10-27 10:15:12 +01:00
.gitignore Multiplayer for self-hosted copies: sessions, server-side saves, a leaderboard 2026-11-07 00:42:39 +01:00
CHANGELOG.md Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
CLAUDE.md Agent mode: an AI agent plays in the player's own tab, with the agent's clock or a running one 2026-11-03 16:18:43 -05:00
CODE_OF_CONDUCT.md Code of conduct: jokes target networks, cables and routers 2026-10-31 13:24:36 +01:00
CONTRIBUTING.md README: add star history, drop Releasing, Hosting setup and Analytics; Signal is for chat, issues for anything meaningful 2026-10-27 18:26:07 +01:00
LICENSE Add MIT license, contributing guide, CLAUDE.md, architecture notes and repo skills 2026-10-25 07:07:00 +01:00
package-lock.json Move customers between paths, and big networks route in half the time (3.3.0) 2026-11-09 13:37:12 +00:00
package.json Merge upstream: Lambda Bazaar, traffic badges, moving customers and faster routing (3.3.0) 2026-11-09 19:04:21 +01:00
README.md Agent mode: an AI agent plays in the player's own tab, with the agent's clock or a running one 2026-11-03 16:18:43 -05:00

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.

Series of Tubes

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

Star history of Series of Tubes

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