Cloudbeds Outage History

8 incidents recorded over the last 365 days, 8 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 Cloudbeds Incident

Cloudbeds incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Booking.com connection impacted1h 0mResolved
Oct 22, 2026Airbnb availability and rate updates impacted2h 30mResolved
Oct 22, 2026Booking.com connection impacted23h 45mResolved
Sep 17, 2026Application impacted16h 59mResolved
Sep 16, 2026Increased card declines for virtual credit card (VCC) payments14h 25mResolved
Sep 10, 2026Tripadvisor Reviews – Connectivity Issue654h 2mResolved
Sep 5, 2026Delay for Payments to appear on folio3h 5mResolved
Sep 2, 2026Delays in Occupancy Data Processing1h 16mResolved

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 Cloudbeds 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 Cloudbeds 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 Cloudbeds 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 Cloudbeds outage in this window ran 27d 6h, against a mean recovery of 3d 17h. If you depend on Cloudbeds 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.