Daily ISP report

Thursday 30 July 2026

Telstra — UNI-D1 on nbn FTTP

Midnight to midnight, Australia/Perth · Browse all reports

Packet loss0.0581%6,026 of 10,367,989 packets
Data coverage100%0 endpoint-minutes with gaps
Endpoints won0 / 12Lowest average latency
Avg latency rank2.00Across all endpoints
Incidents1,099Loss 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 2.8ms 10.2ms 161.7ms 7.5ms 23.7ms 30.3ms 6.93ms 0.0295% 100%
Sydney 49.1ms 59.7ms 152.8ms 60.4ms 72.0ms 76.7ms 7.08ms 0.0249% 100%
Singapore 283.6ms 294.7ms 387.8ms 294.1ms 307.7ms 312.2ms 7.39ms 0.0611% 100%
Seoul 188.7ms 199.5ms 444.4ms 199.1ms 212.1ms 221.6ms 6.73ms 0.053% 100%
Tokyo 163.7ms 173.6ms 411.0ms 173.3ms 187.3ms 192.6ms 7.29ms 0.0287% 100%
Los Angeles 189.6ms 198.3ms 291.9ms 196.3ms 211.8ms 217.1ms 7.28ms 0.0296% 100%
Chicago 240.9ms 263.0ms 355.9ms 262.6ms 276.7ms 282.4ms 7.09ms 0.1682% 100%
Paris 323.6ms 333.8ms 532.2ms 332.0ms 348.7ms 353.7ms 7.27ms 0.0037% 100%
Frankfurt 329.9ms 340.8ms 614.0ms 340.2ms 351.5ms 357.9ms 6.98ms 0.1488% 100%
Amsterdam 327.0ms 348.0ms 989.3ms 348.5ms 360.3ms 361.8ms 6.97ms 0.0811% 100%
London 321.0ms 329.4ms 569.9ms 328.1ms 340.8ms 348.4ms 7.07ms 0.0354% 100%
Stockholm 341.3ms 352.7ms 555.4ms 350.5ms 367.5ms 374.1ms 7.00ms 0.0333% 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
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
01:28 – 01:30 Chicago 2 min 1,070 89.167% —
01:28 – 01:30 Frankfurt 2 min 709 59.083% —
20:54 – 20:56 Amsterdam 2 min 321 26.75% —
07:47 – 07:49 Frankfurt 2 min 259 21.583% —
19:25 – 19:28 Amsterdam 3 min 214 11.889% —
15:42 – 15:44 Frankfurt 2 min 157 13.083% —
02:17 – 02:19 Seoul 2 min 154 12.823% —
02:17 – 02:19 Sydney 2 min 153 12.75% —
02:17 – 02:19 Tokyo 2 min 153 12.75% —
02:17 – 02:19 Perth 2 min 152 12.667% —
02:17 – 02:19 Chicago 2 min 152 12.667% —
20:54 – 20:56 London 2 min 147 12.25% —
Over the day

Latency by endpoint

Perth
051014
Telstra
Sydney
0244872
Telstra
Singapore
0111221332
Telstra
Seoul
078156235
Telstra
Tokyo
070141211
Telstra
Los Angeles
076152228
Telstra
Chicago
0103207310
Telstra
Paris
0129259388
Telstra
Frankfurt
0129257386
Telstra
Amsterdam
0131262393
Telstra
London
0124249373
Telstra
Stockholm
0137273410
Telstra

← Back to the ISP comparison for this day

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-07-31T00:17:07+08:00. The complete underlying dataset for this report is published as JSON.