Booking API incident

We've resolved an issue with Authentication

Resolved after 5 hours 59 minutes, on May 5, 2026.

resolved May 05, 2026, 09:57 PM UTC

We've resolved an issue with Content API Start: 2026-05-05 21:57:00 (GMT+1) Incident Details Acknowledged: 2026-05-05 21:57:13 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-05 21:57:00 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Started
May 05, 2026, 03:57 PM UTC
Resolved
May 05, 2026, 09:57 PM UTC
Duration
5h 59m
Detected by Pingoru
May 05, 2026, 03:57 PM UTC

Update timeline

  1. resolved May 05, 2026, 03:57 PM UTC

    We've resolved an issue with Content API Start: 2026-05-05 15:57:04 (GMT+1) Incident Details Acknowledged: 2026-05-05 16:00:05 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-05 15:57:04 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  2. resolved May 05, 2026, 06:02 PM UTC

    We've resolved an issue with Content API Start: 2026-05-05 18:02:06 (GMT+1) Incident Details Acknowledged: 2026-05-05 18:04:21 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-05 18:02:06 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  3. resolved May 05, 2026, 06:42 PM UTC

    We've resolved an issue with Content API Start: 2026-05-05 18:42:02 (GMT+1) Incident Details Acknowledged: 2026-05-05 18:42:25 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-05 18:42:02 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  4. resolved May 05, 2026, 08:02 PM UTC

    We've resolved an issue with Content API Start: 2026-05-05 20:02:01 (GMT+1) Incident Details Acknowledged: 2026-05-05 20:02:33 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-05 20:02:01 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  5. resolved May 05, 2026, 09:02 PM UTC

    We've resolved an issue with Content API Start: 2026-05-05 21:02:03 (GMT+1) Incident Details Acknowledged: 2026-05-05 21:04:47 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-05 21:02:03 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  6. resolved May 05, 2026, 09:57 PM UTC

    We've resolved an issue with Content API Start: 2026-05-05 21:57:00 (GMT+1) Incident Details Acknowledged: 2026-05-05 21:57:13 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-05 21:57:00 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Your product runs on more than Booking API

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →