OneCall NZ Outage History

OneCall NZ is up right now

Pingoru has recorded 13 incidents for OneCall NZ: 1 in the last 12 months and 0 in the last 90 days.

Source: status.onecall.net.nz

13incidents recorded
1last 12 months
0last 90 days
58 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking OneCall NZ in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 519 (0%)

Incidents, newest first

Notice April 7, 2026 Loss of phone services 58m Voice

Started Apr 07, 2026, 08:16 PM UTC· resolved Apr 07, 2026, 09:15 PM UTC

  1. investigating Apr 07, 2026, 08:16 PM UTC

    Our phone service provider has reported an outage — we're monitoring the situation and will update as we know more.

  2. monitoring Apr 07, 2026, 08:34 PM UTC

    Update - The issue has been resolved. Our team will keep a close eye on things to make sure everything stays stable. Thank you for your patience!

  3. resolved Apr 07, 2026, 11:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 5, 2025 Partial Outage of Phone and Internet Services 18h 35m Voice, Connectivity

Started Aug 05, 2025, 03:39 AM UTC· resolved Aug 05, 2025, 10:15 PM UTC

  1. investigating Aug 05, 2025, 03:39 AM UTC

    Some customers are experiencing outage with phone and internet systems. This includes these services going offline entirely in some cases. We are awaiting resolution from our upstream service provider.

  2. monitoring Aug 05, 2025, 07:56 PM UTC

    Our service provider has advised services are now online and are monitoring state of services until they are confirmed stable.

  3. resolved Aug 05, 2025, 10:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 14, 2025 Voice Outage 3h 55m Voice

Started Mar 14, 2025, 12:12 AM UTC· resolved Mar 14, 2025, 04:08 AM UTC

  1. investigating Mar 14, 2025, 12:12 AM UTC

    Our upstream provider is experiencing a voice outage, all voice services are impacted, engineers are investigating.

  2. identified Mar 14, 2025, 01:07 AM UTC

    Services are being restored. Registrations and calling may still be impacted while the voice platform is brought back up.

  3. monitoring Mar 14, 2025, 03:02 AM UTC

    Services are now back up and under observation

  4. resolved Mar 14, 2025, 04:08 AM UTC

    Services are now Resolved

Read the full incident report →

Major February 4, 2025 Voice Platform Outage 1d Voice

Started Feb 04, 2025, 05:30 AM UTC· resolved Feb 05, 2025, 06:14 AM UTC

  1. investigating Feb 04, 2025, 05:30 AM UTC

    Our upstream provider is currently experiencing a database outage which is affecting customers on the OneCall Voice Platform. We are working with our upstream provider on restoring services.

  2. investigating Feb 04, 2025, 05:31 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Feb 04, 2025, 06:58 AM UTC

    Monitoring - Services have been restored. We are working with our vendor to understand the cause of the outage.

  4. resolved Feb 05, 2025, 06:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 16, 2024 Phone Outage 13h 59m Voice

Started Dec 16, 2024, 05:29 AM UTC· resolved Dec 16, 2024, 07:28 PM UTC

  1. investigating Dec 16, 2024, 05:29 AM UTC

    There is currently an outage affecting all voice customers, we are working with the vendor to find the cause.

  2. investigating Dec 16, 2024, 05:36 AM UTC

    There is currently an outage affecting all voice customers, we are working with the vendor to find the cause.

  3. monitoring Dec 16, 2024, 06:50 AM UTC

    Phone services are now operational. We are currently working with the vendor to implement a permanent fix.

  4. resolved Dec 16, 2024, 07:28 PM UTC

    This incident has been resolved.

Read the full incident report →