5.8 KiB
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 and French. 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: 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
src/ the game page, in pieces (joined into one index.html at build)
index.html the shell: <head>, static markup, @include lines
i18n/en.js English for every label, inlined into the page
styles/ CSS
game/ the game script, by topic: world, networks, simulation, actions, UI, map…
site/ static files, deployed as they are
i18n/it.js Italian translation (label → text), loaded only when the game runs in Italian
i18n/pt.js Portuguese (Brazil) translation, loaded only when the game runs in Portuguese
i18n/fr.js French translation, loaded only when the game runs in French
images/og-image.png social preview (1200×630)
favicon.*, icon-* favicons, app icons, manifest
sw.js service worker (offline play)
robots.txt, sitemap.xml, llms.txt, 404.html, CNAME
scripts/build.js builds _site/ for GitHub Pages: site/ + the assembled page, stamped
scripts/lib/page.js joins src/ into the page
tests/ node:test + jsdom
docs/ architecture and decisions (docs/adr/)
.github/workflows/ ci.yml (pushes to main and PRs) and release.yml (GitHub Pages deploy)
Translations
Player-facing text is keyed by label, and English is a dictionary like the others. Code says
tr('pnis.ready_in_about_n_days', {n}) (or trn('save.n_pop', n) for plurals); static markup uses
data-i18n="label". The English is in src/i18n/en.js, inlined into the page; each other language is
a site/i18n/<lang>.js file mapping the same labels to its text, plus an entry in SOT_LANGS (the
language loader in src/index.html). Missing translations fall back to English, so new text never
breaks the game; npm run i18n:check lists what needs translating, and the tests make sure every
translation keeps its {placeholders}, HTML tags and plural forms.
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
