Regions

Regional hostnames and routing layout for EVMKit Streams and RPC.

EVMKit uses regional hosts for its public RPC and Streams surfaces.

Use the regional hosts directly when you care about latency, locality, or explicit failover behavior.

Hostname pattern

RPC API: https://rpc-<endpoint>.evmkit.app/
Streams API: wss://streams-<endpoint>.evmkit.app/

Supported endpoint families:

Europe: eu1, eu2
US: us1, us2
Canada: ca1, ca2

Current public layout

The public deployment is currently split like this:

Family	RPC API	Streams API
Europe (OVH SBG)	`rpc-eu1.evmkit.app`, `rpc-eu2.evmkit.app`	`streams-eu1.evmkit.app`, `streams-eu2.evmkit.app`
US (NY)	`rpc-us1.evmkit.app`, `rpc-us2.evmkit.app`	`streams-us1.evmkit.app`, `streams-us2.evmkit.app`
Canada (OVH BHS)	`rpc-ca1.evmkit.app`, `rpc-ca2.evmkit.app`	`streams-ca1.evmkit.app`, `streams-ca2.evmkit.app`

Global aliases are also available:

rpc.evmkit.app
streams.evmkit.app

Prefer the regional hosts when you want predictable routing. Use the global aliases only when a single default entrypoint is enough; the global aliases currently target the EU deployment.

Examples:

https://rpc-eu2.evmkit.app/
wss://streams-eu2.evmkit.app/

RPC client guidance

Use the regional RPC hosts directly when latency or explicit failover matters.
RPC hosts require HTTPS with HTTP/2.
Reuse long-lived HTTP/2 connections rather than opening a new connection for each request.
Plan for up to about 32 active HTTP/2 streams per connection.
Keep account-level RPC connection usage conservative across all regions combined; see Rate limits for the current public guidance.

Notes

quota and websocket connection limits remain global across regions