Daily ISP report

Friday 25 September 2026

Superloop — UNI-D1 on nbn FTTP

Midnight to midnight, Australia/Perth · Browse all reports

Packet loss0.056%6,286 of 11,231,986 packets
Data coverage100%0 endpoint-minutes with gaps
Endpoints won0 / 13Lowest average latency
Avg latency rank2.46Across all endpoints
Incidents860Loss or coverage events
Counter resets0Agent restarts excluded from loss
By endpoint

Latency and packet loss, past 24 hours

Min, average and max are the headline numbers. The percentiles sit beside them because a single spike moves an average — p95 means 95% of packets were faster than this.

EndpointMinAvgMax p50p95p99Jitter LossCoverage
Perth best 1.5ms 3.4ms 289.5ms 2.2ms 2.8ms 41.5ms 1.12ms 0.0045% 100%
Sydney 47.3ms 49.3ms 333.9ms 48.0ms 48.6ms 87.6ms 1.12ms 0.0174% 100%
Singapore 195.9ms 197.9ms 483.6ms 196.6ms 197.3ms 236.8ms 1.13ms 0.0108% 100%
Seoul best 188.3ms 209.1ms 478.2ms 189.2ms 361.1ms 361.7ms 1.19ms 0.0617% 100%
Tokyo 146.4ms 148.3ms 433.4ms 147.0ms 147.6ms 186.6ms 1.12ms 0.0053% 100%
Los Angeles 215.2ms 217.1ms 631.3ms 215.8ms 216.7ms 256.5ms 1.17ms 0.038% 100%
Chicago 256.4ms 258.4ms 543.8ms 257.1ms 258.2ms 296.9ms 1.13ms 0.0181% 100%
Paris 270.3ms 272.3ms 558.6ms 271.0ms 271.6ms 311.2ms 1.14ms 0.0244% 100%
Frankfurt 269.6ms 271.7ms 556.1ms 270.4ms 271.4ms 310.8ms 1.14ms 0.1256% 100%
Amsterdam 268.8ms 279.6ms 994.0ms 270.2ms 357.7ms 358.3ms 1.17ms 0.1214% 100%
London 266.5ms 270.5ms 553.2ms 267.9ms 277.7ms 309.2ms 1.15ms 0.1973% 100%
Stockholm 306.0ms 317.7ms 595.0ms 308.4ms 395.4ms 396.0ms 1.12ms 0.0998% 100%
Sydney2 47.6ms 49.5ms 335.7ms 48.2ms 48.9ms 87.8ms 1.13ms 0.0034% 100%
Loss timeline

24 hours, five minutes per cell

No loss< 0.01%0.01 – 0.1%0.1 – 1%> 1%No data
Perth
Sydney
Singapore
Seoul
Tokyo
Los Angeles
Chicago
Paris
Frankfurt
Amsterdam
London
Stockholm
Sydney2
00:0006:0012:0018:0024:00
Incidents

Worst events of the day

Consecutive minutes with packet loss or missing data, ranked by packets lost.

WindowEndpointDuration Packets lostLossCoverage
09:49 – 10:03 London 14 min 461 5.488% —
01:31 – 01:33 Frankfurt 2 min 367 30.583% —
02:27 – 02:29 Seoul 2 min 319 26.583% —
19:35 – 19:36 Los Angeles 1 min 295 49.167% —
00:49 – 00:58 Amsterdam 9 min 231 4.277% —
03:47 – 03:55 Amsterdam 8 min 220 4.583% —
14:50 – 15:01 London 11 min 219 3.318% —
03:47 – 03:55 London 8 min 209 4.354% —
03:47 – 03:55 Stockholm 8 min 207 4.313% —
10:47 – 10:54 London 7 min 187 4.452% —
18:16 – 18:22 Frankfurt 6 min 182 5.056% —
15:52 – 15:58 London 6 min 153 4.25% —
Over the day

Latency by endpoint

Perth
0134
Superloop
Sydney
0193756
Superloop
Singapore
074148222
Superloop
Seoul
0135271406
Superloop
Tokyo
055111166
Superloop
Los Angeles
081162244
Superloop
Chicago
097194291
Superloop
Paris
0103206309
Superloop
Frankfurt
0102205307
Superloop
Amsterdam
0134268402
Superloop
London
0104209313
Superloop
Stockholm
0148296445
Superloop
Sydney2
0193756
Superloop
Methodology

How these numbers were produced

Every ISP in this report is measured on identical hardware, with an identical probe configuration, through the same nbn FTTP NTD at the same premises, over the same time window. Each ISP terminates on its own UNI-D port.

  • ProbeUDP to port 1337, 10 packets per second per endpoint, 1000ms timeout.
  • BucketCounters aggregated in 60-second buckets.
  • LossPacket loss is the sum of reset-safe counter deltas. Buckets where a counter decreases are treated as an agent restart and excluded rather than counted as loss.
  • CoverageCoverage is delivered samples divided by expected samples. Missing data is reported as a gap, never as zero loss.
  • Percentilesp50/p95/p99 are computed over the full day of samples, not averaged from buckets. Approximate (t-digest) quantiles.
  • TimeoutsA sample with latency <= 0 or null is a timeout.
  • RankingEndpoints are ranked ordinally. No weighted composite score is used.
  • Ingest delay75s ingest settling delay applied before a day is generated.

Scope. This is a single-premises measurement against one nbn point of interconnect. It reflects each ISP’s backhaul, peering and congestion as experienced at this location on this date. It is not a nationwide comparison, and results at other locations may differ. All four UNI-D ports share the same physical fibre and GPON access path, so access-network conditions affect every ISP equally and cancel out of the comparison.

Generated 2026-09-26T00:16:06+08:00. The complete underlying dataset for this report is published as JSON.