CleverTap Outage History
2 incidents recorded over the last 365 days, 2 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 CleverTap Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 16, 2026 | Data Ingestion Global OutageThe issue has been resolved, and all affected services are operating normally. We have verified system stability and will continue to monitor as part of our standard operational processes. | 4h 16m | Resolved |
| Mar 2, 2026 | Outage on MEC regionWe have made necessary infra changes to get the systems up and running. Your Success managers have been communicating with you on this. This will continue to happen to address specific queries, relay information about… | 75h 12m | 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 CleverTap 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 CleverTap 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 CleverTap 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 CleverTap outage in this window ran 3d 3h, against a mean recovery of 1d 15h. If you depend on CleverTap 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.