Suzy Outage History

Suzy is up right now

Suzy had 7 outages in the last 2 years totaling 15h 51m of downtime, averaging 0.3 incidents per month.

There were 7 Suzy outages since March 18, 2025 totaling 15h 51m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.suzy.com

Minor June 23, 2026

Chat services experience elevated error rates

Detected by Pingoru
Jun 23, 2026, 03:07 PM UTC
Resolved
Jun 23, 2026, 05:25 PM UTC
Duration
2h 18m
Affected: Classic Suzy
Timeline · 3 updates
  1. monitoring Jun 23, 2026, 03:07 PM UTC

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

  2. monitoring Jun 23, 2026, 03:07 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved Jun 23, 2026, 05:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 11, 2026

Delayed study fielding and response collection

Detected by Pingoru
May 11, 2026, 05:00 AM UTC
Resolved
May 11, 2026, 05:00 AM UTC
Duration
–
Timeline · 1 update
  1. resolved Jul 02, 2026, 09:38 PM UTC

    Between May 11 and May 26, 2026, a subset of studies experienced delayed fielding and slower-than-normal response collection. Affected customers may have seen studies require multiple launch attempts, response counts lag behind expected sample, or dashboard totals not match. No respondent data was lost. Every response that was received was preserved and has since been processed, and all studies are fielding and reporting normally.

Read the full incident report →

Minor November 18, 2025

Cloudflare Outage impacting Suzy services.

Detected by Pingoru
Nov 18, 2025, 01:19 PM UTC
Resolved
Nov 18, 2025, 03:24 PM UTC
Duration
2h 5m
Affected: Classic Suzy
Timeline · 2 updates
  1. investigating Nov 18, 2025, 06:59 PM UTC

    Cloudflare is experiencing an internal service degradation. Some services may be intermittently impacted. We are focused on restoring service

  2. resolved Nov 18, 2025, 06:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 14, 2025

Azure - VM Outage

Detected by Pingoru
Aug 14, 2025, 02:37 AM UTC
Resolved
Aug 14, 2025, 03:44 AM UTC
Duration
1h 7m
Affected: Classic Suzy
Timeline · 3 updates
  1. investigating Aug 14, 2025, 03:07 AM UTC

    We are currently investigating this issue.

  2. identified Aug 14, 2025, 03:33 AM UTC

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

  3. resolved Aug 14, 2025, 03:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 28, 2025

Suzy Global - Service Outage

Detected by Pingoru
Apr 28, 2025, 10:48 PM UTC
Resolved
Apr 28, 2025, 11:06 PM UTC
Duration
18m
Timeline · 2 updates
  1. investigating Apr 28, 2025, 10:48 PM UTC

    We are experiencing an outage with Suzy Global and the source is being investigated

  2. resolved Apr 28, 2025, 11:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 24, 2025

Degraded Performance

Detected by Pingoru
Apr 24, 2025, 07:24 PM UTC
Resolved
Apr 25, 2025, 03:59 AM UTC
Duration
8h 35m
Affected: Classic Suzy
Timeline · 2 updates
  1. identified Apr 24, 2025, 07:24 PM UTC

    Microsoft is having an issue with a node failure on our instance, they are investigating and working with their product team to resolve. We are experiencing intermittent latency on our metrics but no errors or platform outage at this time.

  2. resolved Apr 25, 2025, 03:59 AM UTC

    We have resolved the Azure triggered performance issue. Metrics show the platform is healthy.

Read the full incident report →

Minor March 18, 2025

Azure platform outage impacting Suzy platform

Detected by Pingoru
Mar 18, 2025, 11:57 PM UTC
Resolved
Mar 19, 2025, 01:24 AM UTC
Duration
1h 27m
Affected: Classic Suzy
Timeline · 5 updates
  1. investigating Mar 19, 2025, 01:05 AM UTC

    We are currently investigating this issue.

  2. identified Mar 19, 2025, 01:06 AM UTC

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

  3. monitoring Mar 19, 2025, 01:06 AM UTC

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

  4. monitoring Mar 19, 2025, 01:22 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Mar 19, 2025, 01:24 AM UTC

    This incident has been resolved.

Read the full incident report →