Travel: P1

Update timeline

1. resolved Nov 19, 2025, 06:09 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Nov 19, 2025, 06:30 PM UTC

   We have identified a disruption affecting your service. We have provided details of the incident known at this time below, and are currently assessing and verifying the full extent of the user impact and assembling a specialized Incident Response Team (IRT) to investigate and resolve the issue. We will post the next incident communication at or before 7:15PM UTC on 19 November 2025.

3. resolved Nov 19, 2025, 06:47 PM UTC

   Service has been restored to a normal operating level, and we have started a mandatory post recovery monitoring period to ensure service performance stability prior to declaring the incident resolved. We will post the next incident communication at or before 8:15PMUTC on 19 November 2025. In the US2 Data Center, completing Car and Hotel searches in the New Concur Travel was below expected level. Affected users may have received the following error when attempting to search for travel: "No results found" A workaround for this issue is not available at this time Complete post recovery service performance stability monitoring and verification

4. resolved Nov 19, 2025, 07:02 PM UTC

   We have completed the post recovery stability monitoring period and confirmed that service is operating at a normal and stable level and will now resolve this incident. Please contact the Support Engineer assigned to your case for any questions about this incident. We are sorry for any inconvenience this may have caused. Thank you for your patience. In the US2 Data Center, completing Car and Hotel searches in the New Concur Travel experience was below expected levels. Affected users may have encountered the following errors: for Car searches, ‘No results found,’ and for Hotel searches, ‘No location found.’ A workaround for this issue was not available. The Incident Response Team (IRT) has rolled back a recent deployed change to restore service.

5. resolved Nov 27, 2025, 02:56 PM UTC

   Impact as Reported: In the US2 Data Center, completing Car, Hotel and Rail searches in the New Concur Travel was below expected level. Affected users may have received the following error when attempting to search for travel: "No results found". Root cause: A code update inadvertently introduced a version mismatch between a communication software layer and some of the micro-services leveraging it for connectivity, ultimately leading to inability for user to utilize some functionalities of the Next Gen Travel application. The change was rolled back to restore service. Corrective Actions: The relevant teams have started the development of automation to perform more comprehensive dependency checks prior to executing deployments. The cross-team communication process is also being reviewed with the goal of increasing awareness of changes performed between interdependent services.