No description
Find a file
jvanvik 1f76639b8f Selective peers will not meet you where a satellite is your only way out (#83)
An island or remote town that only satellite circuits join to the rest of
your network (satOnly: no built wave, fiber, cable or pie dish there, its
fastest circuit otherwise) is a place many selective networks will not
peer: they would hand you traffic for your whole network to haul through
orbit. Like remote peering, the verdict is stable per network (a hash):
60 in 100 selective networks refuse a GEO hop, 15 in 100 a MEO one, and
every network that minds MEO minds GEO too. It is judged on what is built,
never on today's cuts, so the single-spur trap does not also pause your
peering mid-outage.

peerOk refuses new IX sessions and PNIs there with one line naming the
orbit and the circuit's round trip; ixSessions leaves an existing session
out while the island is satellite-only, without deleting it from S.peers,
so it carries again once a wave or cable is lit. Existing PNIs stay. No new
state, nothing for saves.
2026-11-09 23:01:51 +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 Plans: the server-run design in the repo, what is left now, and the fork's files 2026-11-09 23:01:43 +01:00
scripts Server-run engine: review fixes 2026-11-09 22:16:52 +01:00
site Selective peers will not meet you where a satellite is your only way out (#83) 2026-11-09 23:01:51 +01:00
src Selective peers will not meet you where a satellite is your only way out (#83) 2026-11-09 23:01:51 +01:00
tests Selective peers will not meet you where a satellite is your only way out (#83) 2026-11-09 23:01:51 +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 Selective peers will not meet you where a satellite is your only way out (#83) 2026-11-09 23:01:51 +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