Daily ISP report

Friday 9 October 2026

Telstra — UNI-D3 on nbn FTTP

Midnight to midnight, Australia/Perth · Browse all reports

Packet loss0.0321%3,603 of 11,231,988 packets
Data coverage100%0 endpoint-minutes with gaps
Endpoints won0 / 13Lowest average latency
Avg latency rank3.85Across all endpoints
Incidents888Loss 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 5.0ms 12.2ms 107.3ms 8.1ms 25.7ms 32.6ms 7.06ms 0.0056% 100%
Sydney 51.3ms 59.3ms 153.1ms 57.6ms 71.2ms 75.5ms 6.74ms 0.0065% 100%
Singapore 289.6ms 306.8ms 439.7ms 304.5ms 319.8ms 325.3ms 6.65ms 0.0517% 100%
Seoul 192.4ms 201.1ms 425.2ms 200.9ms 212.5ms 219.2ms 6.92ms 0.039% 100%
Tokyo 223.6ms 231.4ms 336.7ms 231.0ms 241.3ms 246.2ms 6.17ms 0.0119% 100%
Los Angeles 196.1ms 214.7ms 307.5ms 213.6ms 227.4ms 233.2ms 7.40ms 0.0378% 100%
Chicago 234.4ms 261.8ms 449.2ms 261.0ms 273.9ms 279.4ms 6.69ms 0.0382% 100%
Paris 325.9ms 335.4ms 482.5ms 335.5ms 348.3ms 353.1ms 7.43ms 0.0362% 100%
Frankfurt 332.5ms 342.1ms 491.6ms 341.0ms 354.8ms 360.6ms 7.25ms 0.0369% 100%
Amsterdam 331.1ms 340.3ms 983.7ms 339.7ms 352.9ms 357.6ms 7.05ms 0.0505% 100%
London 326.3ms 344.5ms 475.8ms 343.8ms 355.9ms 360.4ms 6.72ms 0.0512% 100%
Stockholm 345.2ms 354.2ms 505.1ms 353.4ms 365.6ms 371.1ms 6.67ms 0.0424% 100%
Sydney2 53.8ms 61.1ms 155.8ms 59.4ms 71.8ms 77.1ms 6.14ms 0.0091% 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
14:13 – 14:14 Los Angeles 1 min 265 44.167% —
22:28 – 22:30 London 2 min 194 16.167% —
22:28 – 22:30 Paris 2 min 182 15.167% —
22:28 – 22:30 Amsterdam 2 min 181 15.083% —
22:29 – 22:30 Chicago 1 min 169 28.167% —
22:29 – 22:30 Singapore 1 min 168 28% —
07:13 – 07:15 Singapore 2 min 167 13.917% —
22:28 – 22:30 Frankfurt 2 min 164 13.667% —
22:28 – 22:30 Stockholm 2 min 153 12.75% —
03:03 – 03:04 Amsterdam 1 min 124 20.667% —
03:03 – 03:04 Stockholm 1 min 120 20% —
03:03 – 03:04 London 1 min 109 18.167% —
Over the day

Latency by endpoint

Perth
061117
Telstra
Sydney
0234669
Telstra
Singapore
0116232348
Telstra
Seoul
076153229
Telstra
Tokyo
087174262
Telstra
Los Angeles
081163244
Telstra
Chicago
099197296
Telstra
Paris
0126252379
Telstra
Frankfurt
0129258387
Telstra
Amsterdam
0128257385
Telstra
London
0130259389
Telstra
Stockholm
0133266399
Telstra
Sydney2
0244771
Telstra
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-10T00:16:23+08:00. The complete underlying dataset for this report is published as JSON.