Skip to main content

Edge + core · latency budgeting

Global infrastructure narrative for nodejs traffic

This page explains how we talk about regions, PoPs, and failover—without implying outcomes your own measurements must still validate for node-js clients worldwide.

Latency is an empirical claim
Decorative map abstraction: verify with RUM data from your own node applications.

Edge responsibilities

TLS, HTTP/2, bot mitigation hooks—configured per hostname with change logs.

Core responsibilities

Stateful node processes, autoscaling signals, and disk IO class tied to tier.

Failover drills

Game-day exercises scheduled with customer observers when requested.

Texas operations anchor

Corporate address on Congress Ave remains the legal anchor even when workloads span regions.

Data residency notes

Certain industries require data location attestations—procurement packs available for a documented fee.

Measurement checklist

Measurement checklist
RUMSyntheticTraceroutePayload profiles

Need latency tables?

Authenticated portal exports include regional median tables updated monthly.

Client portal