Reference
Regions
Where Kestrel stores and delivers your events, and how to pin an account to one.
Regions
Every account is pinned to a single region at creation. Events are stored and delivered from that region only.
Available regions
| Region | Identifier | API host | Data residency |
|---|---|---|---|
| US East (Virginia) | us-east-1 | api.kestrel.dev | United States |
| EU West (Ireland) | eu-west-1 | eu.api.kestrel.dev | European Union |
| Asia Pacific (Sydney) | ap-southeast-2 | ap.api.kestrel.dev | Australia |
api.kestrel.dev is an alias for the US region, not a global router. An EU account
calling api.kestrel.dev gets 404 account_not_in_region.
Choosing at signup
Region is chosen once, during account creation, and cannot be changed afterwards. Moving regions means creating a new account and re-pointing your subscriptions.
There is no cross-region replication. A regional outage suspends delivery for accounts in that region until it clears; events published during the outage are queued, not lost.
Egress addresses
Deliveries originate from a fixed set of addresses per region. Allowlist the whole block rather than individual addresses — they rotate within the block without notice.
198.51.100.0/24
203.0.113.0/24Latency
Median publish-to-delivery latency, measured over the last 30 days:
| Region | p50 | p95 | p99 |
|---|---|---|---|
us-east-1 | 180 ms | 410 ms | 1.2 s |
eu-west-1 | 195 ms | 450 ms | 1.4 s |
ap-southeast-2 | 240 ms | 620 ms | 2.1 s |
These are measured to the point Kestrel writes the request, and exclude your endpoint's own processing time.