SAP Concur incident

Travel: P1

Resolved after 1 hour 31 minutes, affecting Travel, on March 14, 2025.

resolved Mar 20, 2025, 11:46 AM UTC

Impact as Reported: In the EU2, and US2 Data Centers, travel searches for air, car and hotel through the SAP Concur website were below expected level. Affected users may have encountered the error message, “Sorry, something went wrong.” when attempting to perform travel searches. Root cause: The root cause of the incident has been identified to be a service disruption at one of our third party GDS vendors. Corrective Actions: N/A

Started
Mar 14, 2025, 08:40 PM UTC
Resolved
Mar 14, 2025, 10:11 PM UTC
Duration
1h 31m
Detected by Pingoru
Mar 14, 2025, 08:40 PM UTC

Affected components

Travel

Update timeline

  1. resolved Mar 14, 2025, 09:41 PM UTC

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

  2. resolved Mar 14, 2025, 09:54 PM UTC

    In the APJ1, EU2, and US2 Data Centers, hotel and car searches via Travelport GDS, through the SAP Concur website and the SAP Concur mobile app are below expected level. Affected users may encounter intermittent car and hotel search errors, such as "We're sorry. The server is busy. Please try your request in a few minutes" when attempting to search for cars and hotels. The Incident Response Team is investigating. The Incident Response Team has also received confirmation that Travelport is currently experiencing an outage. Our next scheduled update will be in one hour or sooner should a significant change occur.

  3. resolved Mar 14, 2025, 10:18 PM UTC

    In the APJ1, EU2, and US2 Data Centers, hotel and car searches via Travelport GDS, through the SAP Concur website and the SAP Concur mobile app was below expected level. Affected users may have encountered intermittent car and hotel search errors, such as "We're sorry. The server is busy. Please try your request in a few minutes" when attempting to search for cars and hotels. 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.

  4. resolved Mar 14, 2025, 10:25 PM UTC

    In the APJ1, EU2, and US2 Data Centers, hotel and car searches via Travelport GDS, through the SAP Concur website and the SAP Concur mobile app was below expected level. Affected users may have encountered intermittent car and hotel search errors, such as "We're sorry. The server is busy. Please try your request in a few minutes" when attempting to search for cars and hotels. The Incident Response Team (IRT) received confirmation from Travelport that they took action to improve service performance. 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.

  5. resolved Mar 20, 2025, 11:46 AM UTC

    Impact as Reported: In the EU2, and US2 Data Centers, travel searches for air, car and hotel through the SAP Concur website were below expected level. Affected users may have encountered the error message, “Sorry, something went wrong.” when attempting to perform travel searches. Root cause: The root cause of the incident has been identified to be a service disruption at one of our third party GDS vendors. Corrective Actions: N/A

Your product runs on more than SAP Concur

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 →