Does Jitter on letter J share fate with other letters?

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

Where is Jitter measured first?

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

Jitter: handoff in São Paulo (GRU) · J-17

Runbook J-17 for Jitter in São Paulo (GRU). Marker xserv-j-529f58d176e2. This page covers handoff for LATAM operators, not a worldwide average.

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: Why it matters on this continent

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 cache J-08

Cache rules for Jitter on j-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.

Jitter headers J-09

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

Jitter timeouts J-10

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

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.