Uptime: headers in São Paulo (GRU) · U-57

Runbook U-57 for Uptime in São Paulo (GRU). Marker xserv-u-d7a4b5cec0ea. This page covers headers for LATAM operators, not a worldwide average.

Uptime: What operators should measure

Policy for Uptime is versioned as u-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.

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

Uptime headers U-09

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

Uptime timeouts U-10

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