Daily ISP report

Wednesday 16 September 2026

Superloop — UNI-D1 on nbn FTTP

Midnight to midnight, Australia/Perth · Browse all reports

Packet loss0.0943%10,593 of 11,231,988 packets
Data coverage100%0 endpoint-minutes with gaps
Endpoints won0 / 13Lowest average latency
Avg latency rank3.00Across all endpoints
Incidents571Loss 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.5ms 249.4ms 2.2ms 3.2ms 42.3ms 1.19ms 0.0025% 100%
Sydney 47.4ms 49.6ms 316.7ms 48.1ms 53.6ms 88.2ms 1.23ms 0.1334% 100%
Singapore 195.9ms 198.0ms 474.4ms 196.7ms 198.6ms 236.5ms 1.19ms 0.078% 100%
Seoul 178.7ms 187.6ms 434.6ms 188.5ms 190.3ms 228.2ms 1.24ms 0.0329% 100%
Tokyo 146.5ms 148.5ms 406.8ms 147.1ms 149.1ms 187.3ms 1.19ms 0.0336% 100%
Los Angeles 194.4ms 217.3ms 448.0ms 215.9ms 217.9ms 255.8ms 1.21ms 0.0741% 100%
Chicago 235.3ms 258.5ms 1,001.4ms 257.1ms 258.6ms 297.6ms 1.20ms 0.1134% 100%
Paris 342.1ms 344.5ms 601.6ms 342.9ms 353.3ms 383.1ms 1.19ms 0.025% 100%
Frankfurt 339.8ms 342.2ms 833.3ms 340.6ms 345.6ms 380.6ms 1.18ms 0.1344% 100%
Amsterdam 338.1ms 341.5ms 1,002.4ms 339.5ms 345.1ms 380.6ms 1.24ms 0.1196% 100%
London 335.5ms 337.7ms 577.1ms 336.2ms 337.4ms 376.3ms 1.19ms 0.0433% 100%
Stockholm 356.0ms 391.3ms 654.6ms 377.8ms 431.2ms 438.7ms 1.64ms 0.4311% 100%
Sydney2 47.6ms 49.7ms 295.0ms 48.3ms 50.3ms 88.9ms 1.21ms 0.0047% 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
03:32 – 05:14 Stockholm 102 min 1,920 3.137%
15:41 – 15:44 Chicago 3 min 693 38.5%
15:41 – 15:44 Frankfurt 3 min 680 37.778%
15:41 – 15:44 Amsterdam 3 min 667 37.076%
21:16 – 21:25 Sydney 9 min 602 11.148%
11:38 – 11:40 Stockholm 2 min 420 35%
15:41 – 15:44 Singapore 3 min 319 17.722%
11:53 – 11:54 Stockholm 1 min 309 51.5%
15:41 – 15:44 Los Angeles 3 min 298 16.556%
18:03 – 18:05 Los Angeles 2 min 290 24.167%
15:41 – 15:44 Stockholm 3 min 288 15.991%
18:03 – 18:05 Singapore 2 min 247 20.583%
Over the day

Latency by endpoint

Perth
0134
Superloop
Sydney
0224466
Superloop
Singapore
075149224
Superloop
Seoul
071142213
Superloop
Tokyo
056112168
Superloop
Los Angeles
082164245
Superloop
Chicago
097194291
Superloop
Paris
0136272409
Superloop
Frankfurt
0130259389
Superloop
Amsterdam
0129258388
Superloop
London
0126253379
Superloop
Stockholm
0161323484
Superloop
Sydney2
0193857
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-17T00:15:34+08:00. The complete underlying dataset for this report is published as JSON.