Vorco NZ Outage History
Vorco NZ is up right nowPingoru has recorded 51 incidents for Vorco NZ: 6 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 1 | 1 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 2 | 4 of 744 (1%) |
| August 2026 | 1 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 10 of 518 (2%) |
Incidents, newest first
Major October 13, 2026 Unplanned Event - Tuatahi Taranaki 10h 25m Internet & WAN Access
Started Oct 13, 2026, 02:16 PM UTC· resolved Oct 14, 2026, 12:42 AM UTC
- 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.
- 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.
- resolved Oct 14, 2026, 12:42 AM UTC
This incident has been resolved.
Major August 9, 2026 Unplanned event - akl4-tr1 drop 15m
Started Aug 09, 2026, 03:30 AM UTC· resolved Aug 09, 2026, 03:45 AM UTC
- resolved Aug 09, 2026, 03:58 AM UTC
We are aware of an issue on AKL4-TR1 between 15:45 and 15:50 which resulted in multiple customers losing internet access, and are investigating the cause. Routes are reconverging now and we expect service to be restored soon.
- postmortem Aug 09, 2026, 04:45 AM UTC
## Summary On 09/08/2026, customers connected via our AKL4-TR1 network edge experienced a brief loss of connectivity due to an unplanned interface reset. All affected interfaces automatically recovered and network routing fully reconverged within 8 minutes. ## Impact Customers connected via AKL4-TR1 would have experienced intermittent packet loss, dropped sessions, or unavailability of services routed through this router. Impact was limited to the incident window of 15:45-15:53. Service has been fully restored and stable since. ## Timeline \(all times in NZT\) | Time | Event | | --- | --- | | 15:45 | Router health-monitor triggered a fault condition, causing all interfaces to drop and reinsert | | 15:45–15:52 | Interfaces began rediscovery and recovery | | 15:52 | All interfaces reported back up | | 15:53 | Network routing fully reconverged | ## Root Cause The router's internal health-monitoring subsystem triggered a software defect that led to reset of all network interfaces. The device's self-healing mechanisms restored the interfaces and routing state without requiring manual intervention. We're continuing to investigate the underlying trigger internally. Specific hardware/vendor diagnostic details are not included in this public summary. ## Resolution The affected router automatically recovered without engineer intervention. Our monitoring systems detected the event in real time, and our team confirmed full restoration of service by 15:53. ## Remediation & Next Steps We are reviewing logs and diagnostic data to identify the underlying trigger. We apologise for any disruption this caused. If you continue to experience issues, please contact [email protected].
Major July 6, 2026 Unplanned Event - Reoccurrence of akl2-bng2 issue 2h 31m Internet & WAN Access
Started Jul 06, 2026, 10:02 PM UTC· resolved Jul 07, 2026, 12:33 AM UTC
- 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.
- monitoring Jul 06, 2026, 10:11 PM UTC
We have restarted akl2-bng2 and sessions have returned to normal.
- 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.
Major July 3, 2026 Unplanned Event - akl2-bng2 issue and emergency reboot 1h 49m Internet & WAN Access
Started Jul 03, 2026, 03:05 AM UTC· resolved Jul 03, 2026, 04:55 AM UTC
- 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.
- 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.
Major May 2, 2026 Unplanned Event - Backhaul Outage 1h 11m Core Network, Internet & WAN Access
Started May 02, 2026, 09:08 AM UTC· resolved May 02, 2026, 10:19 AM UTC
- 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.
- 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.
- 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.
Notice February 20, 2026 Unplanned Event - Chorus outage in West Auckland 22h 45m
Started Feb 20, 2026, 08:06 PM UTC· resolved Feb 21, 2026, 06:51 PM UTC
- 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.
- 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.
- 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.
- 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.
- 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.
Minor October 13, 2025 Unplanned Event - Issues reaching certain websites 4h 23m Internet & WAN Access
Started Oct 13, 2025, 11:45 AM UTC· resolved Oct 13, 2025, 04:09 PM UTC
- 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.
- 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.
Major September 17, 2025 Unplanned Event - Backend database unavailable 51m Core Network, Billing System, Internet & WAN Access
Started Sep 17, 2025, 05:02 PM UTC· resolved Sep 17, 2025, 05:54 PM UTC
- 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.
- 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.
- 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.
- 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.
Minor May 20, 2025 Unplanned Event - SkyPhone Standard 3h 15m SkyPhone Standard, Calling for Teams
Started May 20, 2025, 09:30 PM UTC· resolved May 21, 2025, 12:46 AM UTC
- 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.
- 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.
- 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.
- 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.
Minor March 3, 2025 Unplanned Event - Inbound calls to Teams Auto Attendants and Call Queues ring but do not connect 3h 12m Calling for Teams
Started Mar 03, 2025, 06:11 PM UTC· resolved Mar 03, 2025, 09:24 PM UTC
- 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.
- 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.
- 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.
- monitoring Mar 03, 2025, 08:24 PM UTC
We are starting to see incoming calls to Auto Attendants and Call Queues succeed again.
- resolved Mar 03, 2025, 09:24 PM UTC
Microsoft have updated their incident to advise that TM1022107 is fully restored.
Major February 24, 2025 Connectivity issues 14m Core Network, Internet & WAN Access
Started Feb 24, 2025, 01:52 AM UTC· resolved Feb 24, 2025, 02:07 AM UTC
- 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.
- identified Feb 24, 2025, 02:07 AM UTC
We've identified the cause and are taking steps to mitigate
- 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.