Jitter: timeouts in Santiago (SCL) · J-70

Runbook J-70 for Jitter in Santiago (SCL). Marker xserv-j-51f61bf49359. This page covers timeouts for LATAM operators, not a worldwide average.

Jitter: Failure modes we actually see

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

Jitter: How this letter ties to the rest

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

Jitter: A note on cost and transit

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

Jitter regions J-11

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

Jitter docs J-12

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

Jitter design J-01

Design for Jitter on letter J starts in São Paulo (GRU). Runbook j-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.

Jitter probe J-02

Probes for Jitter (j-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.