Is transit the default path?

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

Does Uptime on letter U share fate with other letters?

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

Uptime: capacity in Miami (MIA) · U-64

Runbook U-64 for Uptime in Miami (MIA). Marker xserv-u-5c94cb674a9e. This page covers capacity for LATAM operators, not a worldwide average.

Uptime: Failure modes we actually see

Capacity notes for u-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.

Uptime: How this letter ties to the rest

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

Uptime: A note on cost and transit

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

Uptime handoff U-05

Uptime rollback U-06

Uptime peering U-07

Peering for Uptime (u-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.

Uptime cache U-08

Cache rules for Uptime on u-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.