Paradox Outage History

13 incidents recorded over the last 365 days, 13 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.

Live Paradox status100.00% uptime history

Every Recorded Paradox Incident

Paradox incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 14, 2026CEM UnavailableA data migration triggered with this release impacted system performance and responsiveness more than was expected. This effected availability for a subset of users depending on the specific feature set they have…-3811 minResolved
Aug 19, 2026Long CEM Response times causing CEM slownessThe slowness affecting the CEM was resolved after 10 minutes.-1179 minResolved
Aug 11, 2026CEM SlownessThe slowness affecting the CEM has been resolved, and all operations have returned to normal. We will continue to monitor the system to ensure ongoing stability.-5908 minResolved
Aug 11, 2026Journey Enhanced Permissions Migration IssueThis incident has been resolved.246h 7mResolved
Jul 15, 2026CEM Slowness**Impact/Scope:** Customers experienced significant slowness in CEM \(application-wide latency degradation\). ## Investigation Findings Recent shifts in application pattern usage introduced additional traffic to…57 minResolved
Jul 10, 2026CEM Slowness**Impact/Scope:** Customers experienced significant slowness in CEM \(application-wide latency degradation\). ## Investigation Findings Recent shifts in application pattern usage introduced additional traffic to…28 minResolved
Jul 9, 2026CEM Slowness**Impact/Scope:** Customers experienced significant slowness in CEM \(application-wide latency degradation\). ## Investigation Findings Recent shifts in application pattern usage introduced additional traffic to…3h 22mResolved
Jul 1, 2026CEM Slowness**Impact/Scope:** Customers experienced significant slowness in CEM \(application-wide latency degradation\). ## Investigation Findings Recent shifts in application pattern usage introduced additional traffic…1h 35mResolved
Jun 17, 2026Issue with Browser ExtensionThis incident has been resolved.9h 28mResolved
Jun 4, 2026Production Instances UnavailableBetween 3:06PM and 3:24PM PST, CEM and API services were temporarily unavailable due to a failure in our internal DNS infrastructure following a security update. Our automated systems detected the issue and initiated a…0 minResolved
Apr 17, 2026CEM UnavailableOur CEM site became unavailable for 10 minutes during this time. We are continuing to diagnose the root cause.0 minResolved
Jan 12, 2026Cem SlownessBackend processing impacted database performance. This issue has been resolved and performance is back to normal.3h 23mResolved
Dec 11, 2025Potential Chat Response DelayThis incident has been resolved.19h 17mResolved

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 Paradox 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 Paradox 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 Paradox 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 Paradox outage in this window ran 10d 6h, against a mean recovery of 1d 4h. If you depend on Paradox 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.