Vorco NZ Outage History

Vorco NZ is up right now

Vorco NZ had 11 outages in the last 2 years totaling 50h 39m of downtime — averaging 0.5 incidents per month.

There were 11 Vorco NZ outages since February 24, 2025 totaling 50h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.vorco.net

Major October 13, 2026

Unplanned Event - Tuatahi Taranaki

Detected by Pingoru
Oct 13, 2026, 02:16 PM UTC
Resolved
Oct 14, 2026, 12:42 AM UTC
Duration
10h 25m
Affected: Internet & WAN Access
Timeline · 3 updates
  1. identified Oct 13, 2026, 07:28 PM UTC

    Start Time: 0316 Service(s) Affected: Tuatahi fibre connections in Taranaki Customer Impact: Loss of service This is due to backhaul vendor maintenance overnight. We are liaising with our backhaul vendor to resolve this. We apologise for any inconvenience this may cause.

  2. monitoring Oct 13, 2026, 09:40 PM UTC

    Our backhaul vendor has resolved the issue and we are seeing all impacted customers back online. We will be provided with a Reason For Outage (RFO) in due course. Any impacted customers wanting an RFO for this incident should raise a ticket so we can share the RFO when we have it.

  3. resolved Oct 14, 2026, 12:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 6, 2026

Unplanned Event - Reoccurrence of akl2-bng2 issue

Detected by Pingoru
Jul 06, 2026, 10:02 PM UTC
Resolved
Jul 07, 2026, 12:33 AM UTC
Duration
2h 31m
Affected: Internet & WAN Access
Timeline · 3 updates
  1. identified Jul 06, 2026, 10:02 PM UTC

    Start Time: 0930 Service(s) Affected: Northpower, Tuatahi and Enable fibre connections Customer Impact: Customers on Northpower, Tuatahi and Enable fibre connections may be experiencing issues with connectivity. This specifically affects any new sessions only, existing sessions remain working. We will need to restart this BNG which will cause an outage of around 5 minutes to the above services. Our BNG vendor believes they have identified the software bug which is causing this, and we anticipate receiving a patch this week. We apologise for any inconvenience this may cause.

  2. monitoring Jul 06, 2026, 10:11 PM UTC

    We have restarted akl2-bng2 and sessions have returned to normal.

  3. resolved Jul 07, 2026, 12:33 AM UTC

    Reboot has resolved the issue for now. We are going to schedule an automatic reboot between 4am-5am until we have a software patch ready to deploy. This will be followed by a scheduled maintenance notice.

Read the full incident report →

Major July 3, 2026

Unplanned Event - akl2-bng2 issue and emergency reboot

Detected by Pingoru
Jul 03, 2026, 03:05 AM UTC
Resolved
Jul 03, 2026, 04:55 AM UTC
Duration
1h 49m
Affected: Internet & WAN Access
Timeline · 2 updates
  1. identified Jul 03, 2026, 03:05 AM UTC

    Start Time: 1300 (approximate) Service(s) Affected: Northpower, Tuatahi and Enable fibre connections Customer Impact: Customers on Northpower, Tuatahi and Enable fibre connections may be experiencing issues with connectivity. This seems to be specifically affecting any new sessions only, existing sessions are still working. We are gathering troubleshooting information, and then will restart this BNG which will cause an outage of around 5 minutes to the above services. We apologise for any inconvenience this may cause.

  2. resolved Jul 03, 2026, 04:55 AM UTC

    After a reboot, connectivity is restored for the impacted services. The cause appears to be a software bug, which we're working with our vendor to investigate and resolve.

Read the full incident report →

Major May 2, 2026

Unplanned Event - Backhaul Outage

Detected by Pingoru
May 02, 2026, 09:08 AM UTC
Resolved
May 02, 2026, 10:19 AM UTC
Duration
1h 11m
Affected: Core NetworkInternet & WAN Access
Timeline · 3 updates
  1. identified May 02, 2026, 09:08 AM UTC

    Start Time: 2049 Service(s) Affected: Northpower, Tuatahi and Enable fibre services Customer Impact: Loss of connectivity A backhaul vendor has suffered a hardware failure which is impacting links between Auckland and the above fibre networks. We'll update this as soon as we have more details or an ETR. We apologise for any inconvenience this may cause.

  2. monitoring May 02, 2026, 09:53 AM UTC

    The affected router was restored at 2140 and we are seeing impacted customers come back online now. We’ll update this incident once we have clearance notification to confirm full resolution.

  3. resolved May 02, 2026, 10:19 AM UTC

    Full resolution confirmed at 2140. The fault was caused by an issue with the cooling fan card in the router.

Read the full incident report →

Notice February 20, 2026

Unplanned Event - Chorus outage in West Auckland

Detected by Pingoru
Feb 20, 2026, 08:06 PM UTC
Resolved
Feb 21, 2026, 06:51 PM UTC
Duration
22h 45m
Timeline · 5 updates
  1. identified Feb 20, 2026, 08:06 PM UTC

    Start Time: 0522 Service(s) Affected: Internet access Customer Impact: Customers around the Henderson, Kumeu, Massey, Te Atatu, Piha and Waimauku areas may have no internet. This is due to a Chorus fibre cable that has been damaged between Henderson and Massey exchanges. There is no ETA yet for how long the repair will take as it is physical damage. When we have more information or an ETA to repair we will update this incident. We apologise for any inconvenience this may cause.

  2. identified Feb 20, 2026, 11:44 PM UTC

    Latest update from Chorus is that technicians have confirmed 3 damaged cables. Traffic Management and additional fibre jointers have been mobilised. No current ETA. Next update on status change.

  3. identified Feb 21, 2026, 12:51 AM UTC

    Chorus have advised that traffic management and additional fibre technicians are due at the damage site at 2pm today to assist with repairs.

  4. identified Feb 21, 2026, 04:03 AM UTC

    Latest update from Chorus is that duct repairs and replacement cable hauling is taking place. No estimate for repair completion yet.

  5. resolved Feb 21, 2026, 06:51 PM UTC

    Chorus have restored service to all fibre customers. Only some copper services around Kumeu and Waimauku remain impacted. As our customers are all on fibre in these areas we are closing this incident.

Read the full incident report →

Minor October 13, 2025

Unplanned Event - Issues reaching certain websites

Detected by Pingoru
Oct 13, 2025, 11:45 AM UTC
Resolved
Oct 13, 2025, 04:09 PM UTC
Duration
4h 23m
Affected: Internet & WAN Access
Timeline · 2 updates
  1. identified Oct 13, 2025, 03:47 PM UTC

    Start Time: 0045 Service(s) Affected: Internet Access Customer Impact: Some websites, mainly those hosted on Fastly or Akamai CDN providers, are unreachable on IPv4. IPv6 is not affected. This is due to a routing issue at another transit provider upstream from our network. The affected party has confirmed the issue and that they are actively working on it, but we don't have any ETA or more information at this time. We apologise for any inconvenience this may cause.

  2. resolved Oct 13, 2025, 04:09 PM UTC

    We have received confirmation that the routing issue has been fixed which was impacting some CDN content, and our monitoring probes are all returning normal states.

Read the full incident report →

Major September 17, 2025

Unplanned Event - Backend database unavailable

Detected by Pingoru
Sep 17, 2025, 05:02 PM UTC
Resolved
Sep 17, 2025, 05:54 PM UTC
Duration
51m
Affected: Core NetworkBilling SystemInternet & WAN Access
Timeline · 4 updates
  1. identified Sep 17, 2025, 05:02 PM UTC

    Start Time: 0400 Service(s) Affected: Internet Access, Billing/Provisioning Portals Customer Impact: Some customers are offline due to unavailability of backend authentication services. We apologise for any inconvenience this may cause.

  2. identified Sep 17, 2025, 05:22 PM UTC

    We have identified the problem, and are working to resolve it, and hope to have services back to normal within 30 minutes.

  3. identified Sep 17, 2025, 05:43 PM UTC

    Internet access impact is resolved as backend authentication services are available again. We're still working on billing/provisioning portals.

  4. resolved Sep 17, 2025, 05:54 PM UTC

    Billing/provisioning portals are now available again also. All impacted customers with ICMP ping enabled are showing as back online.

Read the full incident report →

Minor May 20, 2025

Unplanned Event - SkyPhone Standard

Detected by Pingoru
May 20, 2025, 09:30 PM UTC
Resolved
May 21, 2025, 12:46 AM UTC
Duration
3h 15m
Affected: SkyPhone StandardCalling for Teams
Timeline · 4 updates
  1. investigating May 20, 2025, 10:49 PM UTC

    Start Time: 0930 Service(s) Affected: SkyPhone Standard Customer Impact: We're seeing instances of one-way audio on calling and are investigating. We apologise for any inconvenience this may cause.

  2. identified May 20, 2025, 11:31 PM UTC

    The issue with one-way audio has been confirmed as being in an upstream network calls traverse through. We are liaising to get a fix or workaround as soon as possible.

  3. monitoring May 21, 2025, 12:09 AM UTC

    A fix has been put in place just before 11:55am to mitigate the issue with one-way audio. If customers are still experiencing issues with one-way audio after 11:55am today, please email the date, time and phone number to support so we can investigate.

  4. resolved May 21, 2025, 12:46 AM UTC

    We believe this is now fully resolved and apologise for the service interruption. We'll be following up with our upstream provider to better understand the cause of this.

Read the full incident report →

Minor March 3, 2025

Unplanned Event - Inbound calls to Teams Auto Attendants and Call Queues ring but do not connect

Detected by Pingoru
Mar 03, 2025, 06:11 PM UTC
Resolved
Mar 03, 2025, 09:24 PM UTC
Duration
3h 12m
Affected: Calling for Teams
Timeline · 5 updates
  1. investigating Mar 03, 2025, 07:26 PM UTC

    Start Time: 0711 Service(s) Affected: Calling for Teams Customer Impact: Inbound calls to Teams ring forever and don't go through. Based on our initial assessment, Vorco is receiving these calls and delivering them to Microsoft Teams, but the Microsoft Teams side is not responding. We're investigating further.

  2. identified Mar 03, 2025, 07:33 PM UTC

    Microsoft have confirmed this is a problem with the Microsoft Teams platform. Follow issue ID TM1022107 at https://admin.microsoft.com/#/servicehealth/:/alerts/TM1022107 for further information.

  3. identified Mar 03, 2025, 07:44 PM UTC

    Microsoft have provided an update advising that a change to the Teams auto attendant code is causing incoming calls to auto attendants and call queues to be refused, and they are in the process of deploying a fix.

  4. monitoring Mar 03, 2025, 08:24 PM UTC

    We are starting to see incoming calls to Auto Attendants and Call Queues succeed again.

  5. resolved Mar 03, 2025, 09:24 PM UTC

    Microsoft have updated their incident to advise that TM1022107 is fully restored.

Read the full incident report →

Major February 24, 2025

Connectivity issues

Detected by Pingoru
Feb 24, 2025, 01:52 AM UTC
Resolved
Feb 24, 2025, 02:07 AM UTC
Duration
14m
Affected: Core NetworkInternet & WAN Access
Timeline · 3 updates
  1. investigating Feb 24, 2025, 02:01 AM UTC

    We're investigating connectivity issues between one of our core sites and will update this as soon as we know more.

  2. identified Feb 24, 2025, 02:07 AM UTC

    We've identified the cause and are taking steps to mitigate

  3. resolved Feb 24, 2025, 02:54 AM UTC

    One of our MPLS PE routers suffered from a network loop, causing that device to become overloaded and drop traffic. As this router also hosts one of our internet transit paths, BGP reconvergence (a hard failover) occurred which disrupted connectivity for a few minutes. After shutting down the offending service, the affected router returned to normal. We'll be investigating how this occurred, and apologise for the service interruption. Impact was from 14:52 local time until 15:06 local time.

Read the full incident report →