SAP Concur incident

Travel: P1

Resolved after 31 minutes, affecting Travel, on October 27, 2025.

resolved Nov 12, 2025, 08:26 AM UTC

Impact as Reported: New Concur Travel bookings dropped up to 50 % below expected level for 31 minutes in the US2 Data Center. Affected users may have experienced latency, no response, or errors when attempting to perform travel searches or complete travel bookings. Root cause: An application tier supporting travel related workflows experienced performance degradation, resulting in intermittent time outs that impacted users ability to search or book. The Incident Response Team identified an issue with the service infrastructure configuration allocating insufficient memory to process increased load, causing application nodes to fail life checks and be taken out of service, reducing the available processing capacity. Service was restored by increasing the affected application tier capacity. Corrective Actions: The following corrective and preventive actions were identified: Increase the application tier baseline capacity Increase the memory allocated to the tier nodes Review service dependencies and remove unnecessary checks Review auto-scaling configurations for the impacted service to improve scale up parameters to better respond to load changes.

Started
Oct 27, 2025, 01:42 PM UTC
Resolved
Oct 27, 2025, 02:13 PM UTC
Duration
31m
Detected by Pingoru
Oct 27, 2025, 01:42 PM UTC

Affected components

Travel

Update timeline

  1. resolved Oct 27, 2025, 06:25 PM UTC

    New Concur Travel bookings dropped up to 50 % below expected level for 31 minutes in the US2 Data Center. Affected users may have experienced latency, no response, or errors when attempting to perform travel searches or complete travel bookings. A workaround for this issue was not identified during service degradation. As the Incident Response Team (IRT) identified an issue on a business service tier and increased processing capacity to restore service. We have verified that service performance is stable and will now resolve this incident. A continued investigation into the root cause of this incident will be conducted, and a root cause analysis report provided when that investigation is complete.

  2. resolved Nov 12, 2025, 08:26 AM UTC

    Impact as Reported: New Concur Travel bookings dropped up to 50 % below expected level for 31 minutes in the US2 Data Center. Affected users may have experienced latency, no response, or errors when attempting to perform travel searches or complete travel bookings. Root cause: An application tier supporting travel related workflows experienced performance degradation, resulting in intermittent time outs that impacted users ability to search or book. The Incident Response Team identified an issue with the service infrastructure configuration allocating insufficient memory to process increased load, causing application nodes to fail life checks and be taken out of service, reducing the available processing capacity. Service was restored by increasing the affected application tier capacity. Corrective Actions: The following corrective and preventive actions were identified: Increase the application tier baseline capacity Increase the memory allocated to the tier nodes Review service dependencies and remove unnecessary checks Review auto-scaling configurations for the impacted service to improve scale up parameters to better respond to load changes.

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 →