Seattle to Moscow Latency, Ping & RTT | AS203314
Seattle to Moscow ping and RTT: 164.1 ms, 1.62 ms jitter, 82.23 ms fiber floor, and 50.1% efficiency across AS203314. Updated 2026-07-19.
🇺🇸 This page compares the published ping and round-trip time (RTT) from Seattle (SEA) to 🇷🇺 Moscow (MOW) with vacuum and optical-fiber physical limits.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 164.1 ms |
| Jitter | 1.62 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 82.23 ms |
| Fiber Efficiency | 50.1% |
| Latency Tier | Fair |
| Source Region | North America |
| Destination Region | Europe |
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Seattle (47.60621, -122.33207) and Moscow (55.75204, 37.61781). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 8,396.9 km |
| Vacuum RTT floor | 56.02 ms |
| Standard fiber RTT floor () | 82.23 ms |
| Low-latency fiber material floor | 81.9 ms |
| Engineering floor (5% path allowance) | 86.35 ms |
| Research 1.33× mapped-fiber reference | 109.36 ms |
| Estimated unamplified path loss | 1763.3 dB |
| Transparent optical spans / inline amplifiers | 111 / 110 |
| Published RTT inflation over fiber floor | 2× |
Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full theoretical fiber latency, GeoNames, attenuation, and amplifier methodology.
Stability & Trend
The following estimated indicators summarize route stability for the current publication period and are intended for comparative planning rather than SLA evaluation.
| Stability Indicator | Value |
|---|---|
| Minimum RTT | 162.5 ms |
| Median RTT (p50) | 163.8 ms |
| 95th percentile RTT (p95) | 166.2 ms |
| Maximum RTT | 168.2 ms |
| Jitter | 1.62 ms |
| Packet loss | 0% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 163.9 ms
- Minimum
- 162.9 ms
- Maximum
- 165.7 ms
- Average loss
- 0.03%
Route Context
- Departure PoP: Seattle (SEA)
- Destination PoP: Moscow (MOW)
- Region overview: North America → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
- Reverse direction: Moscow to Seattle latency and RTT — 166.1 ms
- Seattle to Los Angeles latency and RTT — 27.1 ms
- Seattle to New York latency and RTT — 59.1 ms
- Seattle to Ashburn latency and RTT — 61.8 ms
- Seattle to Miami latency and RTT — 81.1 ms
- Seattle to Tokyo latency and RTT — 84 ms
About This Measurement
Published RTT reflects best-case backbone path behavior. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. Stability indicators are comparative estimates, and none of these values is an SLA.
Data auto-generated on July 19, 2026. Explore the full interactive latency matrix or browse more city-pair routes.