Skip to content
Back to CloudinaryIncident Postmortem
Cloudinary logo

Cloudinary

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Cloudinary: vendor-reported major incident on September 28 (tracked 5h 5m)

Sep 28, 10:03 AM → Sep 28, 03:08 PM · 5h 5m · high

Cloudinary reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 5h 5m, from Mon, 28 Sep 2026 10:03:29 GMT to Mon, 28 Sep 2026 15:08:45 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
5h 5m
tracked by PulseWatch

Impact

This high-severity incident affected Cloudinary for a duration of 5 hours and 5 minutes. During this period, the service experienced a disruption. No user-reported data was collected for this incident, as it was detected through automated signals.

Incident timeline

  1. Sep 28, 10:03 AM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 28, 10:03 AM

    Status updated: possible issue

  3. Sep 28, 03:08 PM

    PulseWatch closed the incident

Official updates

  1. Sep 28, 10:03 AM

    Cloudinary reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash