Every broker sale of 1-4 alien waves became its own customer, so a large
fiber-resale business grew to tens of thousands of tiny contracts. A real
save reached 124,966 alien-wave contracts and 49 MB: localStorage stopped
accepting it (save() swallows the quota error) and every compute() walked
the whole list.
A carrier that already rents waves on a fiber now grows its contract:
slots, monthly rate and the description add up. migrate() folds older
saves the same way, keeping the unhappier mood and the earliest start.
The same spectrum is sold and the same revenue is billed.
On that save: 124,966 -> 2,190 contracts, 49.3 MB -> 4.2 MB.
Each transit flow's backhaul round trip over your own links (2× the path
latency to the exit) now affects service: free up to 20 ms (~1,500 km),
up to 20% worse at 50 ms, and half the service value past 50 ms. sfOf()
multiplies delivery by it, so revenue, broadband growth and business
customers all feel it. Peering, PNIs and caches are exempt.
City panel chip and Transit-tab warning name the far exit and the round
trip; the NOC lists slow cities. Two tests updated: Moscow on Frankfurt
transit is still fully delivered but now slow, and the Red Sea test pins
Asian demand that would otherwise churn away on Marseille transit.
The NOC's 'Recent events' (S.log) becomes the notification inbox instead of
a separate one. Entries now keep a wall-clock time, a title, a repeat count
and what they are about, and the NOC shows the last ten minutes right after
the incidents rather than at the bottom: title, short text, 'n min ago',
x N for repeats within a minute, and Open.
Open targets come from the notice itself (incidents via their ref, DDoS,
badges, goals, exchange ports and sessions, resolved incidents), then from
its own navigation button, then from the city or link its text names; 45 of
46 notices in a 60-day test game get one. A link or customer that is gone
says so. Unread counts show on the NOC chip and the phone NOC tab (not red:
red stays for incidents). Entries are validated in sanitize().
Peering inbox (Networks tab): requests from small and made-up networks
arrive with every IX port, max-prefix alerts take bilateral sessions
down for a few weeks unless answered (raise the limit for growth, keep
it down for a leak; raising it on a full table is a route leak).
Unanswered mail costs reputation, which makes selective networks up to
10% pickier. The Large Peering Model agent costs $20M a year and gets
about a third of its decisions wrong, with a log to prove it.
PNIs are ordered, not instant: 2 to 6 weeks for small networks, 6 to 12
months for big content networks, Tier 1s and big eyeballs, for new PNIs
and augments alike (halved during a conference). Content networks and
Tier 1s start at 100G; Doitsche Telekomm sells 1G. Microsnoft refuses
PNIs and IX sessions in Ashburn, New York, Boston, Atlanta and Miami.
Only delivered PNIs carry traffic, bill, or count for goals and Tier 1.
After #133 the coastline router treated Egypt and Panama as solid land, so
Marseille–Singapore sailed round Africa (21,440 km instead of 12,175) and
Miami–Lima round Cape Horn (17,700 km for a 4,220 km hop). Real systems
cross both by land: Port Said to Suez beside the canal, and Panama
(PAN AM). These are now overland edges in the sea graph, priced as the
distance they cover. The Red Sea Crisis shuts Suez, and routes are cached
per set of open passages, also in the survey worker.
Long open-water legs follow the great circle where it stays at sea,
instead of a straight line on the map. The low-latency design may land
further off and backhaul overland, and may follow the corridor of the
fastest in-service cable on the pair when that is shorter, so it matches
Hibernia again (London–New York 25.3 ms, Halifax–London 20.9 ms) and
beats cables that take detours (Lagos–Bude 32.2 against 37.6 ms).
Tests: main's expectations restored where #133 had loosened them
(Marseille–Singapore needs no upgrades, New York–Sydney needs terminals,
express equals the fastest cable); the marine check knows the passages;
new checks for Suez, Panama, the crisis and the corridor rule.
The editor gets a help page (how exits are picked, the workflow, every
rule with its real-router equivalent) and seven ready-made scripts
filled in from the live network: Shields Up, Customer Care, Peering
First, Penny Pincher, Prepend Diet, Maintenance Window and Keep Calm.
Slop it with AI dry-runs its favourite recipes against live traffic,
keeps the best, and signs it with a pun-named model and a confident
remark. The glossary mentions RouteScript too.
Halifax, Bermuda, Ponta Delgada (Azores), Tenerife, Praia (Cape Verde)
and St Helena, the islands each their own landmass with outlines on the
map. Exchanges only where one runs today (CVIXP in Praia, HFXIX in
Halifax); none in Bermuda, the Azores, the Canaries or St Helena.
Cables follow real landings: new pairs on Hibernia Express (Halifax),
Nuvem (Bermuda), Columbus III (Azores), EllaLink (Cape Verde), Equiano
(St Helena), SAT-3, ACE, 2Africa and WACS (Canaries, WACS also Cape
Verde), existing pairs untouched so saves keep their links. New: Sol
(Florida, Bermuda, Azores, Santander), Atlantis-2 (Las Toninas,
Fortaleza, Praia, Dakar, Tenerife, Sesimbra) and Canalink as puns.
Crossings just over the 6,000 km 1.6T reach now split at the islands:
Miami-Madrid, Atlanta-Lisbon, Lisbon/London-Lagos and Fortaleza-Madrid
go from 1.2T to 1.6T per wave hop by hop.
Island networks with Tier 1 upstreams (One Communications, CV Telecom,
Sure South Atlantic, Eastlink as puns), MEO in the Azores, Bell in
Halifax, Bermuda Triangle cuts, and the Mid-Atlantic Accent scenario.
Broadband in a town smaller than 8 Gbps now starts at its ceiling
instead of above it.
A link's routing metric could only be one of four presets (Prefer,
Normal, Avoid, Backup only). Links now also get a Custom option, closer
to how real networks tune IGP metrics:
- Multiplier mode scales the distance cost, (km + 60) × 0.1 to 100.
- Cost mode sets an exact cost, 1 to 65535 like an OSPF metric.
The preset buttons stay plain. Picking Custom explains how a link's cost
is worked out and lists what each preset comes to on that link. Choosing
Custom starts from the current preset and switching modes keeps the
effective cost, so nothing moves until the player changes the value.
Like the presets, it applies to every link between the two cities.
The cost formula lives in one helper, linkW(), used by compute() and the
traceroute paths. Custom links store mk/mv, which sanitize() repairs and
clamps; old saves load unchanged. The link panel skips its daily
re-render while the number field has focus, and Enter applies the value.
Tests cover routing equivalence with the presets, rerouting by cost,
mode switching, input clamping, saves, and the panel at desktop and
phone width. French, Italian and Portuguese for the new strings.
Perf on the big network: no change beyond noise, routing identical to
main.
Porto Alegre and Florianopolis are 65 px apart at the old maximum zoom,
and each city grabbed taps within 38 px, so the link between them could
not be selected at all. The maximum zoom goes from 6x to 16x (city icons
stop growing at 1.35x, so dense regions spread out), and a city now wins
a tap outright only on its icon; in the rest of its tap circle a link
right under the pointer wins. The hover cursor follows the same rule.
Dragging from a POP still draws a new link.
Wholesale alien waves and spare-pair leases already existed, but only as
random offers, and the fiber only said how many channels were sold. Each
dark fiber in service now has a 'Selling spare capacity' section: free
channels, who rents what and for how much, a pending offer with Accept,
and 'List it with a capacity broker', which creates an offer for that
fiber at once at the usual price minus a 10% broker cut (alien waves on
free channels first, then a spare pair in your own trench). One listing
per fiber at a time. Random offers use the same helpers and draw the same
random numbers in the same order, so seeded games are unchanged.
- #113: the goal was a Marseille-Singapore path and 300 Gbps served
anywhere, which broadband with local transit reached on day 0. It is now
the path plus 80 Gbps on your links between Asia and the rest of your
network for 30 days in a row (S.stats.asiaRun). A 100G route around Africa
gets there in about two months and costs about 590k a month against 2.5M
of starting cash, so it is a real challenge. The scenario card shows
today's traffic and the streak.
- #84: Poste Restante, Luxembourg's eyeball network, at LU-SICK in
Bettembourg (selective, buys transit from Tier 1s, so Tier 1 reach holds).
Citrus Belgium's blurb now says it is Tangerine's Belgian daughter.
- The wave seller and wholesale customer 'GTT (Got Tangled Twice)' used a
real company name; it is now 'G&T (Gin and Transit)'.
- The scenario start toast puts a full stop after the goal.
S.scrubAt/S.scrubTier become S.scrubs, one center per city, each with its
own size and monthly fee; old saves carry theirs over in sanitize().
An attack goes to the nearest working center with a backbone path, and
spills to the next when it is full. A remote center's flood (plus a share
of the victim's own traffic) is reserved along the backbone path after
the L2 circuits, like a circuit: it fills those links, the round trip is
shown in the NOC, and what the links cannot carry is not scrubbed and
lands on the city. Local centers behave as before.
DDoS protection customers lose mood while their attack detours 30+ ms,
with the reason in their row; a new requirement asks for a center on the
customer's continent. The Infra tab names the nearest center and its
distance, and How to play explains it.
Goals gets a Tier 1 card once it is the current goal (or the title was
lost): transit ports left, Tier 1 PNIs with the missing ones named, the
club requirements they wait for, and reach without transit with the
networks you would lose. The Networks tab gains an 'out of reach without
transit' filter and a single-network view with every PNI city and
exchange, your POPs first, then nearest. The NOC transit to-do list names
the nearest city and links to the network.
Routing counts reach without transit in the same pass. Places and
distances are cached until the POP set changes, and exchange membership
once per routing pass, so the Networks tab costs what it did.
- Upgrades take effect: the optic speed cache from #89 is now kept per cable
state (subsea, terminals in service, engineering in service), so a cable
no longer stays at 400G after both upgrades are commissioned.
- Refunds: a cable remembers what was paid for it, design and upgrades
included. Calling off a 7x low-latency cable returned 10% of its price.
'Unusable' now means no optic lights it even with both upgrades.
- Length limit: #88 counts the shortest design and both upgrades. The order
screen says which upgrade a route needs and will not order without it;
the order action checks the same. New York to Sydney needs terminals.
No leased-wave payback hint where no leased wave reaches.
- Choices start fresh when you open the own-cable view and after ordering.
- The 'consider terminals or engineering' hint only on cables you own.
- Low-latency builds take 1.7x as long (London-New York ~2.9 years), not
3.5x; optimized 1.3x. Each design is one tappable card.
- The low-latency factor is worked out once per route instead of on every
latency lookup. 'Number.isFinite' alone, no repeated guard in seaQuote,
the express factor folded into seaLatencyFactor, '+{n} days' as one
translatable string.
- Portuguese and French for the new strings; one CHANGELOG bullet (#65).
Big network vs main: no slowdowns, identical routing.
"Caisse · Banque" wrapped onto two lines in the phone's top bar at 360 px
and cut off the monthly line under the cash. "Cash · Banque" fits on one
line like the Italian and Portuguese labels do.
The CHANGELOG named Vodafone instead of Voda-Phony. The note claimed more
carrier-neutral data centers than Hamburg and Munich together; #108 only
says more than each of them.
After #115: upgrading an existing PNI, in the Peering tab and in the NOC's
connection list, also showed only the one-off cost. Both now read
'Upgrade 100G $2.3k + $350/mo', like transit. The two old labels without a
monthly part are no longer used and leave it.js and pt.js.
Networks follow PeeringDB's 14 Düsseldorf facilities: NTT, Tell-Ya,
Cogentle, Drizzle, Voda-Phony, Doitsche Telekomm and the Crowdflare,
Amazin', Microsnoft and BiteDance clouds (NetChill and Akamaybe are
everywhere already). No nudge needed: 27+ map units from Frankfurt,
Amsterdam and Brussels.
The #16 shark test compared .land, which ignores Cairo's land2, so a
valid overland Mumbai-Cairo ask counted as crossing an ocean once the
extra city shifted the seeded draws. It now uses isSub like the game.
The buy buttons only showed the one-off setup (1500 + setup/2), so a
$1.8k cross-connect read like a monthly bill, while the real monthly
fee (PORT[i].pni) was shown nowhere. Reuse the existing translated
'{port} <small>{cost} + {mo}/mo</small>' label, like transit and IX.
CITY_PDB holds, per city, the carrier-neutral facilities and network
presences from PeeringDB (within 50 km or same city name) and the ASN
count of its country from bgp.he.net, pulled 2026-10-25.
- Transit: the regional multiplier is scaled by competition, up to 1.8x
where few networks are present. Hubs (1000+ presences) are unchanged,
and hand-set markets (Korea, Belgian red tape) keep their price.
- POPs: 1.25x to build and run with one or two facilities, 1.5x with none.
- Offers: countries with 2000+ ASNs bring extra ISP customers.
Honolulu, Guam, Koror, Majuro, Port Moresby, Honiara, Noumea, Suva,
Nuku'alofa, Apia, Pago Pago and Papeete, each its own landmass with its
real outline on the map. Exchanges only where one runs today (DRF IX,
Guam IX, Fiji-IXP, CAN'L IXP, Solomon Islands IX); PNG and Tonga have
none active, Samoa's is still planned.
Cables follow real landings: new pairs on Southern Cross, Hawaiki, AJC,
JGA, Bifrost and Humboldt (existing pairs untouched, so saves keep their
links), plus SEA-US, AAG, Echo, HANTRU-1, Coral Sea, Gondwana-1, Tonga
Cable, Tui-Samoa, ASH, Honotua, Manatua and SX NEXT as puns.
Subsea waves have no regens, so a POP on an island splits a crossing into
shorter spans: California-Sydney 400G -> 1.6T per wave via Honolulu and
Suva, LA-Hong Kong/Manila 400G -> 800G via Guam, Santiago-Sydney
400G -> 800G via Tahiti (1.2T on own fiber). LA-Tokyo stays 800G leased:
Honolulu-Guam is just over the 6,000 km 1.6T reach.
Twelve island networks, all with Tier 1 upstreams so Tier 1 players keep
their reach. PacNOG in Suva, unreliable power in Guam, Port Moresby and
Honiara, volcano cuts for Tonga, and the Stepping Stones scenario
(1.6T hop by hop from Los Angeles to Sydney).
The group split runs over an index range with one scratch array instead of
map/reduce/forEach and slice, leftover exits go into one reused array and are
sorted in place (insertion sort for short lists; both sorts are stable, so
the order is the same), flows are split without per-flow arrays, and the hot
loops use indexes instead of for...of. Without Auto-TE, exits whose path is
already full are not called at all. One routing pass on the big network
allocates 23 MB in Chromium instead of 66 MB.
Routing results are identical. The speed test's plain path now also uses the
original group split and sort, and a new test routes around a full 10G link
with Auto-TE (and a spill script) and compares both paths; planted bugs in
the split, the sort and both full-path skips are caught.
Big network vs main, two runs: headless routing -23% to -30%, Chromium
desktop -14% to -27%, phone -15% to -27%. Steps 2-4 together vs c76dd4d:
Chromium desktop routing -49%, phone -34%, a game day -26% and -30%.
Capacity only shrinks while traffic is routed, so a path with one full link
or node fits nothing for the rest of the pass: push marks it and later tries
return at once (92% of pushes on the big network went into such paths). The
nearest group of exits is found in one scan instead of two, and exits that
filled up are dropped from the shared lists once a quarter of a list is full.
Routing results are identical to before. The speed test's plain path now also
runs without these, with Auto-TE and with a RouteScript that keeps headroom on
every link; planted bugs in each of the three are caught.
Big network vs main, two runs: headless routing -51% to -58%, Chromium
desktop -22% to -31%, Chromium phone -15% to -29%.
Adds site/i18n/fr.js with all 2541 strings, registers Français in the
language list (picked automatically for fr-* browsers), caches it in the
service worker, and runs the full screen tour and the Signal-link check
in French in the tests.
npm run perf -- --browser times the same workloads in Chromium as a desktop
and as a phone (390x844 at 3x, CPU slowed 4x), one browser per version. Each
run collects garbage first and ends by forcing layout and the map canvas, so
deferred work counts. The jsdom DOM is about 30x slower than a browser's and
has no layout, so the interface rows need this.
Shared machines swing single runs by 30% on identical code, CPU time
included. A row now counts as slower or faster only when it moved 15% and a
Mann-Whitney U test gives p < 0.01 (15 runs a side by default). Identical
code: no flags in three full runs; a routing slowdown planted in a copy is
flagged in jsdom and on the phone.
The panel workload renders both selections every run instead of alternating,
which split its samples in two. CI drives the runner's Chrome through
playwright-core, no browser download.
Its fallback ladder skipped 1.2T, so between 4,000 and 5,500 km on land
(6,000-8,250 km subsea) it carried 800G while the cheaper 1.6T optic
carried 1.2T. A test now checks that a bigger optic on the same line
system never carries less than a smaller one at any distance.