CaptivateIQ experienced a major incident on October 20, 2025 affecting Workbooks & Commission Plans and Data & Connections and 1 more component, lasting 11h 45m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 20, 2025, 09:30 AM UTC
We are currently investigating this issue.
- investigating Oct 20, 2025, 09:31 AM UTC
We are continuing to investigate this issue.
- identified Oct 20, 2025, 09:34 AM UTC
CaptivateIQ is experiencing widespread service disruptions as a result of a large outage at our hosting provider. We are working to restore service currently
- identified Oct 20, 2025, 10:44 AM UTC
Our hosting provider is recovering and we are continuing to restore the system. Overall performance is still impacted as we work to provision capacity.
- identified Oct 20, 2025, 01:00 PM UTC
We continue to work though capacity issues resulting from our hosting providers outage.
- identified Oct 20, 2025, 04:13 PM UTC
We continue to work though issues resulting from our hosting providers outage and will provide an additional update as soon as one is available.
- identified Oct 20, 2025, 05:32 PM UTC
We are seeing some early signs of service recovery within Amazon Web Services (AWS). Some CaptivateIQ systems remain degraded, and we’re continuing to monitor the system and ensure that we achieve a full recovery.
- identified Oct 20, 2025, 06:36 PM UTC
CaptivateIQ services are continuing to recover. Customers are advised to delay critical processing tasks until we've finished mitigating the effects of today's issues.
- identified Oct 20, 2025, 08:04 PM UTC
We are seeing services continuing to recover within Amazon Web Services (AWS). Some CaptivateIQ systems remain degraded, and we’re continuing to monitor the system and ensure that we achieve a full recovery.
- monitoring Oct 20, 2025, 09:11 PM UTC
We're seeing customer processing returning to normal and are monitoring the system to ensure the system remains stable.
- resolved Oct 20, 2025, 10:04 PM UTC
This incident has been resolved.