Resolved after 56 minutes, affecting Travel, on March 20, 2026.
Impact as Reported: In the US2 Data Center, New Concur Travel bookings were 30% below expected level. Affected users may have experienced latency and performance issues. when accessing the travel page and attempting to perform booking related tasks. Root cause: Due to resource throttling available CPU was increased on a container custer to maintain performance. However, with average CPU usage having been lowered, the containers automatically scaled down to the configured minimum number of pods, which was not sufficient to handle incoming traffic. The Incident Response team increased the number of pods to fully restore the service. Corrective Actions: The following corrective and preventative actions were identified: Additional metrics are being configure as auto-scaling triggers to maintain the optimal number of pods Monitoring is being updated to alert when pods scale down to minimum
Affected components
Update timeline
- resolved Mar 20, 2026, 08:49 PM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Mar 20, 2026, 09:03 PM UTC
In the US2 Data Center, New Concur Travel bookings via the Sabre and Amadeus Global Distribution Systems are 30% below expected level. Affected users may experience latency and performance issues. The Incident Response Team (IRT) is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Mar 20, 2026, 09:15 PM UTC
In the US2 Data Center, New Concur Travel bookings were 30% below expected level. Affected users may have experienced latency and performance issues when accessing the travel page and attempting to perform booking related tasks. 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.
- resolved Mar 20, 2026, 09:28 PM UTC
In the US2 Data Center, New Concur Travel bookings were 30% below expected level. Affected users may have experienced latency and performance issues when accessing the travel page and attempting to perform booking related tasks. The Incident Response Team (IRT) took action to increase capacity on an application server tier to restore service. We have verified that service performance is stable and will now resolve this 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.
- resolved Apr 09, 2026, 06:14 AM UTC
Impact as Reported: In the US2 Data Center, New Concur Travel bookings were 30% below expected level. Affected users may have experienced latency and performance issues. when accessing the travel page and attempting to perform booking related tasks. Root cause: Due to resource throttling available CPU was increased on a container custer to maintain performance. However, with average CPU usage having been lowered, the containers automatically scaled down to the configured minimum number of pods, which was not sufficient to handle incoming traffic. The Incident Response team increased the number of pods to fully restore the service. Corrective Actions: The following corrective and preventative actions were identified: Additional metrics are being configure as auto-scaling triggers to maintain the optimal number of pods Monitoring is being updated to alert when pods scale down to minimum
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.
Amazon Web Services