APNIC schedules two Brisbane cutovers for nine services

Two Brisbane Cutovers, the Same Nine APNIC Services

Why it matters

APNIC put its member portal, registry API and seven other services into network-migration windows on 3 and 5 November. Each window lasts two hours; the advertised interruption can reach 15 minutes. The registry has published the schedule, not a service-by-service account of the first cutover.

Daniel Kade3 November 2026 at 17:44 UTCReading Time 2 minLast update: 3 November 2026

APNIC scheduled two Brisbane network-migration windows for the same nine services. Conceptual editorial image, not an APNIC facility photograph.

Summary

APNIC announced Brisbane data-centre network migration for 3 and 5 November 2026, 07:00–09:00 UTC+10 on each date. Both notices name the same nine services and possible interruptions of up to 15 minutes.
The list includes MyAPNIC and registry-api.apnic.net, as well as the website, Academy, Blog, Orbit, DASH, RPKI-rsc-verifier and REx. The two-hour maintenance window is the period of exposure; 15 minutes is APNIC’s stated possible interruption, not a recorded outage.

The 3 November notice and the 5 November notice read like twin bookings for the same network change. APNIC says it is migrating networks at its Brisbane data-centre locations to improve stability and resilience. The first window has passed; the second is set for Thursday. Both are 07:00–09:00 in Brisbane’s UTC+10 time zone. Neither notice reports what actually happened to any service on 3 November.

The exposed inventory is unusually broad for a single maintenance notice. A member trying to use MyAPNIC could meet the change at the login and account surface. An automated customer using registry-api.apnic.net could meet it in a job rather than a browser. The public website, Academy, Blog, Orbit, DASH, RPKI-rsc-verifier and REx complete the nine named entries. APNIC identifies that particular verifier tool; the notice gives no basis for converting it into a claim about the entire RPKI system.

One week earlier, APNIC's 29 October notice booked critical security updates for Brisbane network devices. Its window was also two hours, but its possible interruption was up to five minutes and its list added FTP and Whois Oceania. The next pair is a network migration with a longer stated interruption allowance. The distinction is practical: an operator can avoid scheduling a registry-API task inside either November window, while an analyst cannot infer that every named service actually went dark for 15 minutes.

The notices supply times and names, but no cutover sequence, per-service impact log or completion report. A dated post-change record would show whether the second window finished the job and how much of the advertised interruption budget each service used.