Summary

  • APNIC scheduled three hours of Brisbane network maintenance across 15 public status components, with possible interruptions of up to five minutes.
  • Its status-page configuration excludes maintenance from uptime calculations, so the displayed percentage does not establish whether users saw interruptions.

The notice sets a ceiling, not a result

APNIC published its service notice on 13 October. It scheduled critical security updates to network devices at its Brisbane data-centre locations for 06:00–09:00 UTC+10 on Thursday 15 October, a three-hour window. The notice says listed services may be interrupted for up to five minutes. That is a forecast, not a measured outage duration.

The notice names 11 service groups: MyAPNIC Member Portal, registry-api.apnic.net, APNIC Website, APNIC Academy, APNIC Blog, Orbit, FTP, RPKI Services, DASH, REx and Whois Oceania. APNIC’s public status page maps the work to 15 components, including separate RPKI repository, RRDP, AS0, publication-protocol and RSC-verifier entries. The wider list matters because a single maintenance label can cover dependencies with different functions.

The uptime column answers a narrower question

At 09:16 UTC+10, sixteen minutes after the announced end, the status page still listed the event under “Upcoming Maintenance”. Its incident history said no incidents had been reported for 14 October, and the component rows displayed 100% in the Uptime column. Those lines do not establish that every listed service remained continuously available: planned work and unplanned incidents are recorded separately.

The public page’s configuration exposes ignore_maintenance_for_uptime_calculation: true and show_status_history_uptime: true. Site24x7’s StatusIQ API reference documents that setting; its help material explains that maintenance periods can be excluded from downtime and availability calculations. The page also limits displayed status and incident history to two days. Read together, the 100% figure is not an event-specific receipt for the three-hour window.

In the sources checked, APNIC had not yet published a per-component account of actual interruption times, service restoration or whether any user-facing interruption occurred. The public evidence supports the planned work and its possible five-minute ceiling, not an assertion that the ceiling was reached—or that impact was zero.

Sources: APNIC’s 15 October service notice; APNIC Services Status; Site24x7 StatusIQ API reference; Site24x7’s uptime-calculation guidance. APNIC service updates; Site24x7 guidance on excluding scheduled maintenance from availability SLA reports.