Wyng Outage History

Wyng is up right now

Wyng had 11 outages in the last 2 years totaling 91h 40m of downtime — averaging 0.5 incidents per month.

There were 11 Wyng outages since October 13, 2024 totaling 91h 40m 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 →

Minor February 28, 2025

Experience metrics are delayed

Detected by Pingoru
Feb 28, 2025, 02:00 AM UTC
Resolved
Feb 28, 2025, 08:36 PM UTC
Duration
18h 36m
Affected: Metrics
Timeline · 3 updates
  1. identified Feb 28, 2025, 07:02 PM UTC

    Experience metrics are delayed for some users. Historical metrics are still available. Data is being collected and will be updated once the issue is resolved. We have isolated the problem and are working on a fix.

  2. monitoring Feb 28, 2025, 08:31 PM UTC

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

  3. resolved Feb 28, 2025, 08:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 4, 2025

Some customers are unable to access some Experience Metrics

Detected by Pingoru
Feb 04, 2025, 02:31 PM UTC
Resolved
Feb 04, 2025, 06:09 PM UTC
Duration
3h 37m
Affected: Metrics
Timeline · 3 updates
  1. investigating Feb 04, 2025, 02:31 PM UTC

    Some customers are reporting an issue accessing Metrics sub-tabs. The issue is limited to a subset of customers, and does not affect accuracy of metrics or related event processing. Summary metrics continue to work normally. We are currently investigating the issue.

  2. monitoring Feb 04, 2025, 05:50 PM UTC

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

  3. resolved Feb 04, 2025, 06:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 9, 2024

Instagram Content Streams are not collecting new content

Detected by Pingoru
Dec 09, 2024, 02:01 PM UTC
Resolved
Dec 10, 2024, 11:45 PM UTC
Duration
1d 9h
Affected: Instagram Content Stream
Timeline · 4 updates
  1. identified Dec 09, 2024, 02:01 PM UTC

    Instagram Content Streams are not collecting new content due to an issue with our integration to Facebook's API. We are working with Facebook on a resolution.

  2. identified Dec 09, 2024, 02:02 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Dec 10, 2024, 02:34 PM UTC

    We are continuing to work with Facebook on a fix for this issue.

  4. resolved Dec 11, 2024, 01:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2024

Issues with Experiences using reward codes

Detected by Pingoru
Nov 18, 2024, 02:06 PM UTC
Resolved
Nov 18, 2024, 05:09 PM UTC
Duration
3h 3m
Affected: ExperiencesExperience Management
Timeline · 3 updates
  1. investigating Nov 18, 2024, 02:06 PM UTC

    Some users are encountering issues with Experiences using reward codes. Users may be unable to save edits to Experiences with reward codes, or the save action may be slow. Live experiences using code validation or unique code distribution may perform slowly. We are investigating.

  2. monitoring Nov 18, 2024, 03:18 PM UTC

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

  3. resolved Nov 18, 2024, 05:09 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor November 14, 2024

Some users cannot add new content to Brand Content Library

Detected by Pingoru
Nov 14, 2024, 07:10 PM UTC
Resolved
Nov 14, 2024, 09:54 PM UTC
Duration
2h 44m
Affected: Content Management
Timeline · 3 updates
  1. identified Nov 14, 2024, 07:10 PM UTC

    Some users cannot add new content to Brand Content Library. We are aware of the cause and working on a fix. Existing assets hosted in Brand Content Library are not affected.

  2. monitoring Nov 14, 2024, 09:14 PM UTC

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

  3. resolved Nov 14, 2024, 09:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 25, 2024

Some delays in processing outbound integration data flows

Detected by Pingoru
Oct 25, 2024, 12:01 AM UTC
Resolved
Oct 25, 2024, 08:10 AM UTC
Duration
8h 8m
Affected: Salesforce Marketing Cloud IntegrationMailChimp IntegrationOracle Responsys IntegrationWebhook Integration
Timeline · 2 updates
  1. investigating Oct 25, 2024, 12:01 AM UTC

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

  2. resolved Oct 25, 2024, 12:49 PM UTC

    After further analysis, we have determined that integrations are operating normally, and the delays were limited to a customer-specific integration, due to latency of API calls to a specific external system.

Read the full incident report →

Major October 23, 2024

Performance issues with Wyng platform and some experiences

Detected by Pingoru
Oct 23, 2024, 05:35 PM UTC
Resolved
Oct 23, 2024, 07:47 PM UTC
Duration
2h 11m
Affected: LoginExperiences
Timeline · 5 updates
  1. investigating Oct 23, 2024, 06:12 PM UTC

    We are currently investigating an issue causing degraded performance with the Wyng platform and some experiences. Some experiences may display slowly or not display. Platform users may encounter slow login behavior, or require multiple attempts to log in.

  2. identified Oct 23, 2024, 06:32 PM UTC

    The issues have been isolated to specific platform services, and steps are being taken to address. Most experiences should now be loading.

  3. monitoring Oct 23, 2024, 06:37 PM UTC

    After actions taken to restore affected services, all experiences are operating normally. We are continuing to monitor.

  4. monitoring Oct 23, 2024, 06:44 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Oct 23, 2024, 07:47 PM UTC

    The incident was resolved. We have reviewed the root cause and taking action to prevent recurrence.

Read the full incident report →

Major October 13, 2024

Experience SDK issues

Detected by Pingoru
Oct 13, 2024, 12:32 PM UTC
Resolved
Oct 13, 2024, 12:32 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 21, 2024, 07:53 PM UTC

    On October 11 at 2:30 PM EDT, we received reports from some customers about problems with Custom JavaScript code not running properly. At 4:19 PM EDT, we isolated the error to a problem in a recent release of the Wyng platform, and identified an available workaround for affected clients, to set the Wyng Platform version used by their experience to 1.2.165. After further investigation we determined the root cause to be some Experience SDK events were not being generated correctly, the campaign_loaded and page_loaded events. The bug was resolved with a hot-fix released on October 13, at 8:26 AM EDT. After further internal review, we have determined that this incident was avoidable. The error in logic was missed by our quality assurance processes, specifically our automated regression testing system, due to a gap in test coverage. That gap has been corrected, and we do not expect a similar issue to recur.

Read the full incident report →