Squiz Outage History

Squiz is up right now

There were 3 Squiz outages since February 20, 2026 totaling 14h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.squiz.cloud

Minor March 12, 2026

Unable to access Advanced Forms in the Squiz DXP

Detected by Pingoru
Mar 12, 2026, 11:50 PM UTC
Resolved
Mar 13, 2026, 01:03 AM UTC
Duration
1h 13m
Affected: Squiz SaaS Hosted Instances
Timeline · 4 updates
  1. investigating Mar 12, 2026, 11:50 PM UTC

    Customers are currently experiencing issues with accessing Advanced Forms in the DXP via the Console. Users attempting to access the service are observing HTTP502 errors and/or login forms. The incident team is currently investigating the cause.

  2. identified Mar 13, 2026, 12:15 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 13, 2026, 12:42 AM UTC

    A fix has been implemented and we have started to observe recovery. We are monitoring the roll out of the recovery and will confirm that operations are returned to normal once the process has completed.

  4. resolved Mar 13, 2026, 01:03 AM UTC

    The incident has been resolved and Advanced Forms access should be restored for all customers.

Read the full incident report →

Minor March 4, 2026

Connect Ordinary Flows (US Region)

Detected by Pingoru
Mar 04, 2026, 03:52 PM UTC
Resolved
Mar 04, 2026, 10:57 PM UTC
Duration
7h 5m
Affected: Squiz Cloud Hosted Instances
Timeline · 13 updates
  1. investigating Mar 04, 2026, 03:52 PM UTC

    We are currently investigating an issue affecting Connect Ordinary Flows on our US instance. Due to a service disruption with our upstream cloud provider in the US East (Ashburn) region, new containers are currently unable to launch. Please note that all incoming messages are being securely held in our queues. No data is being lost, and processing will resume automatically once the connection is restored. Our engineering team is working closely with the provider to expedite a resolution. We will provide further updates as more information becomes available.

  2. investigating Mar 04, 2026, 04:25 PM UTC

    We are continuing to work with the provider on full resolution for all affected services. We will provide updates as they become available.

  3. investigating Mar 04, 2026, 04:55 PM UTC

    We are continuing to work with the provider for a resolution. We will provide updates as they become available.

  4. investigating Mar 04, 2026, 05:30 PM UTC

    We are continuing to work with the provider on full resolution for all affected services. We will provide updates as they become available.

  5. identified Mar 04, 2026, 05:57 PM UTC

    We are seeing partial restoration at this time and are monitoring closely.

  6. monitoring Mar 04, 2026, 06:36 PM UTC

    Ordinary Flows are beginning to operate now. We continue to monitor the progress closely while working to full resolution.

  7. monitoring Mar 04, 2026, 07:03 PM UTC

    Our engineering team continues to monitor and work with the provider for resolution. We will continue to provide updates as more information becomes available.

  8. monitoring Mar 04, 2026, 07:33 PM UTC

    We are continuing the monitoring, but seeing better results. We will provide further updates as more information becomes available.

  9. monitoring Mar 04, 2026, 08:00 PM UTC

    We are continuing the monitoring, but seeing better results. We will provide further updates as more information becomes available.

  10. monitoring Mar 04, 2026, 08:30 PM UTC

    We are continuing the monitoring, but seeing better results. We will provide further updates as more information becomes available.

  11. monitoring Mar 04, 2026, 09:33 PM UTC

    We are continuing to work with our provider for full resolution. We will provide further updates as more information becomes available.

  12. monitoring Mar 04, 2026, 10:30 PM UTC

    Our vendor has indicated that the platform should now be fully operational. We will continue to monitor to confirm resolution, and provide updates as more details become available.

  13. resolved Mar 04, 2026, 10:57 PM UTC

    Squiz teams have worked with our 3rd party service provider, and a fix has been deployed for the current Incident. This restored service for all affected customers. We apologise for this degradation of service and thank you for your patience while we worked on the resolution. A postmortem will be provided via https://status.squiz.cloud once we have worked with our service provider.

Read the full incident report →

Critical February 20, 2026

Service degradation

Detected by Pingoru
Feb 20, 2026, 06:09 PM UTC
Resolved
Feb 21, 2026, 12:00 AM UTC
Duration
5h 50m
Affected: Squiz SaaS Hosted Instances
Timeline · 19 updates
  1. investigating Feb 20, 2026, 06:09 PM UTC

    We are currently investigating an issue impacting all our services. Initial diagnostics suggest a widespread disruption with Cloudflare, our content delivery provider. Our team is monitoring the situation closely and will provide updates as they become available.

  2. identified Feb 20, 2026, 06:29 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 20, 2026, 06:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. investigating Feb 20, 2026, 06:37 PM UTC

    We are investigating additional issues for all affected clients. We will provide further updates as they become available.

  5. identified Feb 20, 2026, 07:03 PM UTC

    We are working with Cloudflare regarding connectivity issues. The Cloudflare status page can be found here: https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt

  6. identified Feb 20, 2026, 07:24 PM UTC

    We continue to work with Cloudflare regarding the ongoing issues. We will provide further updates as they become available.

  7. identified Feb 20, 2026, 07:53 PM UTC

    We are continuing to work on full resolution with Cloudflare. We will provide further updates as they become available.

  8. identified Feb 20, 2026, 08:15 PM UTC

    We are continuing to work with our content delivery provider for full resolution. We will provide updates as they become available.

  9. identified Feb 20, 2026, 08:45 PM UTC

    We are continuing to work on full resolution and will provide updates as they become available.

  10. identified Feb 20, 2026, 09:17 PM UTC

    We are continuing to work with Cloudflare on full resolution for all affected services. We will provide updates as they become available.

  11. identified Feb 20, 2026, 09:22 PM UTC

    We are continuing to work with Cloudflare on full resolution for all affected services. We will provide updates as they become available.

  12. identified Feb 20, 2026, 09:54 PM UTC

    We are continuing to work with Cloudflare on full resolution for all affected services. We will provide updates as they become available.

  13. identified Feb 20, 2026, 10:05 PM UTC

    We are seeing recovery of services at this time and we are monitoring the situation to ensure things remain stable.

  14. monitoring Feb 20, 2026, 10:05 PM UTC

    We are seeing recovery of services at this time and we are monitoring the situation to ensure things remain stable.

  15. monitoring Feb 20, 2026, 10:33 PM UTC

    We are seeing recovery of services at this time and we are continuing to monitoring the situation to ensure all services remain stable.

  16. monitoring Feb 20, 2026, 11:02 PM UTC

    We are still monitoring this situation at large as well as investigating a handful of remaining intermittent issues. We will provide additional updates as available.

  17. monitoring Feb 20, 2026, 11:30 PM UTC

    We are still seeing recovery of services at this time and we are continuing to monitoring the situation to ensure all services remain stable.

  18. resolved Feb 21, 2026, 12:00 AM UTC

    This incident has been resolved.

  19. postmortem Feb 23, 2026, 03:54 AM UTC

    **Executive Summary** On Friday, February 20, 2026, at 1748 UTC, a global Cloudflare incident impacted network routing used to deliver traffic to services hosted on the Squiz DXP platform. During this time: * All DXP users, and Squiz cloud customers using Cloudflare, were unable to log in to any administrative interfaces in the Squiz DXP, including the Console, Content Management System \(Matrix\), and Funnelback. * Customer frontend websites using Cloudflare were returning cloudflare errors “Connection timed Out” This issue was caused by a change that Cloudflare made to how our network manages IP addresses. Cloudflare have provided a detailed analysis of the incident at [https://blog.cloudflare.com/cloudflare-outage-february-20-2026/](https://blog.cloudflare.com/cloudflare-outage-february-20-2026/) Restoration of the cloudflare service for individual customers ranged from between 30 mins to 3.5 hours depending on the IP configurations for each customer. If you require more information specific to your solution please log a ticket via the My.Squiz portal requesting a Custom Post Incident Report. Squiz would like to remind customers to subscribe to the Squiz Status page at [status.squiz.net](http://status.squiz.net) to receive real time notification of Major Incidents. **References** * Cloudflare incident Page: [https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt](https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt) * Cloudflare incident Blog: [https://blog.cloudflare.com/cloudflare-outage-february-20-2026/](https://blog.cloudflare.com/cloudflare-outage-february-20-2026/) * Squiz Status Page: [https://status.squiz.cloud/](https://status.squiz.cloud/) **Timeline: 20 Feb \(UTC\)** * Incident start time: 1749 UTC * Squiz Incident declaration: 1800 UTC * Initial Squiz Status Page notifications posted: 1809 UTC * Cloudflare reported full resolution for anycast customers: 2053 UTC * Cloudflare reported full resolution for spectrum customers: 2259 UTC * Cloudflare marked the incident resolved on at 23:50 UTC * Squiz Declared Incident resolved: 0000 21 Feb UTC

Read the full incident report →

Looking to track Squiz downtime and outages?

Pingoru polls Squiz's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Squiz reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Squiz alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Squiz for free

5 free monitors · No credit card required