Does Network on letter N share fate with other letters?

The control plane is shared. Data-plane queues for Network stay isolated, so incident n-01 cannot drain neighbor letters.

Where is Network measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter N.

How fast is rollback for n-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

Network as the product, not a hidden diagram

Routing policy, MTU, and prefix lists are documented the same way APIs are: versioned, reviewable, reversible.

Network: Why it matters on this continent

Design for Network on letter N starts in São Paulo (GRU). Runbook n-01 keeps a single owner, a written rollback, and a traffic split that can be reversed without a global freeze. Neighbors in Santiago only take overflow after the local pool fails a health window.

Network: How XServ runs it day to day

Probes for Network (n-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.

Network: What operators should measure

Policy for Network is versioned as n-03. Operators measure error rate, p95 from Bogotá, and time-to-rollback — not a worldwide average. Changes land in Bogotá first, then Miami, with a hold if either region regresses.

Network: Failure modes we actually see

Capacity notes for n-04 assume rainy-season power in Miami and festival peaks toward São Paulo. The failure we actually see is a single uplink, not a cartoon partition of the whole continent. Spare ports and a second provider sit on the same runbook.

Network: How this letter ties to the rest

Handoff from letter N Network into the rest of the platform uses the same request IDs as the gateway. Runbook n-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

Network: A note on cost and transit

Rollback for n-06 is a documented command, not a hope. Transit is billed as backup while Network prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.

Network design N-01

Network probe N-02

Network policy N-03

Network capacity N-04

Network handoff N-05

Network rollback N-06

Network peering N-07

Peering for Network (n-07) prefers the IX fabric that already carries last-mile ISPs in Bogotá. Session counts and prefix limits are on the same page as the Miami backup path.

Network cache N-08

Cache rules for Network on n-08 keep language-correct objects near Miami. São Paulo is a sibling cache, not an origin. TTLs are short enough that a bad asset does not live through a weekend.

Network headers N-09

Headers for n-09 carry the letter, the region (GRU) and a request id. Network debugging in São Paulo should not require a packet capture in Santiago first.

Network timeouts N-10

Timeouts on n-10 are tighter than the WAN RTT to Bogotá. Network in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

Network regions N-11

Region names on n-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. Network dashboards never say “LATAM” as if it were one RTT.

Network docs N-12

Public docs for letter N stay aligned with identifier xserv-n-pack. Page n-12 is the Network slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.