Cloudinary outage on August 13 — 19h 13m disruption
Aug 13, 10:43 PM → Aug 14, 05:57 PM · 19h 13m · medium
Cloudinary experienced a service disruption that was initially detected through user reports. The incident began on August 13, 2026, at 22:43 UTC and was resolved on August 14, 2026, at 17:57 UTC.
Impact
This disruption was identified through user reports, with a total of 304 reports received during the incident's duration. The primary issue reported by users was 'Website down'. No specific regional impact was recorded during this period, indicating a broader service disruption.
Top reported issues
- Website down304
Incident timeline
- Aug 13, 10:43 PM
PulseWatch detected elevated report volume (medium severity)
- Aug 14, 05:00 AM
Peak of 4 reports in 15 minutes (baseline 1.3)
- Aug 14, 12:57 PM
Status updated: possible issue
- Aug 14, 01:04 PM
Status updated: possible issue
- Aug 14, 01:08 PM
Status updated: possible issue
- Aug 14, 01:12 PM
Status updated: possible issue
- Aug 14, 01:23 PM
Status updated: possible issue
- Aug 14, 01:28 PM
Status updated: possible issue
- Aug 14, 01:33 PM
Status updated: possible issue
- Aug 14, 01:36 PM
Status updated: possible issue
- Aug 14, 01:41 PM
Status updated: possible issue
- Aug 14, 01:53 PM
Status updated: possible issue
- Aug 14, 01:57 PM
Status updated: possible issue
- Aug 14, 02:03 PM
Status updated: possible issue
- Aug 14, 02:07 PM
Status updated: possible issue
- Aug 14, 02:12 PM
Status updated: possible issue
- Aug 14, 02:23 PM
Status updated: possible issue
- Aug 14, 02:26 PM
Status updated: possible issue
- Aug 14, 02:33 PM
Status updated: possible issue
- Aug 14, 02:37 PM
Status updated: possible issue
- Aug 14, 02:42 PM
Status updated: possible issue
- Aug 14, 02:54 PM
Status updated: possible issue
- Aug 14, 02:57 PM
Status updated: possible issue
- Aug 14, 03:04 PM
Status updated: possible issue
- Aug 14, 03:07 PM
Status updated: possible issue
- Aug 14, 03:12 PM
Status updated: possible issue
- Aug 14, 03:23 PM
Status updated: possible issue
- Aug 14, 03:27 PM
Status updated: possible issue
- Aug 14, 03:33 PM
Status updated: possible issue
- Aug 14, 03:37 PM
Status updated: possible issue
- Aug 14, 03:42 PM
Status updated: possible issue
- Aug 14, 03:53 PM
Status updated: possible issue
- Aug 14, 03:57 PM
Status updated: possible issue
- Aug 14, 04:03 PM
Status updated: possible issue
- Aug 14, 04:07 PM
Status updated: possible issue
- Aug 14, 04:12 PM
Status updated: possible issue
- Aug 14, 04:24 PM
Status updated: possible issue
- Aug 14, 04:30 PM
Status updated: possible issue
- Aug 14, 04:33 PM
Status updated: possible issue
- Aug 14, 04:37 PM
Status updated: possible issue
- Aug 14, 04:42 PM
Status updated: possible issue
- Aug 14, 04:53 PM
Status updated: possible issue
- Aug 14, 04:57 PM
Status updated: possible issue
- Aug 14, 05:03 PM
Status updated: possible issue
- Aug 14, 05:07 PM
Status updated: possible issue
- Aug 14, 05:12 PM
Status updated: possible issue
- Aug 14, 05:23 PM
Status updated: possible issue
- Aug 14, 05:29 PM
Status updated: possible issue
- Aug 14, 05:33 PM
Status updated: possible issue
- Aug 14, 05:37 PM
Status updated: possible issue
- Aug 14, 05:42 PM
Status updated: possible issue
- Aug 14, 05:57 PM
Report volume returned to baseline — incident resolved
Official updates
- Aug 13, 10:43 PM
Cloudinary status page acknowledged the incident.
View official source