Quick NZ incident

Incident - Network Degradation - 10/05

Minor Resolved View vendor source →

Quick NZ experienced a minor incident on May 10, 2026 affecting UFB Internet and Cloud Servers, lasting 1d 20h. The incident has been resolved; the full update timeline is below.

Started
May 10, 2026, 02:49 AM UTC
Resolved
May 11, 2026, 10:55 PM UTC
Duration
1d 20h
Detected by Pingoru
May 10, 2026, 02:49 AM UTC

Affected components

UFB InternetCloud Servers

Update timeline

  1. investigating May 10, 2026, 02:49 AM UTC

    The team are currently investigating instability/degradation on the network. Investigations are underway and updates to follow.

  2. investigating May 10, 2026, 03:13 AM UTC

    The team are continuing to investigate. Investigations thus far are indicating this could be a large attack against our network. Updates to follow.

  3. investigating May 10, 2026, 03:37 AM UTC

    The team are continuing to work through this incident as quickly as possible. We apologise for the inconvenience caused, and will provide updates as they become available.

  4. identified May 10, 2026, 04:08 AM UTC

    This incident has been confirmed as a very large distributed attack against our network. We have limited international connectivity of our network as an immediate response, which has improved domestic connectivity, while we work with upstream partners on further mitigation steps. Updates to follow.

  5. identified May 10, 2026, 04:38 AM UTC

    Restoration of internal network elements and domestic connectivity is continuing successfully. International connectivity remains limited. Updates to follow. Thank you for your patience while our team deal with this large-scale attack.

  6. identified May 10, 2026, 05:15 AM UTC

    Domestic, trans-tasman and internal network connectivity remains normal. The team are working through interrupted internal systems for impacted compute workloads. Network attack is still continuing, and international connectivity remains limited while further mitigations are implemented or levels subside. We apologise for any inconvenience caused.

  7. identified May 10, 2026, 05:50 AM UTC

    Domestic, trans-tasman and internal network connectivity remains operational. IPv6 traffic may subject to increased impact as opposed to IPv4. Impacted internal compute workloads have been restored. Network attack is still continuing, and international connectivity remains limited while further mitigations are implemented or levels subside. We apologise for the inconvenience caused.

  8. identified May 10, 2026, 07:02 AM UTC

    Further works have been conducted in joint efforts with our upstream international transit providers to further mitigate against attacks, and international connectivity is no longer as heavily disrupted as earlier. Domestic, trans-tasman and internal network connectivity remains operational. IPv6 traffic may subject to increased impact as opposed to IPv4. International connectivity remains limitedc while further analysis continues. We apologise for the inconvenience caused.

  9. monitoring May 10, 2026, 08:41 AM UTC

    Further defences have been implemented in joint efforts with our upstream international transit providers to further mitigate against attacks, and international connectivity is at near-normal performance levels. Domestic, trans-tasman and internal network connectivity remains operational. International connectivity remains limited, however is now at near-normal performance levels. Incident is now moving to a monitoring state with our response team. We apologise for the inconvenience caused while we worked through this immediate incident response of this large-scale distributed attack today.

  10. monitoring May 10, 2026, 08:01 PM UTC

    The team have continued to mitigate this attack through the night, with customer services remaining stable and functional. Following on from our last update yesterday evening, there should be no significant impact to connectivity or services in this current state. Our team continue to monitor and adjust defences while this attack still continues.

  11. monitoring May 11, 2026, 05:02 AM UTC

    Incident remains under monitoring. Attacks have continued and defence mitigations have been functioning as expected, resulting in no significant customer impact. Our team continue to monitor and adjust defences while this attack still continues. Next update tomorrow morning unless there is a change to network status.

  12. monitoring May 11, 2026, 08:13 PM UTC

    Attacks appear to have subsided. Our team is monitoring closely. Next update on status change or to move through to resolution.

  13. resolved May 11, 2026, 10:55 PM UTC

    This incident has been resolved. The large-scale distributed attack against our network has subsided, and all services are operating normally. We thank you for your patience throughout this incident, and apologise for any inconvenience caused.