- Identify regions offering the best latency for your users
- Verify these regions are among the supported regions
- Contact Ona support if you need support for additional regions
Predicting Network Latency
Before deploying Ona Runners, you can measure network latency using these tools:Latency Testing Tools
- Third-party websites (search for “aws latency test”):
- 
Command-line tools:
- pingcommand (requires ICMP support)
- httping (for HTTP/HTTPS-only networks)
 
Important Considerations
- Test results reflect latency from your location to AWS regions. If users are in different locations, have them run the same tests.
- Ona is designed to work with multipe regions by installing a runner in each region.
- VPN usage affects test results. Configure your connection to match your planned Ona usage:
- Use VPN if you plan to connect to Ona through VPN
- Disable VPN if you plan to connect directly
 
Measuring Network Latency
After deploying Ona Runners, you can monitor latency using:- JetBrains IDE: Check the “backend status” view when connected to a remote dev environment
Recommended Latency Thresholds
| Latency | Experience | Recommendation | 
|---|---|---|
| < 70ms | Excellent! | Ideal for all development tasks | 
| < 120ms | Good | Suitable for most development work | 
| < 200ms | Ok | Users may notice some latency in IDE and terminal | 
| > 200ms | Poor | Not recommended. Users will experience significant delays | 
Supported AWS Regions
Ona AWS Runners are available in select regions across North America, Europe, Asia Pacific, and South America.North America
- us-east-1(N. Virginia)
- us-east-2(Ohio)
- us-west-1(N. California)
- us-west-2(Oregon)
- ca-central-1(Canada Central)
Europe
- eu-west-1(Ireland)
- eu-west-2(London)
- eu-central-1(Frankfurt)
- il-central-1(Israel Central)
Asia Pacific
- ap-southeast-1(Singapore)
- ap-southeast-2(Sydney)
- ap-northeast-1(Tokyo)
South America
- sa-east-1(São Paulo)