Daily ISP report

Tuesday 13 October 2026

Superloop — UNI-D1 on nbn FTTP

Midnight to midnight, Australia/Perth · Browse all reports

Packet loss0.031%3,481 of 11,231,987 packets
Data coverage100%0 endpoint-minutes with gaps
Endpoints won0 / 13Lowest average latency
Avg latency rank2.46Across all endpoints
Incidents815Loss 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 1.6ms 3.6ms 253.9ms 2.3ms 3.0ms 42.5ms 1.10ms 0.0024% 100%
Sydney 47.4ms 49.4ms 321.0ms 48.0ms 48.7ms 88.8ms 1.12ms 0.0013% 100%
Singapore 196.1ms 198.1ms 483.1ms 196.8ms 197.4ms 237.7ms 1.12ms 0.0122% 100%
Seoul 176.9ms 179.0ms 427.9ms 177.6ms 180.2ms 218.2ms 1.18ms 0.0081% 100%
Tokyo 146.4ms 148.3ms 408.5ms 147.0ms 148.1ms 187.5ms 1.16ms 0.0079% 100%
Los Angeles 215.6ms 218.3ms 405.4ms 216.3ms 232.3ms 257.5ms 1.18ms 0.0376% 100%
Chicago 236.3ms 261.1ms 518.1ms 258.3ms 260.1ms 373.3ms 1.10ms 0.0089% 100%
Paris 265.9ms 268.0ms 550.7ms 266.6ms 268.6ms 306.9ms 1.23ms 0.0082% 100%
Frankfurt 269.7ms 294.4ms 578.5ms 291.8ms 294.7ms 406.8ms 1.12ms 0.087% 100%
Amsterdam 269.5ms 294.8ms 684.5ms 291.5ms 299.2ms 406.5ms 1.14ms 0.0509% 100%
London 266.5ms 269.4ms 1,032.8ms 267.5ms 283.7ms 308.1ms 1.13ms 0.0976% 100%
Stockholm 286.5ms 289.8ms 537.0ms 287.4ms 307.7ms 328.4ms 1.11ms 0.0782% 100%
Sydney2 47.6ms 49.6ms 328.2ms 48.3ms 49.0ms 88.9ms 1.12ms 0.0025% 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:32 – 09:39 London 7 min 394 9.381% —
04:58 – 04:59 Los Angeles 1 min 285 47.5% —
22:49 – 22:52 Stockholm 3 min 224 12.444% —
04:02 – 04:04 Amsterdam 2 min 204 17% —
23:49 – 23:51 Frankfurt 2 min 193 16.083% —
03:21 – 03:23 Stockholm 2 min 189 15.75% —
23:54 – 23:56 Frankfurt 2 min 173 14.417% —
04:02 – 04:04 London 2 min 167 13.917% —
07:27 – 07:28 Frankfurt 1 min 127 21.167% —
03:52 – 03:54 London 2 min 115 9.583% —
03:24 – 03:26 Stockholm 2 min 113 9.417% —
23:44 – 23:46 Frankfurt 2 min 85 7.083% —
Over the day

Latency by endpoint

Perth
0134
Superloop
Sydney
0193756
Superloop
Singapore
074148222
Superloop
Seoul
067134201
Superloop
Tokyo
055111166
Superloop
Los Angeles
087174262
Superloop
Chicago
0140280420
Superloop
Paris
0100200300
Superloop
Frankfurt
0152305457
Superloop
Amsterdam
0152305457
Superloop
London
0106213319
Superloop
Stockholm
0115231346
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-10-14T00:16:11+08:00. The complete underlying dataset for this report is published as JSON.