Wyng logo

Is Wyng Down?

SaaSLive status, outages, and incident history

No. Wyng is up right now.

Every monitored Wyng system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · 60s while moving

Know the moment Wyng breaks

Wyng is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

How we know: the official Wyng status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Wyng Component Status

The main Wyng systems on this page. All 32 are operational right now.

32operational
APIs » Content API
Operational
APIs » Profiles API
Operational
Corporate Website
Operational

29 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Experiences, Integrations » MailChimp Integration, Integrations » Oracle Responsys Integration, Integrations » Salesforce Marketing Cloud Integration, Integrations » Webhook Integration, Platform » Content Management, Platform » Experience Management, Platform » Login, Platform » Metrics, Platform » Profiles Management, Platform » Support Center, Social Content Streams » Instagram Content Stream, and 17 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Wyng Outages & Incidents

Incident history from the official Wyng status page, including resolution updates.

Delays in processing data streamsResolved Jul 2, 2026 · 14h 42mResolved

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. --- [2026-07-02T18:42:28.476-04:00] (resolved) Delays have been resolved for all impacted clients. --- [2026-07-03T01:10:55.561-04:00] (monitoring) 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. [UPDATE 08:30 AM EDT] We have taken steps to address the issue and processing delay for impacted clients is recovering now.

Wyng Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Wyng incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 3 days with incidentsSep 25

Live Wyng Outage Reports

Problems reported by engineers using Wyng. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Wyng problems reported yet.

Something wrong with Wyng on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Wyng

Wyng publishes a public status page at status.wyng.com covering 37 components, including Login, AWS ec2-us-east-1 and Content API. PulsAPI tracks Wyng outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Wyng uptime at 100.00%. Response times, incident history, and SLA tracking for Wyng are available on the PulsAPI dashboard.

Wyng Status FAQ

Is Wyng down right now?

The verdict at the top of this page comes from the latest poll of the official Wyng status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Wyng is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Wyng recovers.

How do I check Wyng uptime history?

PulsAPI tracks Wyng uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Wyng changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Wyng outages?

PulsAPI reads the official Wyng status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Wyng components?

Yes. PulsAPI monitors 32 individual Wyng components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Wyng goes down?

Yes. Create a free account and subscribe to Wyng: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Wyng to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Wyng problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Wyng?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Wyng plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Wyng with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services