Wyng Outage History

Wyng is up right now

Wyng had 3 outages in the last 2 years totaling 19h 35m of downtime — averaging 0.1 incidents per month.

There were 3 Wyng outages since June 11, 2025 totaling 19h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.wyng.com

Minor May 8, 2026

Delays in processing integration data flows

Detected by Pingoru
May 08, 2026, 12:55 PM UTC
Resolved
May 08, 2026, 12:59 PM UTC
Duration
3m
Affected: Salesforce Marketing Cloud IntegrationMailChimp IntegrationOracle Responsys IntegrationWebhook Integration
Timeline · 3 updates
  1. investigating May 08, 2026, 12:55 PM UTC

    We are seeing delays in processing integration data flows outbound from Wyng to external systems. Users may notice more integration transactions in a Pending state, and longer elapsed times between data collection by an experience and the delivery of that data to their external system or API. Data collection and storage are not impacted, and are operating normally. We are investigating.

  2. resolved May 08, 2026, 12:59 PM UTC

    The backlogs in processing integration data flows have been cleared, and processing times have returned to normal. We are continuing to actively monitor.

  3. postmortem May 08, 2026, 01:04 PM UTC

    This incident was triggered inaccurately, due to outdated events in a log stream, and can be ignored. We are reviewing and taking action to correct similar cases in the future.

Read the full incident report →

Minor June 11, 2025

Degraded performance of content management features

Detected by Pingoru
Jun 11, 2025, 01:53 AM UTC
Resolved
Jun 10, 2025, 07:53 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 11, 2025, 01:53 AM UTC

    Some users reported degraded performance and intermittent failures in content management features. Wyng support became aware of the issue at 07:53 GMT on June 10, and the issue was resolved by manual intervention by our production ops team at 10:08 GMT on June 10.

Read the full incident report →