Travel: P1

Update timeline

1. resolved Jun 17, 2026, 03:17 PM UTC

   All Sabre and Amadeus customers in the APJ1 Data Center are experiencing a functional disruption affecting travel booking completions. At the Review and Book stage, users encounter the error: “An error has occurred with your booking. Start a new search and try again.” This error occurs after selecting Book and Continue for air, hotel, and car travel bookings, preventing completion of the reservation. At this time, Sabre and Amadeus bookings cannot be finalized, while bookings using other GDS (Global Distribution System) providers remain unaffected and can be completed successfully. Workaround: A workaround for this issue is not available at this time. The Incident Response Team (IRT) is engaged and rolled back a recent change in attempt to resolve the issue. This action did not yield successful results. The IRT has engaged additional resources to investigate the cause of this incident and identify a fix. Our next scheduled update will be in one hour or sooner should a significant change occur.

2. resolved Jun 17, 2026, 04:07 PM UTC

   All Sabre and Amadeus customers in the APJ1 Data Center experienced a functional disruption affecting travel booking completions. At the Review and Book stage, users encountered the error: “An error has occurred with your booking. Start a new search and try again.” This error occurred after selecting Book and Continue for air, hotel, and car travel bookings, preventing completion of the reservation. Sabre and Amadeus bookings could not be finalized, while bookings using other GDS (Global Distribution System) providers remained unaffected and could be completed successfully. Workaround: A workaround for this issue was not available during service impact. Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

3. resolved Jun 17, 2026, 04:23 PM UTC

   All Sabre and Amadeus customers in the APJ1 Data Center experienced a functional disruption affecting travel booking completions. At the Review and Book stage, users encountered the error: “An error has occurred with your booking. Start a new search and try again.” This error occurred after selecting Book and Continue for air, hotel, and car travel bookings, preventing completion of the reservation. Sabre and Amadeus bookings could not be finalized, while bookings using other GDS (Global Distribution System) providers remained unaffected and could be completed successfully. Workaround: A workaround for this issue was not available during service impact. The Incident Response Team (IRT) updated a configuration component on an application server tier to restore service. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

4. resolved Jul 02, 2026, 01:30 PM UTC

   Impact as Reported: All Sabre and Amadeus customers in the APJ1 Data Center experienced a functional disruption affecting travel booking completions. At the Review and Book stage, users encountered the error: “An error has occurred with your booking. Start a new search and try again.” This error occured after selecting Book and Continue for air, hotel, and car travel bookings, preventing completion of the reservation. During the incident, Sabre and Amadeus bookings could not be finalized, while bookings using other GDS (Global Distribution System) providers remained unaffected and could be completed successfully. Root cause: An issue impacted booking transactions across all verticals in the APJ environment, resulting in booking failures. The failures occurred because a critical service responsible for managing booking-related operations was unable to complete required processing. The root cause was an incorrect AWS IAM role configuration associated with a service account used by the booking management service in the APJ environment. During deployment changes related to another environment, the configuration was updated for several regions but the APJ-specific setting was inadvertently left unchanged. As a result, the service could not obtain the required AWS credentials, causing booking operations to fail. Service was restored by deploying a configuration update that corrected the IAM role assignment for the affected service account. The issue was not detected during testing because the configuration was environment-specific and only impacted APJ. Additionally, the change review process focused primarily on the target deployment environment and did not identify the unintended impact to APJ. Corrective Actions: The following corrective and preventative actions were identified: Deployed a configuration update to correct the IAM role assignment for the affected service account in APJ. Validated the updated configuration and restored normal booking processing. Implement pre-merge protections for high-risk service-level configuration changes, including service accounts, IAM role assignments, and other critical infrastructure settings. Require additional reviewer oversight and validation for protected configuration paths to reduce the risk of configuration drift across environments. Introduce automated checks that detect and block unsafe environment-specific configuration changes before deployment. Enhance application resiliency by enabling downstream components to use an alternate data source when the booking management service is unavailable, reducing the customer impact of similar failures in the future.