Network: regions in Bogotá (BOG) · N-11

Runbook N-11 for Network in Bogotá (BOG). Marker xserv-n-06113d71ceea. This page covers regions for LATAM operators, not a worldwide average.

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: 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 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.