Edge: policy in Bogotá (BOG) · E-75

Runbook E-75 for Edge in Bogotá (BOG). Marker xserv-e-108ae3e8f9fa. This page covers policy for LATAM operators, not a worldwide average.

Edge: What operators should measure

Policy for Edge is versioned as e-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.

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

Edge docs E-12

Public docs for letter E stay aligned with identifier xserv-e-pack. Page e-12 is the Edge slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.

Edge design E-01

Design for Edge on letter E starts in São Paulo (GRU). Runbook e-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.