Catalyst Outage History

Catalyst is up right now

Catalyst had 2 outages in the last 2 years totaling 21h 53m of downtime — averaging 0.1 incidents per month.

There were 2 Catalyst outages since October 20, 2025 totaling 21h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getcatalyst.io

Notice October 27, 2025

Salesforce-Synced Field Data Incident

Detected by Pingoru
Oct 27, 2025, 07:10 PM UTC
Resolved
Oct 27, 2025, 10:55 PM UTC
Duration
3h 45m
Affected: Website
Timeline · 2 updates
  1. identified Oct 27, 2025, 07:10 PM UTC

    We are currently investigating an issue affecting synced Salesforce fields with decimals. While there is no data loss for these fields, the issue is affecting the display of those field values for all customers. Our team has identified the cause and is implementing a fix now.

  2. resolved Oct 27, 2025, 10:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

Current Incident: Global Vendor Outage Impacting Integrations

Detected by Pingoru
Oct 20, 2025, 08:05 PM UTC
Resolved
Oct 21, 2025, 02:14 PM UTC
Duration
18h 8m
Affected: Website
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 08:05 PM UTC

    Issue: AWS is currently experiencing a global service disruption impacting multiple regions and cloud-based applications worldwide. As a result, all Catalyst integrations may experience interruption or delay. Impact: - Syncing delays between Catalyst and integrated systems (including Salesforce and others) - Trend modules may not display the most up-to-date data - Playbooks may not trigger or run as expected Our engineering team is actively monitoring the situation and will restore full functionality as soon as AWS services stabilize. Once the AWS disruption is resolved, we fully expect all integrations and Catalyst functionality to automatically restore without additional customer action. Thank you for your patience and understanding.

  2. resolved Oct 21, 2025, 02:14 PM UTC

    This incident has been resolved.

Read the full incident report →