HTTP endpoints
Use these endpoints for standard HTTP and SSE requests:| Endpoint | Region |
|---|---|
https://users.rime.ai | US West — default (alias for users-west) |
https://users-west.rime.ai | US West (us-west-2) |
https://users-east.rime.ai | US East (us-east-1) |
WebSocket endpoints
Use these endpoints for real-time streaming over WebSocket. The regional routing pattern applies to every WebSocket path (/ws, /ws2, /ws3) — the /ws3 examples below are shown because it’s Rime’s flagship WebSocket endpoint.
| Endpoint | Region |
|---|---|
wss://users-ws.rime.ai/ws3 | US West (us-west-2) |
wss://users-east-ws.rime.ai/ws3 | US East (us-east-1) |
Typical network latency
Use these rough round-trip times (RTT) — the back-and-forth network delay between your application and Rime — to pick the closest endpoint.| From metro | To US East | To US West |
|---|---|---|
| East Coast (NYC, DC, Boston, Atlanta) | 5–25 ms | 60–85 ms |
| Midwest / South (Chicago, Dallas, Denver) | 25–55 ms | 35–65 ms |
| West Coast (SF, LA, Seattle) | 60–85 ms | 5–25 ms |
- Same region (your app and the Rime endpoint in the same AWS region): typically 1–10 ms.
- Coast-to-coast: ~60 ms is the physical floor, set by the speed of light in fiber across ~2,500 miles. 60–85 ms is normal.
- Above 90 ms between major US metros usually points to a suboptimal network route, not Rime.
Choosing a region
Choose the endpoint in the region closest to where your application is deployed. For example:- If your server runs in AWS
us-west-2, useusers-west.rime.ai/users-ws.rime.ai. - If your server runs in AWS
us-east-1, useusers-east.rime.ai/users-east-ws.rime.ai.

