Moscow to Melbourne Latency, Ping & RTT | AS203314
Moscow to Melbourne ping and RTT: 238.9 ms, 2.12 ms jitter, 141.13 ms fiber floor, and 59.1% efficiency across AS203314. Updated 2026-07-19.
🇷🇺 This page compares the published ping and round-trip time (RTT) from Moscow (MOW) to 🇦🇺 Melbourne (MEL) with vacuum and optical-fiber physical limits.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 238.9 ms |
| Jitter | 2.12 ms |
| Packet Loss | 0.05% |
| Standard Fiber Floor | 141.13 ms |
| Fiber Efficiency | 59.1% |
| Latency Tier | Fair |
| Source Region | Europe |
| Destination Region | Asia Pacific |
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Moscow (55.75204, 37.61781) and Melbourne (-37.81400, 144.96332). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 14,412.1 km |
| Vacuum RTT floor | 96.15 ms |
| Standard fiber RTT floor () | 141.13 ms |
| Low-latency fiber material floor | 140.57 ms |
| Engineering floor (5% path allowance) | 148.21 ms |
| Research 1.33× mapped-fiber reference | 187.71 ms |
| Estimated unamplified path loss | 3026.5 dB |
| Transparent optical spans / inline amplifiers | 190 / 189 |
| Published RTT inflation over fiber floor | 1.69× |
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 | 236.1 ms |
| Median RTT (p50) | 238.5 ms |
| 95th percentile RTT (p95) | 241.8 ms |
| Maximum RTT | 244.1 ms |
| Jitter | 2.12 ms |
| Packet loss | 0.05% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 239.2 ms
- Minimum
- 236.9 ms
- Maximum
- 240.9 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Moscow (MOW)
- Destination PoP: Melbourne (MEL)
- Region overview: Europe → Asia Pacific
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
- Reverse direction: Melbourne to Moscow latency and RTT — 238.1 ms
- Moscow to Berlin latency and RTT — 26.8 ms
- Moscow to Frankfurt latency and RTT — 34.2 ms
- Moscow to Amsterdam latency and RTT — 38.8 ms
- Moscow to Paris latency and RTT — 43.7 ms
- Moscow to London latency and RTT — 44 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.