Changes / Optimizely / Netspring outage

Optimizely: Major incident: Netspring outage

Summary

Optimizely Analytics (Netspring) experienced a major outage affecting Netspring customers only, starting 2026-08-03 02:30 UTC and resolved at 2026-08-03 16:04 UTC, lasting 13 h 33 min. Optimizely reported identifying the underlying cause without disclosing details and confirmed service was restored to normal operation.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: Netspring outage
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-08-03 02:30 UTC
AddedResolved time#5
Before: not present
After: 2026-08-03 16:04 UTC
AddedAffected components#6
Before: not present
After: Optimizely Analytics (Netspring)
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating an issue affecting our Netspring service (Netspring customers only). We will continue to provide timely updates as they become available.
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate the issue. Thank you for your patience!
AddedUpdateidentified#9
Before: not present
After: We have identified the underlying cause of the issue affecting the Netspring service and are actively working toward resolution. We will continue to provide timely updates on our progress as they become available.
AddedUpdateresolved#10
Before: not present
After: The issue affecting the Netspring service has been resolved, and service has been restored to normal operation.

First version of this incident archived by Rewindex. View the live incident.

History of this incident

When (UTC)ChangeKind
Major incident: Netspring outage (this change)
Optimizely Analytics (Netspring) experienced a major outage affecting Netspring customers only, starting 2026-08-03 02:30 UTC and resolved at 2026-08-03 16:04 UTC, lasting 13 h 33 min. Optimizely reported identifying the underlying cause without disclosing details and confirmed service was restored to normal operation.
Major incident

All Optimizely changes → · Optimizely profile · Markdown · JSON