Squiz experienced a critical incident on October 20, 2025 affecting Squiz SaaS Hosted Instances, lasting 15h 10m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 20, 2025, 07:29 AM UTC
We’re currently experiencing issues when trying to log-in to DXP systems. Our engineers are investigating the issue and will provide updates via the Squiz Status page.
- investigating Oct 20, 2025, 07:29 AM UTC
We are continuing to investigate this issue.
- investigating Oct 20, 2025, 07:45 AM UTC
Our Engineers are continuing to investigate the issue at hand and will provide more details once more is known.
- investigating Oct 20, 2025, 08:06 AM UTC
AWS is currently seeing critical issues, see details here. The following Squiz services are impacted: Global: - DXP Authentication - Static sites served from Filestore US Region only: - Component Service - Page Builder - Conversational Search
- investigating Oct 20, 2025, 08:37 AM UTC
AWS still currently seeing critical issues, see details here: https://health.aws.amazon.com/health/status The following Squiz services are impacted: Global: - DXP Authentication - Static sites served from Filestore - Squiz Support Services - MySquiz/Jira - Squiz Support phone lines - Squiz Status Page US Region only: - Component Service - Page Builder - Conversational Search
- identified Oct 20, 2025, 08:37 AM UTC
The issue has been identified and a fix is being implemented.
- identified Oct 20, 2025, 08:37 AM UTC
We are continuing to work on a fix for this issue.
- identified Oct 20, 2025, 09:26 AM UTC
AWS has applied mitigations and we are starting to see recovery on Squiz services
- monitoring Oct 20, 2025, 09:52 AM UTC
AWS is reporting significant signs of recovery. Squiz is also now seeing recovery on all previously listed services. We will continue to monitor the situation until AWS marks the incident as resolved.
- monitoring Oct 20, 2025, 01:10 PM UTC
Squiz is seeing all of our services as stable and fully recovered. We will however keep this incident open until Amazon declares full recovery. We are continuing to closely monitor the situation
- monitoring Oct 20, 2025, 04:34 PM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 20, 2025, 06:35 PM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 20, 2025, 07:56 PM UTC
AWS is reporting significant signs of recovery but this issue is still on-going. We will continue to monitor the situation until AWS marks the incident as resolved.
- monitoring Oct 20, 2025, 10:28 PM UTC
We are continuing to Monitor for any changes in the status of this issue.
- resolved Oct 20, 2025, 11:16 PM UTC
We have received confirmation from AWS that the incident shall now be resolved. We will continue to monitor for changes and will communicate if a further issue arises. Feel free to let us know at My.Squiz.Net if you believe you are still affected.