Is Quick NZ down?

Last checked 5m ago
Current status
Quick NZ is up

No incidents right now.

Official status page: https://status.quic.nz · Polled every 5 minutes · 4 components tracked

Quick NZ is operational right now. Last checked 5m ago; the most recent incident resolved 3d ago.

Real-time Quick NZ status, recent outages, and incident history — pulled directly from Quick NZ's official status page at https://status.quic.nz every 5 minutes. Pingoru tracks 4 Quick NZ services and has captured 14 incidents in the last 90 days (97.50% uptime). Get email, Slack, Discord, or webhook alerts the moment Quick NZ reports a new incident — free for 5 monitors, no credit card.

Users who monitor Quick NZ also follow these Telecom services: Optus SMS iQmetrix TPG Telecom Dubber Vimla Simbase gaiia software Helium Mobile Tuatahi First Fibre Glink View all 6,000+ providers
Quick NZ uptime 97.50% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 19m
    Started Jun 30, 2026, 04:19 AM UTC · Resolved Jun 30, 2026, 04:39 AM UTC
    UFB Internet
    Timeline · 3 updates
    • investigating · Jun 30, 2026, 04:19 AM UTC

      Some customers may be experiencing an interruption or degradation of connectivity. Our team are investigating.

    • monitoring · Jun 30, 2026, 04:23 AM UTC

      Affected connectivity has been restored, or is restoring. The team are continuing their investigations.

    • resolved · Jun 30, 2026, 04:39 AM UTC

      Engineers have identified the cause of this disruption to a firmware bug. Maintenance is being planned to complete updates on two network elements and will be posted on our status page once confirmed. We apologise for any inconvenience caused.

    Latest: Engineers have identified the cause of this disruption to a firmware bug. Maintenance is being planned to complete updates on two network elements and will be posted on our status …

  2. Resolved 17m
    Started Jun 25, 2026, 03:24 AM UTC · Resolved Jun 25, 2026, 03:41 AM UTC
    Cloud Servers
    Timeline · 3 updates
    • identified · Jun 25, 2026, 03:24 AM UTC

      We have been alerted to a process lockup on network element pe2-akl1, causing potential interruption to service or suboptimal routing for customers connected via this device. Engineers have concluded a restart of the device is necessary, which may cause a brief interruption to directly connected and singlehomed equipment for approximately 5-10 minutes. We apologise for the inconvenience, and will post updates once completed and restored to normal operation.

    • monitoring · Jun 25, 2026, 03:33 AM UTC

      Device restart has been completed and engineers are monitoring to ensure service restoration.

    • resolved · Jun 25, 2026, 03:41 AM UTC

      Network element and associated services have remained stable since manual intervention. If you are experiencing issues with your service, please reach out to our team for further assistance.

    Latest: Network element and associated services have remained stable since manual intervention. If you are experiencing issues with your service, please reach out to our team for further a…

  3. Resolved 41m
    Started May 27, 2026, 02:24 PM UTC · Resolved May 27, 2026, 03:05 PM UTC
    UFB InternetCloud Servers
    Timeline · 3 updates
    • investigating · May 27, 2026, 02:24 PM UTC

      Some customers may be experiencing degraded international connectivity. Our team are investigating and updates to follow.

    • monitoring · May 27, 2026, 02:48 PM UTC

      Issue has been isolated to an upstream transit path, which has now been temporarily removed from our network. Affected destinations, seemingly Europe-specific are now functioning.

    • resolved · May 27, 2026, 03:05 PM UTC

      Issue has been confirmed as major congestion within a single transit providers network. This provider has been temporarily removed from our network and traffic re-routed, which has resolved affected traffic destinations. We apologise for any inconvenience.

    Latest: Issue has been confirmed as major congestion within a single transit providers network. This provider has been temporarily removed from our network and traffic re-routed, which has…

  4. Resolved 28m
    Started May 13, 2026, 01:36 AM UTC · Resolved May 13, 2026, 02:05 AM UTC
    UFB Internet
    Timeline · 3 updates
    • identified · May 13, 2026, 01:36 AM UTC

      We are experiencing an issue impacting some customers with Chorus connections authenticating onto the Vetta network. The team are investigating and resolving as quickly as possible.

    • monitoring · May 13, 2026, 01:38 AM UTC

      Rollback has been performed from a change and impacted connections are recovering. The team are monitoring to ensure resolution.

    • resolved · May 13, 2026, 02:05 AM UTC

      Incident has been resolved. If you are without connectivity, please reach out to our team. This incident was caused by an erroneous setting pushed into our authentication backend, which resulted in some service disruption for some customers, which will be investigated to analyse the root cause. We apologise for any inconvenience caused.

    Latest: Incident has been resolved. If you are without connectivity, please reach out to our team. This incident was caused by an erroneous setting pushed into our authentication backend, …

  5. Resolved 1d 20h
    Started May 10, 2026, 02:49 AM UTC · Resolved May 11, 2026, 10:55 PM UTC
    UFB InternetCloud Servers
    Timeline · 13 updates
    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    Latest: 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 throug…

Outage history

Past 90 days · 5 incidents View full outage history →