CloudConvert 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 CloudConvert status97.93% uptime history

Every Recorded CloudConvert Incident

CloudConvert incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 12, 2026Web and iWork are down570h 43mResolved
Oct 8, 2026Degraded performance in EU Central662h 13mResolved
Sep 29, 2026iWork is down880h 58mResolved
Sep 14, 2026US East and iWork are down; EU Central is degraded1247h 51mResolved
Sep 11, 2026Delayed webhook delivery1315h 29mResolved
Sep 7, 2026Office and iWork are down; EU Central, US East, and 1 other service are degraded1404h 43mResolved
Aug 3, 2026iWork is degraded2144h 39mResolved
Jul 31, 2026API, Office, and 1 other service are down1478h 48mResolved
Jul 28, 2026iWork is degraded1552h 47mResolved
Jul 6, 2026iWork is degraded2080h 45mResolved
Jun 16, 2026US East and iWork are down1828h 53mResolved
Jun 12, 2026iWork is down1936h 57mResolved
Jun 11, 2026API is down1961h 9mResolved

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 CloudConvert 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 CloudConvert 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 CloudConvert 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 CloudConvert outage in this window ran 89d 8h, against a mean recovery of 61d 2h. If you depend on CloudConvert 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.