Where is Edge measured first?

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

How fast is rollback for e-03?

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

Edge: timeouts in Santiago (SCL) · E-10

Runbook E-10 for Edge in Santiago (SCL). Marker xserv-e-bcf25d4e10b7. This page covers timeouts for LATAM operators, not a worldwide average.

Edge: Failure modes we actually see

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

Edge: How this letter ties to the rest

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

Edge: A note on cost and transit

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

Edge cache E-08

Cache rules for Edge on e-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.

Edge headers E-09

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

Edge timeouts E-10

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

Edge regions E-11

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