Daily ISP report

Monday 5 October 2026

Telstra — UNI-D3 on nbn FTTP

Midnight to midnight, Australia/Perth · Browse all reports

Packet loss0.661%74,249 of 11,231,985 packets
Data coverage100%0 endpoint-minutes with gaps
Endpoints won0 / 13Lowest average latency
Avg latency rank3.69Across all endpoints
Incidents495Loss 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.5ms 107.3ms 9.0ms 25.7ms 32.5ms 7.20ms 0.5924% 100%
Sydney 51.3ms 59.4ms 182.5ms 57.8ms 71.2ms 75.9ms 6.73ms 0.5933% 100%
Singapore 297.5ms 306.8ms 401.3ms 304.8ms 320.5ms 325.6ms 6.75ms 0.6106% 100%
Seoul 186.1ms 194.8ms 313.9ms 193.9ms 208.4ms 212.5ms 7.35ms 0.6072% 100%
Tokyo 223.8ms 231.8ms 326.3ms 231.5ms 241.6ms 246.2ms 6.25ms 0.5949% 100%
Los Angeles 205.5ms 215.3ms 308.8ms 213.9ms 227.5ms 233.2ms 7.27ms 0.5958% 100%
Chicago 253.7ms 261.9ms 816.4ms 261.0ms 274.5ms 280.1ms 6.87ms 0.5998% 100%
Paris 325.8ms 334.8ms 1,002.3ms 334.5ms 347.9ms 352.4ms 7.31ms 0.7419% 100%
Frankfurt 332.4ms 342.3ms 1,008.4ms 341.0ms 354.9ms 360.7ms 7.27ms 0.7742% 100%
Amsterdam 331.4ms 340.7ms 1,021.7ms 339.7ms 352.5ms 357.8ms 6.97ms 0.764% 100%
London 336.2ms 344.7ms 974.8ms 343.8ms 356.0ms 362.1ms 6.74ms 0.7649% 100%
Stockholm 345.7ms 354.5ms 973.4ms 354.1ms 368.3ms 373.1ms 6.67ms 0.7604% 100%
Sydney2 53.8ms 61.0ms 155.4ms 59.0ms 72.4ms 76.6ms 6.26ms 0.5942% 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
07:41 – 07:48 London 7 min 2,678 63.762% —
07:41 – 07:49 Seoul 8 min 2,677 55.771% —
07:41 – 07:49 Tokyo 8 min 2,677 55.771% —
07:41 – 07:49 Frankfurt 8 min 2,677 55.771% —
07:41 – 07:48 Amsterdam 7 min 2,677 63.738% —
07:41 – 07:47 Singapore 6 min 2,676 74.333% —
07:41 – 07:49 Los Angeles 8 min 2,676 55.75% —
07:41 – 07:48 Chicago 7 min 2,676 63.714% —
07:41 – 07:47 Stockholm 6 min 2,676 74.333% —
07:41 – 07:47 Paris 6 min 2,675 74.306% —
07:41 – 07:48 Sydney2 7 min 2,673 63.643% —
07:41 – 07:47 Perth 6 min 2,672 74.222% —
Over the day

Latency by endpoint

Perth
061117
Telstra
Sydney
0234668
Telstra
Singapore
0116232348
Telstra
Seoul
073147220
Telstra
Tokyo
087174262
Telstra
Los Angeles
081162244
Telstra
Chicago
099197296
Telstra
Paris
0126252378
Telstra
Frankfurt
0129258387
Telstra
Amsterdam
0128257385
Telstra
London
0130260389
Telstra
Stockholm
0133267400
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-06T00:16:24+08:00. The complete underlying dataset for this report is published as JSON.