Active regions
| Region | Location | Approx. latency |
|---|---|---|
| NYC | New York, USA | ~10ms |
| AMS | Amsterdam, Netherlands | ~16ms |
| FRA | Frankfurt, Germany | ~18ms |
Latency figures are measured from co-located infrastructure within each region. Actual latency from your application depends on your network location.
Coming soon
| Region | Location |
|---|---|
| DAL | Dallas, USA |
| LON | London, UK |
| SGP | Singapore |
| TYO | Tokyo, Japan |
| BKK | Bangkok, Thailand |
Service availability by region
All active regions support the full set of Solami services.| Service | AMS | FRA | NYC |
|---|---|---|---|
| RPC | Yes | Yes | Yes |
| WebSocket | Yes | Yes | Yes |
| gRPC | Yes | Yes | Yes |
| ShredStream | Yes | Yes | Yes |
| Dedicated Nodes | Yes | Yes | Yes |
Choosing a region
The right region depends on your use case. MEV and trading — choose the region where your validator or co-located infrastructure runs. Lower round-trip time directly reduces your reaction latency. General development — any active region works. Pick the one geographically closest to where your application runs. Co-location — Amsterdam (AMS) is recommended if you’re deploying on DigitalOcean or similar providers alongside Solami infrastructure.Next steps
ShredStream
Configure ShredStream in your nearest region for sub-block latency.
Dedicated Nodes
Provision a bare metal server in your preferred region.
RPC
Connect to the RPC endpoint for your region.