CureMD Outage History
1 incident recorded over the last 365 days, 1 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 CureMD Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 18, 2025 | Service Disruption Due to Global Cloudflare OutageDear CureMD User, We’re pleased to inform you that the service disruption affecting the CureMD application has been fully resolved. The issue originated from a global Cloudflare outage, which has now been addressed by… | 23h 21m | Resolved |
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 CureMD 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 CureMD 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 CureMD 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 CureMD outage in this window ran 23h 21m, against a mean recovery of 23h 21m. If you depend on CureMD 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.