ICMP RTT metrics from São Paulo, Brazil to Moscow, Russia: average, minimum, maximum, jitter, packet loss, and fiber efficiency for this route.

🇧🇷 São Paulo, Brazil (GRU) → 🇷🇺 Moscow, Russia (MOW)

Measurement round: 2026-08-15T04:03:13Z.

During the 2026-08-15T04:03:13Z measurement round, the São Paulo-to-Moscow ICMP path reported a 216.2 ms average RTT across 50 samples, with a minimum of 210.33 ms and a maximum of 232.83 ms. Every probe was returned; packet loss was 0%.

The route’s standard deviation was 4.68 ms, about 2.2% of the average, and jitter was 4.59 ms. This variability is below the 3.08% median for the 19 outbound routes in the round, while the path ranked twelfth in that outbound set.

For a geodesic distance of 11,791.1 km, the vacuum floor is 78.66 ms and the fiber floor is 115.47 ms. The observed 216.2 ms average is 1.87 times the fiber floor, placing this route at 53.4% fiber efficiency and confirming the Fair latency tier is primarily a consequence of the long continental separation, not unstable delivery.

Latency Summary

Metric	Value
RTT	216.2 ms
Jitter	4.59 ms
Packet Loss	0%
Standard Fiber Floor	115.47 ms
Fiber Efficiency	53.4%
Latency Tier	Fair
Source Region	South America
Destination Region	Europe

Ping Measurement Series

The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart.

Ping series: GRU → MOW

50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 216.2 ± 0.66 ms (SE)

Sample distribution: box = interquartile range (212.9–218.8 ms), median 215.2 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.

How to read this chart

The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.

The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (115.5 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	212.08
2	100	214.44
3	200	220.55
4	300	215.15
5	400	211.47
6	500	211.96
7	600	212.33
8	700	218.91
9	800	215.24
10	900	211.09
11	1000	219.13
12	1100	213.84
13	1200	215.05
14	1300	216.50
15	1400	212.83
16	1500	232.83
17	1600	221.23
18	1700	216.21
19	1800	213.17
20	1900	215.86
21	2000	213.10
22	2100	211.23
23	2200	220.23
24	2300	213.21
25	2400	215.37
26	2500	213.11
27	2600	230.65
28	2700	221.20
29	2800	224.79
30	2900	218.59
31	3000	220.52
32	3100	213.60
33	3200	212.83
34	3300	219.40
35	3400	213.37
36	3500	214.17
37	3600	212.27
38	3700	212.48
39	3800	222.96
40	3900	217.34
41	4000	215.87
42	4100	215.18
43	4200	212.40
44	4300	210.33
45	4400	213.26
46	4500	210.58
47	4600	218.32
48	4700	219.73
49	4800	216.21
50	4900	217.83

Download This Route's Data

This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See About This Measurement for citation guidance.

Download this dataset

Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for São Paulo (-23.54750, -46.63611) and Moscow (55.75204, 37.61781). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	11,791.1 km
Vacuum RTT floor	78.66 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	115.47 ms
Low-latency fiber material floor	115 ms
Engineering floor (5% path allowance)	121.26 ms
Research 1.33× mapped-fiber reference	153.57 ms
Estimated unamplified path loss	2476.1 dB
Transparent optical spans / inline amplifiers	155 / 154
Published RTT inflation over fiber floor	1.87×

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 current measurement round (2026-08-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	210.33 ms
Average RTT	216.2 ms
Maximum RTT	232.83 ms
Standard deviation	4.68 ms
Stdev / average	2.2%

RTT trend

Estimated route stability across the selected time window.

Average: 216.3 ms
Minimum: 214.4 ms
Maximum: 218.1 ms
Average loss: 0.02%

Route Context

Departure PoP: São Paulo (GRU)
Destination PoP: Moscow (MOW)
Region overview: South America → Europe
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Moscow to São Paulo latency and RTT — 214.9 ms

Fastest routes departing São Paulo (GRU)

São Paulo to Miami latency and RTT — 74 ms
São Paulo to New York latency and RTT — 122 ms
São Paulo to Ashburn latency and RTT — 128 ms
São Paulo to Los Angeles latency and RTT — 130.8 ms
São Paulo to Seattle latency and RTT — 156 ms

Fastest routes arriving at Moscow (MOW)

Berlin to Moscow latency and RTT — 28 ms
Frankfurt to Moscow latency and RTT — 34.8 ms
Amsterdam to Moscow latency and RTT — 38.2 ms
London to Moscow latency and RTT — 44.1 ms
Paris to Moscow latency and RTT — 44.5 ms

Same corridor (South America → Europe)

São Paulo to London latency and RTT — 174.7 ms
São Paulo to Paris latency and RTT — 179.4 ms
São Paulo to Amsterdam latency and RTT — 181.3 ms

About This Measurement

Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA.

The measurement round behind this page is published as open data under CC BY 4.0 in the Hats Network latency dataset. Per-pair files are available at /opendata/latency/latest/pairs/gru-mow.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Moscow round 2026-08-15T04:03:13Z, CC BY 4.0".

Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.

São Paulo, Brazil → Moscow, Russia RTT