Darwin CX logo

Is Darwin CX Down?

MediaLive status, outages, and incident history

No. Darwin CX is up right now.

Every monitored Darwin CX system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 9m agoLive · every 60s

Know the moment Darwin CX breaks

Darwin CX is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

Official Darwin CX status page
How we know: the official Darwin CX status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Darwin CX Status Summary

As of 14:11 UTC on 14 November 2026, Darwin CX is operational. PulsAPI checked Darwin CX's official status page and found 28 of 28 components operational, with no active incidents. The latest incident, "Darwin services currently unavailable", was on Oct 26, 2026 and lasted 17h 25m.

Cite as: PulsAPI, “Darwin CX status”, checked 14 November 2026, 14:11 UTC. https://www.pulsapi.com/services/darwin-cx

Darwin CX Component Status

The main Darwin CX systems on this page. All 28 are operational right now.

28operational
Atlas
Operational
AWS » AWS cloudfront
Operational
AWS » AWS rds-ca-central-1
Operational

25 more components tracked

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

Also tracking AWS » AWS rds-us-east-1, AWS » AWS rds-us-east-2, Client API » Client API - 2900, Cloudinary Media Delivery, Core » DCXBackend, Customer Self Service » Customer Portals - Main, Darwin Client & Care App, DarwinCX Worldwide Deployments » DarwinCX DE, DarwinCX Worldwide Deployments » DarwinCX UK, Data Services » Data Transfer via FiveTran, Data Services » Snowflake Snowflake Data Warehouse, DCXAdmin » darwinadmin, and 13 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Darwin CX Outages & Incidents

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

Darwin services currently unavailableResolved Oct 26, 2026 · 17h 25mResolved

This incident has been resolved. --- [2026-10-27T11:42:10.881Z] (monitoring) Monitoring and remediation complete. --- [2026-10-26T18:57:41.172Z] (monitoring) The issue affecting services has been resolved and service has been restored. We are monitoring the platform to ensure continued stability before closing this incident. --- [2026-10-26T18:16:39.907Z] (investigating) We’re aware of a problem affecting service and our engineers are actively working to restore full access. Impact remains ongoing at this time; we will share additional information as it becomes available.

Shop pages not renderingResolved Oct 21, 2026 · 1h 23mResolved

The issue affecting shop pages has been resolved and service has been restored. We are monitoring the platform to ensure continued stability before closing this incident. Thank you. --- [2026-10-21T19:52:16.369Z] (identified) We have identified the cause of an issue impacting some users and are actively working to restore full service. Our teams are continuing remediation efforts. We will share additional information as it becomes available.

Transactions held in queueResolved Aug 21, 2026 · 472h 38mResolved

This was monitored for 3 weeks to ensure no transactions were missed. --- [2026-08-22T16:39:47.599Z] (monitoring) The issue affecting users has been resolved and transactions have been released. We are monitoring the platform to ensure continued stability before closing this incident. --- [2026-08-21T21:55:56.268Z] (identified) We have identified the cause of an issue impacting some users and are actively working to restore full service. Once completed we will endure the transactions are no longer in queue. We will continue to provide updates as remediation progresses. --- [2026-08-21T21:05:13.805Z] (investigating) We continue to investigate an issue affecting some users. Impact remains ongoing at this time and our teams are actively working to identify what is causing transactions to be held in queue. We will share additional information as it becomes available.

Darwin CX Uptime History

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

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Darwin CX Outage Reports

Problems reported by engineers using Darwin CX. 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 Darwin CX problems reported yet.

Something wrong with Darwin CX on your end?

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

About Darwin CX

Darwin CX's status page at status.darwin.cx lists 28 components, such as AWS cloudfront, AWS rds-ca-central-1 and AWS rds-us-east-1. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Darwin CX's side or yours.

Darwin CX Status FAQ

Is Darwin CX down right now?

The verdict at the top of this page comes from the latest poll of the official Darwin CX status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Darwin CX 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 Darwin CX recovers.

How do I check Darwin CX uptime history?

PulsAPI tracks Darwin CX uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Darwin CX changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Darwin CX outages?

PulsAPI reads the official Darwin CX status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Darwin CX components?

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

Can I get alerts when Darwin CX goes down?

Yes. Create a free account and subscribe to Darwin CX: 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 Darwin CX 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 Darwin CX problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Darwin CX?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Darwin CX 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 Darwin CX with the rest of your stack

4372+ 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