Wyng Outage History

12 incidents recorded over the last 365 days, 12 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Wyng Incident

Wyng incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jul 2, 2026Delays in processing data streamsAn 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…14h 42mResolved
Jun 12, 2026Instagram Content Stream issuesThe 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…3h 43mResolved
Jun 12, 2026Issues impacting login and performance of Wyng dashboardThe incident has been resolved.2h 44mResolved
Jun 5, 2026Issues impacting login and performance of internal Wyng dashboard functionsLogin and all Wyng dashboard functions have recovered are operating normally. We are continuing to monitor.3h 35mResolved
May 8, 2026Delays in processing integration data flowsThis 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.3 minResolved
May 7, 2026Delays in processing integration data flowsThe backlogs in processing integration data flows have been cleared, and processing times have returned to normal. We are continuing to actively monitor.24h 50mResolved
Feb 26, 2026Delays in processing integration data flowsThe backlogs in processing integration data flows have been cleared, and processing times have returned to normal. We are continuing to actively monitor.25h 9mResolved
Feb 25, 2026Delays in processing integration data flowsWe opened a new incident report to track this.13h 19mResolved
Feb 25, 2026Delays in processing integration data flowsThe backlogs in processing integration data flows have been cleared, and processing times have returned to normal. We are continuing to actively monitor.2h 54mResolved
Feb 25, 2026Delays in processing integration data flowsThe backlogs in processing integration data flows have been cleared, and processing times have returned to normal. We are continuing to actively monitor.4h 30mResolved
Feb 2, 2026Delays in processing integration data flowsThe backlogs in processing integration data flows have been cleared, and processing times have returned to normal. We are continuing to actively monitor.2h 59mResolved
Nov 20, 2025Delays in processing integration data flowsThe backlogs in processing integration data flows have been cleared, and processing times have returned to normal. We are continuing to actively monitor.19h 21mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Wyng incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Wyng Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Wyng acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Wyng outage in this window ran 1d 1h, against a mean recovery of 9h 49m. If you depend on Wyng in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.