Wyng Outage History

Wyng is up right now

Wyng had 6 outages in the last 2 years totaling 44h 21m of downtime — averaging 0.2 incidents per month.

There were 6 Wyng outages since October 16, 2025 totaling 44h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.wyng.com

Minor July 2, 2026

Delays in processing data streams

Detected by Pingoru
Jul 02, 2026, 08:00 AM UTC
Resolved
Jul 02, 2026, 10:42 PM UTC
Duration
14h 42m
Affected: Salesforce Marketing Cloud IntegrationMailChimp IntegrationOracle Responsys IntegrationWebhook Integration
Timeline · 3 updates
  1. monitoring Jul 02, 2026, 09:44 PM UTC

    Some clients are experiencing 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 have identified the issue and processing delays for impacted clients is recovering now.

  2. resolved Jul 02, 2026, 10:42 PM UTC

    Delays have been resolved for all impacted clients.

  3. postmortem Jul 03, 2026, 12:16 AM UTC

    An issue with event processing streams caused delays in integration processing affected a subset of Wyng clients. Initial behavior was intermittent, with delays occurring sporadically on July 1, that progressed to a backlog of up to 9 hours of transactions for affected clients starting at about 4:00 AM EDT on July 2. Wyng ops staff took initial action on the issue at 8:30 AM EDT on July 2. By 12:00 EDT the backlog reduced to 2 hours, by 4:20 PM EDT the backlog was 1 hour, and the issue was resolved for all affected clients at 6:38 PM EDT on July 2. The root cause was interdependence between a set of clients whose transactions were being processed in a shared stream. Significant delays in downstream processing by one client caused a backlog across all clients sharing the stream. To avoid recurrence of this failure mode, Wyng is prioritizing a infrastructure update to move from shared to dedicated streams for transaction event processing.

Read the full incident report →

Minor June 12, 2026

Instagram Content Stream issues

Detected by Pingoru
Jun 12, 2026, 04:52 PM UTC
Resolved
Jun 12, 2026, 08:36 PM UTC
Duration
3h 43m
Affected: Instagram Content Stream
Timeline · 3 updates
  1. monitoring Jun 12, 2026, 04:52 PM UTC

    Instagram Content Streams are not collecting new content or experiencing significant delays in collecting new content, due to an outage affecting Meta and Instagram APIs. We are monitoring the situation. All other Wyng content features including UGC moderation, display, and Content API are operating normally.

  2. monitoring Jun 12, 2026, 04:52 PM UTC

    We are continuing to monitor and will update on a change in status.

  3. resolved Jun 12, 2026, 08:36 PM UTC

    The issue affecting Instagram Content Streams has been resolved. New Instagram content is now being collected normally following the restoration of Meta and Instagram API services. We will continue to monitor the services, but no further impact is currently expected.

Read the full incident report →

Minor June 12, 2026

Issues impacting login and performance of Wyng dashboard

Detected by Pingoru
Jun 12, 2026, 02:00 PM UTC
Resolved
Jun 12, 2026, 04:45 PM UTC
Duration
2h 44m
Affected: LoginMetricsExperience ManagementContent ManagementProfiles Management
Timeline · 3 updates
  1. investigating Jun 12, 2026, 02:00 PM UTC

    Some Wyng users are unable to log into the Platform. Additionally some users who are already logged in may encounter delays using Internal Wyng dashboard functions, including editing and publishing experiences. We are investigating. Live experiences are operating normally and not affected.

  2. monitoring Jun 12, 2026, 03:27 PM UTC

    The root cause has been identified and issues are recovering. We are monitoring.

  3. resolved Jun 12, 2026, 04:45 PM UTC

    The incident has been resolved.

Read the full incident report →

Major June 5, 2026

Issues impacting login and performance of internal Wyng dashboard functions

Detected by Pingoru
Jun 05, 2026, 02:45 PM UTC
Resolved
Jun 05, 2026, 06:21 PM UTC
Duration
3h 35m
Affected: LoginMetricsExperience ManagementContent ManagementProfiles Management
Timeline · 3 updates
  1. investigating Jun 05, 2026, 05:32 PM UTC

    Some Wyng users are unable to log into the Platform. Additionally some users who are already logged in may encounter delays or intermittent issues using Internal Wyng dashboard functions, including editing and publishing experiences. We are investigating. Live experiences are operating normally and not affected.

  2. monitoring Jun 05, 2026, 05:56 PM UTC

    Login is being restored for affected users, and degraded performance of some internal Wyng dashboard functions is also recovering, We are continuing to monitor.

  3. resolved Jun 05, 2026, 06:21 PM UTC

    Login and all Wyng dashboard functions have recovered are operating normally. We are continuing to monitor.

Read the full incident report →

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 →