Rocketspark incident

Investigating a reported outage on New Zealand

Critical Resolved View vendor source →

Rocketspark experienced a critical incident on May 6, 2026 affecting New Zealand, lasting 1h 30m. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 09:26 AM UTC
Resolved
May 06, 2026, 10:56 AM UTC
Duration
1h 30m
Detected by Pingoru
May 06, 2026, 09:26 AM UTC

Affected components

New Zealand

Update timeline

  1. investigating May 06, 2026, 09:26 AM UTC

    We are currently investigating a reported outage on our system, we will be updating this status shortly.

  2. investigating May 06, 2026, 09:52 AM UTC

    We are still investigating the outage and working through this with our hosting provider.

  3. investigating May 06, 2026, 10:13 AM UTC

    Our technicians are still working through restoring services in New Zealand.

  4. monitoring May 06, 2026, 10:52 AM UTC

    Websites are responding again and we are investigating further.

  5. resolved May 06, 2026, 10:56 AM UTC

    This incident has been resolved.

  6. postmortem May 06, 2026, 11:08 AM UTC

    # Service Incident Postmortem – May 6, 2026 On the evening of May 6, 2026, Rocketspark experienced a significant service outage affecting customer websites hosted in New Zealand and the Rocketspark Studio partner portal. Email services and Google Workspace were not affected. We sincerely apologise for the disruption this caused. ## What Happened As part of planned maintenance, we were carrying out important system and security updates intended to keep our platform secure and reliable. Unfortunately, the updates did not go to plan and resulted in an unexpected outage affecting customer websites hosted in New Zealand and the Rocketspark Studio partner portal. The outage began at approximately **9:10pm NZST**. Our monitoring systems alerted our team immediately, and the issue was escalated internally. We also engaged our hosting and infrastructure providers to assist with recovery efforts. After working through the issue with our providers, most systems were back online around **10:34pm NZST** while we continued stabilising services and monitoring the platform. **No customer data lost** during this incident. ## Timeline * **9:10pm NZST** — Outage begins during planned maintenance * **9:26pm NZST** — Initial public status update posted * **9:52pm NZST** — Investigation ongoing with hosting provider * **10:13pm NZST** — Recovery work continuing * **10:34pm NZST** — Most systems restored while monitoring and stabilisation continued * **10:56pm NZST** — Incident resolved ## What We’re Doing Next We take incidents like this very seriously. Following this outage, we will be conducting a full internal review of: * Our maintenance procedures * System architecture and recovery processes * Deployment and rollback safeguards * Monitoring and escalation procedures Our goal is to reduce the likelihood of an incident like this occurring again and to improve recovery times should issues arise in the future. We appreciate your patience and understanding while we worked to restore services.