Berlin, Germany → São Paulo, Brazil RTT
ICMP echo RTT measurement page for Berlin, Germany to São Paulo, Brazil: 186.5 ms average RTT, zero packet loss, 5.27 ms jitter.
🇩🇪 Berlin, Germany (BER) → 🇧🇷 São Paulo, Brazil (GRU)
Measurement round: 2026-08-16T04:07:28Z.
During round 2026-08-16T04:07:28Z, 50 ICMP echo samples from Berlin, Germany to São Paulo, Brazil averaged 186.5 ms, with a minimum of 179.2 ms, a maximum of 206.69 ms, and zero packet loss. Jitter of 5.27 ms and a standard deviation of 6.78 ms keep the path in the fair latency tier.
At 1.86 times the 100.2 ms fiber-floor estimate for the 10,232 km separation, the measured average translates to 53.7% fiber efficiency. The spread is about 3.6% of the average, which sits close to the 3.28% median variability seen across the 19 routes in this round.
Ranked 16th of those 19, the route's absolute RTT is the main constraint; its loss-free, moderately jittered profile suggests a stable path whose cost is distance rather than erratic behavior.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 186.5 ms |
| Jitter | 5.27 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 100.2 ms |
| Fiber Efficiency | 53.7% |
| Latency Tier | Fair |
| Source Region | Europe |
| Destination Region | South America |
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: BER → GRU
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 186.5 ± 0.96 ms (SE)
Sample distribution: box = interquartile range (181.2–189.7 ms), median 183.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 (100.2 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 201.32 |
| 2 | 100 | 187.32 |
| 3 | 200 | 181.30 |
| 4 | 300 | 179.21 |
| 5 | 400 | 179.20 |
| 6 | 500 | 179.46 |
| 7 | 600 | 206.69 |
| 8 | 700 | 189.30 |
| 9 | 800 | 195.35 |
| 10 | 900 | 198.67 |
| 11 | 1000 | 197.00 |
| 12 | 1100 | 189.68 |
| 13 | 1200 | 182.94 |
| 14 | 1300 | 188.52 |
| 15 | 1400 | 182.87 |
| 16 | 1500 | 182.93 |
| 17 | 1600 | 180.49 |
| 18 | 1700 | 179.83 |
| 19 | 1800 | 198.23 |
| 20 | 1900 | 189.58 |
| 21 | 2000 | 189.01 |
| 22 | 2100 | 190.05 |
| 23 | 2200 | 187.46 |
| 24 | 2300 | 193.86 |
| 25 | 2400 | 186.51 |
| 26 | 2500 | 191.88 |
| 27 | 2600 | 183.47 |
| 28 | 2700 | 180.28 |
| 29 | 2800 | 181.71 |
| 30 | 2900 | 181.48 |
| 31 | 3000 | 182.20 |
| 32 | 3100 | 181.67 |
| 33 | 3200 | 179.39 |
| 34 | 3300 | 180.52 |
| 35 | 3400 | 190.21 |
| 36 | 3500 | 186.90 |
| 37 | 3600 | 182.00 |
| 38 | 3700 | 182.72 |
| 39 | 3800 | 179.96 |
| 40 | 3900 | 188.83 |
| 41 | 4000 | 202.05 |
| 42 | 4100 | 188.25 |
| 43 | 4200 | 190.47 |
| 44 | 4300 | 182.36 |
| 45 | 4400 | 181.12 |
| 46 | 4500 | 180.01 |
| 47 | 4600 | 180.10 |
| 48 | 4700 | 181.09 |
| 49 | 4800 | 187.61 |
| 50 | 4900 | 181.94 |
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.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Berlin (52.52437, 13.41053) and São Paulo (-23.54750, -46.63611). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 10,232.3 km |
| Vacuum RTT floor | 68.26 ms |
| Standard fiber RTT floor () | 100.2 ms |
| Low-latency fiber material floor | 99.8 ms |
| Engineering floor (5% path allowance) | 105.23 ms |
| Research 1.33× mapped-fiber reference | 133.27 ms |
| Estimated unamplified path loss | 2148.8 dB |
| Transparent optical spans / inline amplifiers | 135 / 134 |
| Published RTT inflation over fiber floor | 1.86× |
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-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 179.2 ms |
| Average RTT | 186.5 ms |
| Maximum RTT | 206.69 ms |
| Standard deviation | 6.78 ms |
| Stdev / average | 3.6% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 186.5 ms
- Minimum
- 184.5 ms
- Maximum
- 188.5 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Berlin (BER)
- Destination PoP: São Paulo (GRU)
- Region overview: Europe → South America
- Corridor overview: Europe to South America
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- São Paulo to Berlin latency and RTT — 191.3 ms
Fastest routes departing Berlin (BER)
- Berlin to Frankfurt latency and RTT — 6.1 ms
- Berlin to Amsterdam latency and RTT — 7.2 ms
- Berlin to London latency and RTT — 15.2 ms
- Berlin to Paris latency and RTT — 15.6 ms
- Berlin to Marseille latency and RTT — 20.2 ms
Fastest routes arriving at São Paulo (GRU)
- Ashburn to São Paulo latency and RTT — 101.4 ms
- New York to São Paulo latency and RTT — 106.9 ms
- Miami to São Paulo latency and RTT — 128.7 ms
- Los Angeles to São Paulo latency and RTT — 131.3 ms
- Seattle to São Paulo latency and RTT — 155.7 ms
Same corridor (Europe → South America)
- London to São Paulo latency and RTT — 170.7 ms
- Amsterdam to São Paulo latency and RTT — 175.5 ms
- Paris to São Paulo latency and RTT — 175.8 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/ber-gru.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0".
Data auto-generated on August 16, 2026. Explore the full interactive latency matrix or browse more city-pair routes.