Wyng Outage History

Wyng is up right now

Pingoru has recorded 53 incidents for Wyng: 12 in the last 12 months and 0 in the last 90 days.

Source: status.wyng.com

53incidents recorded
12last 12 months
0last 90 days
10 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Wyng in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 2026225 of 744 (3%)
June 2026310 of 720 (1%)
July 2026115 of 744 (2%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 511 (0%)

Incidents, newest first

Minor July 2, 2026 Delays in processing data streams 14h 42m Salesforce Marketing Cloud Integration, MailChimp Integration, Oracle Responsys Integration, Webhook Integration

Started Jul 02, 2026, 08:00 AM UTC· resolved Jul 02, 2026, 10:42 PM UTC

  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 3h 43m Instagram Content Stream

Started Jun 12, 2026, 04:52 PM UTC· resolved Jun 12, 2026, 08:36 PM UTC

  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 2h 44m Login, Metrics, Experience Management, Content Management and 1 more

Started Jun 12, 2026, 02:00 PM UTC· resolved Jun 12, 2026, 04:45 PM UTC

  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 3h 35m Login, Metrics, Experience Management, Content Management and 1 more

Started Jun 05, 2026, 02:45 PM UTC· resolved Jun 05, 2026, 06:21 PM UTC

  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 3m Salesforce Marketing Cloud Integration, MailChimp Integration, Oracle Responsys Integration, Webhook Integration

Started May 08, 2026, 12:55 PM UTC· resolved May 08, 2026, 12:59 PM UTC

  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 →

Major October 20, 2025 Disruption to integrations, content streams, metrics, and experiences with custom domains 19h 31m AWS ec2-us-east-1, Salesforce Marketing Cloud Integration, Experiences, Metrics and 5 more

Started Oct 20, 2025, 01:41 PM UTC· resolved Oct 21, 2025, 09:12 AM UTC

  1. identified Oct 20, 2025, 01:41 PM UTC

    There is a disruption affecting some Wyng customers and services. The root cause is an Amazon Web Services outage. Currently the following Wyng components and features are delayed or not working: * Experience Metrics * Weekly performance reports sent by email * Content Streams * Integrations and Webhooks * Identity Resolution by Email and SMS * Experiences with Custom Domains AWS indicates that impacted services are in process of being restored. AWS Service health can be found here: https://health.aws.amazon.com/health/status

  2. identified Oct 20, 2025, 01:55 PM UTC

    We have updated the status of some components. We will post another update in 60 minutes.

  3. identified Oct 20, 2025, 03:39 PM UTC

    Amazon Web Services continues to work on resolving the outage, and we continue to track updates and monitor for recovery. Here is the latest update from AWS, posted at 11:04 AM U.S. Eastern time: "[08:04 AM PDT] We continue to investigate the root cause for the network connectivity issues that are impacting AWS services such as DynamoDB, SQS, and Amazon Connect in the US-EAST-1 Region. We have identified that the issue originated from within the EC2 internal network. We continue to investigate and identify mitigations.".

  4. monitoring Oct 20, 2025, 04:56 PM UTC

    Amazon Web Services continues to work on full resolution, but at this time, all Wyng services are operational or recovering. Integrations and web hooks are operating normally, and all queued transactions have been processed. Weekly reports have been delivered. We continue to monitor. Here is the latest update from AWS, posted at 12:13 PM U.S. Eastern time: "[09:13 AM PDT] We have taken additional mitigation steps to aid the recovery of the underlying internal subsystem responsible for monitoring the health of our network load balancers and are now seeing connectivity and API recovery for AWS services. We have also identified and are applying next steps to mitigate throttling of new EC2 instance launches. We will provide an update by 10:00 AM PDT."

  5. monitoring Oct 20, 2025, 07:48 PM UTC

    Amazon Web Services continues to work to resolve the outage, and we are continuing to monitor. We have identified a new, related issue, which is that users editing experiences cannot view or edit sections with formatted text content. This is due to the AWS outage impacting a third-party vendor whose formatted text editor component we use. While this issue is outstanding, we recommend users hold off on editing and publishing changes to experiences that use formatted text content. Formatted text will continue to display normally in any experiences that are already live. Here is the latest update from AWS, posted at 3:15 PM U.S. Eastern time: "[12:15 PM PDT] We continue to observe recovery across all AWS services, and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions. For Lambda, customers may face intermittent function errors for functions making network requests to other services or systems as we work to address residual network connectivity issues. To recover Lambda’s invocation errors, we slowed down the rate of SQS polling via Lambda Event Source Mappings. We are now increasing the rate of SQS polling as we experience more successful invocations and reduced function errors. We will provide another update by 1:00 PM PDT."

  6. monitoring Oct 20, 2025, 10:13 PM UTC

    At this time all Wyng applications and services are operating normally. Amazon Web Services continues to work on full resolution of the root cause incident, which remains open as of the last update, at 5:48 PM U.S. Eastern Time. We are continuing to monitor.

  7. resolved Oct 21, 2025, 09:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2025 Degraded performance of content management features 2h 15m

Started Jun 10, 2025, 07:53 AM UTC· resolved Jun 10, 2025, 10:08 AM UTC

  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 18h 36m Metrics

Started Feb 28, 2025, 02:00 AM UTC· resolved Feb 28, 2025, 08:36 PM UTC

  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 3h 37m Metrics

Started Feb 04, 2025, 02:31 PM UTC· resolved Feb 04, 2025, 06:09 PM UTC

  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 1d 9h Instagram Content Stream

Started Dec 09, 2024, 02:01 PM UTC· resolved Dec 10, 2024, 11:45 PM UTC

  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 3h 3m Experiences, Experience Management

Started Nov 18, 2024, 02:06 PM UTC· resolved Nov 18, 2024, 05:09 PM UTC

  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 2h 44m Content Management

Started Nov 14, 2024, 07:10 PM UTC· resolved Nov 14, 2024, 09:54 PM UTC

  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 8h 8m Salesforce Marketing Cloud Integration, MailChimp Integration, Oracle Responsys Integration, Webhook Integration

Started Oct 25, 2024, 12:01 AM UTC· resolved Oct 25, 2024, 08:10 AM UTC

  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 2h 11m Login, Experiences

Started Oct 23, 2024, 05:35 PM UTC· resolved Oct 23, 2024, 07:47 PM UTC

  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 →