SAP Concur Real Time Status

13 April 2026 | 10:55 am

Impact as Reported: In the US2 Data Center, some SAP Concur Expense customers experienced issues creating expense reports. Internal performance metrics indicated at least a 75% drop in expense report submissions, while internal testing confirmed affected users encountered various errors and latency within the expense report creation process or when attempting to access existing expense reports. Internal testing also showed that attempting to refresh or retry after receiving an error resulted in no changed behavior. As a workaround, affected users could sign-in to the SAP Concur mobile app to create and submit expense reports. Root cause: Some core services were experiencing performance degradation under load causing several container pods to restart. The Incident Response Team increased the pods available to handle the additional load until the service became responsive again and restored the application. In the root cause investigation, engineering identified an update to a service component unexpectedly and excessively increased resource utilization. A change was made to the component to reduce its memory usage and the updated version was deployed to production. The Incident Response Team was able to confirm that the update resolved the high load on core services and made it more responsive to requests. Corrective Actions: The following corrective and preventive actions were identified: -Updated the dependency with a more performant method to reduce resource utilization. -Update monitoring based on the metrics identified in the root cause investigation. -Update the auto-scaler to include additional metrics to ensure enough pods are available to handle traffic.

9 April 2026 | 1:14 am

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

9 April 2026 | 1:11 am

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

1 April 2026 | 4:16 am

Impact as Reported: SAP Concur Expense customers experienced an issue itemizing hotel expenses. Affected users encounter the following error after clicking the itemizations tab within a new or existing expense, “Before you can continue, you must provide valid information for: Date Range.” The error is encountered despite having a date range populated. Legacy Expense customers are not affected. A potential workaround for this issue has been identified. Users may be able to bypass this issue by reattempting itemization steps after receiving the error. Root cause: A performance improvement change deployed to the expense service inadvertently introdcued a cache synchronization issue that could result in stale date being returned for the hotel range date fields to the form entry validation UI code, with an error being presented to the user preventing hotel expense itemization. Once the issue was raised and the offending change identified, the code was rolled back to restore service.

30 March 2026 | 2:49 pm

Some SAP Concur Expense customers experienced issues creating expense reports. Internal performance metrics indicated at least a 75% drop in expense report submissions, while internal testing confirmed affected users encountered various errors and latency within the expense report creation process or when attempting to access existing expense reports. Internal testing also showed that attempting to refresh or retry after receiving an error resulted in no changed behavior. As a workaround, affected users could sign-in to the SAP Concur mobile app to create and submit expense reports. The Incident Response Team increased capacity on a business 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.