Resolved after 1 hour 41 minutes, affecting Expense and Travel, on March 23, 2026.
Impact as Reported: In the US2 Data Center, expense report submissions metrics and travel booking metrics were 40% below expected level. Internal testing showed that affected users may have encountered a home page indicating a disruption to services, after logging in. Users who were already logged-in may have encountered errors and general latency while attempting to navigate and perform tasks within SAP Concur Travel and SAP Concur Expense services. Root cause: A core database suffered performance degradation that affected several services. The Incident Response Team identified a stored procedure that was exhausting the resources on the database. The database team switched over to a secondary instance to quickly remove all existing connections. This resolved the degradation and restored all the services. Corrective Actions: The following corrective and preventative actions were identified: Update the stored procedure plan to use less parallelism to prevent it from overloading the database Update the stored procedure to run on read-only secondary instances to prevent it from affecting the primary database instance
Affected components
Update timeline
- resolved Mar 23, 2026, 04:27 PM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Mar 23, 2026, 04:53 PM UTC
In the US2 Data Center, expense report submission metrics and travel booking metrics were 40% below expected level. Internal monitoring and testing suggest affected travel users may have encountered an issue with searching for car or hotel segments encountering errors or latency. Affected expense users may have encountered errors or latency when attempting to create or submit expense reports. 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 23, 2026, 05:34 PM UTC
In the US2 Data Center, expense report submissions metrics and travel booking metrics are 40% below expected level. Internal testing shows that affected users may encounter a home page indicating a disruption to services, after logging in. Users who are already logged-in may encounter errors and general latency while attempting to navigate and perform tasks within SAP Concur Travel and SAP Concur Expense services. We have observed a new disruption to our services during the monitoring period. The Incident Response Team (IRT) is investigating the issue. Our next scheduled update will be in one hour or sooner, should a significant change occur.
- resolved Mar 23, 2026, 06:18 PM UTC
In the US2 Data Center, expense report submissions metrics and travel booking metrics were 40% below expected level. Internal testing showed that affected users may have encountered a home page indicating a disruption to services, after logging in. Users who were already logged-in may have encountered errors and general latency while attempting to navigate and perform tasks within SAP Concur Travel and SAP Concur Expense services. 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 23, 2026, 06:32 PM UTC
In the US2 Data Center, expense report submissions metrics and travel booking metrics were 40% below expected level. Internal testing showed that affected users may have encountered a home page indicating a disruption to services, after logging in. Users who were already logged-in may have encountered errors and general latency while attempting to navigate and perform tasks within SAP Concur Travel and SAP Concur Expense services. The Incident Response Team performed a failover on a database 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.
- resolved Apr 09, 2026, 06:11 AM UTC
Impact as Reported: In the US2 Data Center, expense report submissions metrics and travel booking metrics were 40% below expected level. Internal testing showed that affected users may have encountered a home page indicating a disruption to services, after logging in. Users who were already logged-in may have encountered errors and general latency while attempting to navigate and perform tasks within SAP Concur Travel and SAP Concur Expense services. Root cause: A core database suffered performance degradation that affected several services. The Incident Response Team identified a stored procedure that was exhausting the resources on the database. The database team switched over to a secondary instance to quickly remove all existing connections. This resolved the degradation and restored all the services. Corrective Actions: The following corrective and preventative actions were identified: Update the stored procedure plan to use less parallelism to prevent it from overloading the database Update the stored procedure to run on read-only secondary instances to prevent it from affecting the primary database instance
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