Booking API Outage History

Booking API is up right now

Pingoru has recorded 70 incidents for Booking API: 70 in the last 12 months and 32 in the last 90 days.

Source: connect.booking.com

70incidents recorded
70last 12 months
32last 90 days
58 minutestypical duration
Incidents per month
02040AprMayJunJulAugSepOctNov4
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov2%
Pingoru began tracking Booking API in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202640 of 720 (0%)
May 2026714 of 744 (2%)
June 2026115 of 720 (1%)
July 2026104 of 744 (1%)
August 2026106 of 744 (1%)
September 202631 of 720 (0%)
October 20262116 of 744 (2%)
November 202642 of 114 (2%)

Incidents, newest first

Minor June 29, 2026 We've resolved an issue with Reservations –

Started Jun 29, 2026, 09:38 AM UTC· resolved Jun 29, 2026, 09:38 AM UTC

  1. resolved Jun 29, 2026, 09:38 AM UTC

    We've resolved an issue with Content API Start: 2026-06-29 09:38:25 (GMT+1) Incident Details Triggered: 2026-06-29 09:38:25 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Read the full incident report →

Minor June 28, 2026 We've resolved an issue with Content API –

Started Jun 28, 2026, 10:30 AM UTC· resolved Jun 28, 2026, 10:30 AM UTC

  1. resolved Jun 28, 2026, 10:30 AM UTC

    We've resolved an issue with Content API Start: 2026-06-28 10:30:00 (GMT+1) Incident Details Triggered: 2026-06-28 10:30:00 (GMT+1) New property creation unavailable since Jun 28, 12:30 CEST. OTA_HotelDescriptiveContentNotif returns HTTP 400; property-api returns HTTP 500. Existing properties not affected. Please hold submissions until further notice — resubmission will be required once resolved.

Read the full incident report →

Minor June 22, 2026 We've resolved an issue with Reservations 38m

Started Jun 22, 2026, 07:44 PM UTC· resolved Jun 22, 2026, 08:22 PM UTC

  1. resolved Jun 22, 2026, 07:44 PM UTC

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

  2. resolved Jun 22, 2026, 08:22 PM UTC

    We've resolved an issue with Content API Start: 2026-06-22 20:22:56 (GMT+1) Incident Details Triggered: 2026-06-22 20:22:56 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Read the full incident report →

Minor June 21, 2026 We've resolved an issue with Reservations –

Started Jun 21, 2026, 03:26 AM UTC· resolved Jun 21, 2026, 03:26 AM UTC

  1. resolved Jun 21, 2026, 03:26 AM UTC

    We've resolved an issue with Content API Start: 2026-06-21 03:26:21 (GMT+1) End: 2026-06-21 03:27:25 (GMT+1) Incident Details Resolved: 2026-06-21 03:27:25 (GMT+1) A previously identified issue has been resolved and no action is required from your end. We apologise for any inconvenience this may have caused. Acknowledged: 2026-06-21 03:27:14 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-06-21 03:26:21 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Read the full incident report →

Minor June 19, 2026 We've resolved an issue with Reservations 4m

Started Jun 19, 2026, 10:26 AM UTC· resolved Jun 19, 2026, 10:31 AM UTC

  1. resolved Jun 19, 2026, 10:26 AM UTC

    We've resolved an issue with Content API Start: 2026-06-19 10:26:59 (GMT+1) Incident Details Triggered: 2026-06-19 10:26:59 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  2. resolved Jun 19, 2026, 10:31 AM UTC

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

Read the full incident report →

Minor June 15, 2026 We've resolved an issue with Reservations –

Started Jun 15, 2026, 09:06 PM UTC· resolved Jun 15, 2026, 09:06 PM UTC

  1. resolved Jun 15, 2026, 09:06 PM UTC

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

Read the full incident report →

Minor June 3, 2026 We've resolved an issue with Reservations 36m

Started Jun 03, 2026, 06:14 PM UTC· resolved Jun 03, 2026, 06:51 PM UTC

  1. resolved Jun 03, 2026, 06:14 PM UTC

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

  2. resolved Jun 03, 2026, 06:51 PM UTC

    We've resolved an issue with Content API Start: 2026-06-03 18:51:23 (GMT+1) End: 2026-06-03 18:52:26 (GMT+1) Incident Details Resolved: 2026-06-03 18:52:26 (GMT+1) A previously identified issue has been resolved and no action is required from your end. We apologise for any inconvenience this may have caused. Acknowledged: 2026-06-03 18:51:26 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-06-03 18:51:23 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Read the full incident report →

Minor June 2, 2026 We've resolved an issue with Room and Rate Plan Management 1s

Started Jun 02, 2026, 11:19 AM UTC· resolved Jun 02, 2026, 11:19 AM UTC

  1. resolved Jun 02, 2026, 11:19 AM UTC

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

  2. resolved Jun 02, 2026, 11:19 AM UTC

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

Read the full incident report →

Minor June 2, 2026 We've resolved an issue with Rates and Availability –

Started Jun 02, 2026, 11:09 AM UTC· resolved Jun 02, 2026, 11:09 AM UTC

  1. resolved Jun 02, 2026, 11:09 AM UTC

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

Read the full incident report →

Minor May 27, 2026 We've resolved an issue with Reservations –

Started May 27, 2026, 01:43 PM UTC· resolved May 27, 2026, 01:43 PM UTC

  1. resolved May 27, 2026, 01:43 PM UTC

    We've resolved an issue with Content API Start: 2026-05-27 13:43:25 (GMT+1) Incident Details Triggered: 2026-05-27 13:43:25 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Read the full incident report →

Minor May 21, 2026 We've resolved an issue with Reservations 4h 50m

Started May 21, 2026, 10:27 AM UTC· resolved May 21, 2026, 03:17 PM UTC

  1. resolved May 21, 2026, 10:27 AM UTC

    We've resolved an issue with Content API Start: 2026-05-21 10:27:25 (GMT+1) End: 2026-05-21 10:29:29 (GMT+1) Incident Details Resolved: 2026-05-21 10:29:29 (GMT+1) A previously identified issue has been resolved and no action is required from your end. We apologise for any inconvenience this may have caused. Acknowledged: 2026-05-21 10:27:50 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-21 10:27:25 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  2. resolved May 21, 2026, 10:44 AM UTC

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

  3. resolved May 21, 2026, 11:02 AM UTC

    We've resolved an issue with Content API Start: 2026-05-21 11:02:22 (GMT+1) Incident Details Triggered: 2026-05-21 11:02:22 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  4. resolved May 21, 2026, 11:16 AM UTC

    We've resolved an issue with Content API Start: 2026-05-21 11:16:24 (GMT+1) End: 2026-05-21 11:20:25 (GMT+1) Incident Details Resolved: 2026-05-21 11:20:25 (GMT+1) A previously identified issue has been resolved and no action is required from your end. We apologise for any inconvenience this may have caused. Acknowledged: 2026-05-21 11:16:54 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-21 11:16:24 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  5. resolved May 21, 2026, 11:51 AM UTC

    We've resolved an issue with Content API Start: 2026-05-21 11:51:23 (GMT+1) End: 2026-05-21 11:54:28 (GMT+1) Incident Details Resolved: 2026-05-21 11:54:28 (GMT+1) A previously identified issue has been resolved and no action is required from your end. We apologise for any inconvenience this may have caused. Acknowledged: 2026-05-21 11:51:54 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-21 11:51:23 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  6. resolved May 21, 2026, 12:04 PM UTC

    We've resolved an issue with Content API Start: 2026-05-21 12:04:25 (GMT+1) End: 2026-05-21 12:06:30 (GMT+1) Incident Details Resolved: 2026-05-21 12:06:30 (GMT+1) A previously identified issue has been resolved and no action is required from your end. We apologise for any inconvenience this may have caused. Acknowledged: 2026-05-21 12:06:31 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-21 12:04:25 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

  7. resolved May 21, 2026, 03:17 PM UTC

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

Read the full incident report →

Minor May 20, 2026 We've resolved an issue with Reservations –

Started May 20, 2026, 11:01 AM UTC· resolved May 20, 2026, 11:01 AM UTC

  1. resolved May 20, 2026, 11:01 AM UTC

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

Read the full incident report →

Minor May 19, 2026 We've resolved an issue with Reservations –

Started May 19, 2026, 11:58 AM UTC· resolved May 19, 2026, 11:58 AM UTC

  1. resolved May 19, 2026, 11:58 AM UTC

    We've resolved an issue with Content API Start: 2026-05-19 11:58:24 (GMT+1) End: 2026-05-19 12:00:38 (GMT+1) Incident Details Resolved: 2026-05-19 12:00:38 (GMT+1) A previously identified issue has been resolved and no action is required from your end. We apologise for any inconvenience this may have caused. Acknowledged: 2026-05-19 11:58:49 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-05-19 11:58:24 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Read the full incident report →

Minor May 11, 2026 We've resolved an issue with Rates and Availability –

Started May 11, 2026, 02:51 PM UTC· resolved May 11, 2026, 02:51 PM UTC

  1. resolved May 11, 2026, 02:51 PM UTC

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

Read the full incident report →

Minor May 6, 2026 We've resolved an issue with Authentication 3h

Started May 06, 2026, 01:02 PM UTC· resolved May 06, 2026, 04:02 PM UTC

  1. resolved May 06, 2026, 01:02 PM UTC

    We've resolved an issue with Content API Start: 2026-05-06 13:02:03 (GMT+1) Incident Details Triggered: 2026-05-06 13:02:03 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

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

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

  3. resolved May 06, 2026, 04:02 PM UTC

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

Read the full incident report →

Minor May 5, 2026 We've resolved an issue with Authentication 5h 59m

Started May 05, 2026, 03:57 PM UTC· resolved May 05, 2026, 09:57 PM UTC

  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.

Read the full incident report →

Minor April 30, 2026 We've resolved an issue with Reservations –

Started Apr 30, 2026, 07:51 PM UTC· resolved Apr 30, 2026, 07:51 PM UTC

  1. resolved Apr 30, 2026, 07:51 PM UTC

    We've resolved an issue with Content API Start: 2026-04-30 19:51:25 (GMT+1) Incident Details Triggered: 2026-04-30 19:51:25 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Read the full incident report →

Minor April 25, 2026 We've resolved an issue with Reservations –

Started Apr 25, 2026, 11:49 AM UTC· resolved Apr 25, 2026, 11:49 AM UTC

  1. resolved Apr 25, 2026, 11:49 AM UTC

    We've resolved an issue with Content API Start: 2026-04-25 11:49:57 (GMT+1) Incident Details Triggered: 2026-04-25 11:49:57 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Read the full incident report →

Minor April 23, 2026 We've resolved an issue with Reservations –

Started Apr 23, 2026, 10:12 AM UTC· resolved Apr 23, 2026, 10:12 AM UTC

  1. resolved Apr 23, 2026, 10:12 AM UTC

    We've resolved an issue with Content API Start: 2026-04-23 10:12:23 (GMT+1) End: 2026-04-23 10:16:24 (GMT+1) Incident Details Resolved: 2026-04-23 10:16:24 (GMT+1) A previously identified issue has been resolved and no action is required from your end. We apologise for any inconvenience this may have caused. Acknowledged: 2026-04-23 10:15:24 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-04-23 10:12:23 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Read the full incident report →

Minor April 20, 2026 We've resolved an issue with Reservations –

Started Apr 20, 2026, 06:48 AM UTC· resolved Apr 20, 2026, 06:48 AM UTC

  1. resolved Apr 20, 2026, 06:48 AM UTC

    We've resolved an issue with Content API Start: 2026-04-20 06:48:52 (GMT+1) End: 2026-04-20 07:01:29 (GMT+1) Incident Details Resolved: 2026-04-20 07:01:29 (GMT+1) A previously identified issue has been resolved and no action is required from your end. We apologise for any inconvenience this may have caused. Acknowledged: 2026-04-20 06:50:20 (GMT+1) Identified - We are on it. We have identified the issue and are working to fully resolve service. Triggered: 2026-04-20 06:48:52 (GMT+1) Investigating - We are investigating the incident which is causing errors for this api.

Read the full incident report →