Resolved after 42 minutes, affecting Australia and New Zealand and 1 more, on October 18, 2025.
# Incident Report: Temporary Outage on October 18, 2025 **Date:** Saturday, October 18, 2025 **Duration:** Around 40 minutes \(10:08 PM – 10:48 PM NZDT\) **Status:** ✅ Resolved – All systems are now fully operational ## What Happened On the evening of **October 18**, an unexpected issue during our deployment process caused a **temporary outage** across Rocketspark websites and Design Studio systems. Our monitoring systems alerted us immediately, and our engineers began investigating. We discovered that a **third-party deployment provider** had mistakenly reactivated an **old, pending deployment**. This unexpected event rolled back parts of our system to an outdated version, causing widespread disruption. ## How We Responded Our on-call engineers quickly identified the cause and worked through multiple redeployments to restore the correct version of our system. By **10:48 PM NZDT**, all websites and services were back up and running normally. We also contacted our deployment provider, who confirmed that their system fault had triggered this incident and assured us that steps are being taken to prevent it from happening again. ## What We’re Doing to Prevent This We’re taking several steps to ensure this kind of incident does not re-occur: * **Reviewing our deployment process** to prevent any outdated deployments from being queued or triggered in the future. * **Exploring infrastructure changes** to reduce reliance on external tools for critical production deployments. Our goal is to make sure that Rocketspark websites remain **stable, reliable, and always online**, even when unexpected things happen. ## Final Thoughts We sincerely apologise for the disruption this caused — especially given the timing outside normal business hours. We understand how important uptime is for your business and your customers, and we take that responsibility seriously. Thank you for your understanding and continued trust in Rocketspark. — **Richard King** Co-founder & Chief Technical Officer [Rocketspark.com](https://www.rocketspark.com)
Affected components
Update timeline
- investigating Oct 18, 2025, 09:34 AM UTC
We are currently investigating a reported outage across a number of systems, we will be updating this status shortly.
- resolved Oct 18, 2025, 10:17 AM UTC
All systems are now fully operational. We apologise for the inconvenience caused by an unexpected issue during our deployment process, which temporarily affected several systems. Our team is investigating the root cause to ensure this does not happen again in the future.
- postmortem Oct 18, 2025, 10:21 PM UTC
# Incident Report: Temporary Outage on October 18, 2025 **Date:** Saturday, October 18, 2025 **Duration:** Around 40 minutes \(10:08 PM – 10:48 PM NZDT\) **Status:** ✅ Resolved – All systems are now fully operational ## What Happened On the evening of **October 18**, an unexpected issue during our deployment process caused a **temporary outage** across Rocketspark websites and Design Studio systems. Our monitoring systems alerted us immediately, and our engineers began investigating. We discovered that a **third-party deployment provider** had mistakenly reactivated an **old, pending deployment**. This unexpected event rolled back parts of our system to an outdated version, causing widespread disruption. ## How We Responded Our on-call engineers quickly identified the cause and worked through multiple redeployments to restore the correct version of our system. By **10:48 PM NZDT**, all websites and services were back up and running normally. We also contacted our deployment provider, who confirmed that their system fault had triggered this incident and assured us that steps are being taken to prevent it from happening again. ## What We’re Doing to Prevent This We’re taking several steps to ensure this kind of incident does not re-occur: * **Reviewing our deployment process** to prevent any outdated deployments from being queued or triggered in the future. * **Exploring infrastructure changes** to reduce reliance on external tools for critical production deployments. Our goal is to make sure that Rocketspark websites remain **stable, reliable, and always online**, even when unexpected things happen. ## Final Thoughts We sincerely apologise for the disruption this caused — especially given the timing outside normal business hours. We understand how important uptime is for your business and your customers, and we take that responsibility seriously. Thank you for your understanding and continued trust in Rocketspark. — **Richard King** Co-founder & Chief Technical Officer [Rocketspark.com](https://www.rocketspark.com)
Your product runs on more than Rocketspark
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services