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: regions in Bogotá (BOG) · N-59

Runbook N-59 for Network in Bogotá (BOG). Marker xserv-n-9adb774db57b. 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 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.