Resolved after 4 hours 48 minutes, affecting Expense, on March 30, 2026.
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.
Affected components
Update timeline
- resolved Mar 30, 2026, 01:58 PM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Mar 30, 2026, 02:28 PM UTC
Some SAP Concur Expense customers are experiencing issues creating expense reports. Internal performance metrics currently indicate at least a 75% drop in expense report submissions, while internal testing has confirmed affected users encounter errors and latency within the expense report creation process. Internal testing also shows that attempting to refresh or retry after receiving the error resulted in no changed behavior. The Incident Response Team is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Mar 30, 2026, 03:24 PM UTC
Some SAP Concur Expense customers are experiencing issues creating expense reports. Internal performance metrics currently indicate at least a 75% drop in expense report submissions, while internal testing has confirmed affected users encounter various errors and latency within the expense report creation process. Internal testing also shows that attempting to refresh or retry after receiving an error resulted in no changed behavior. The Incident Response Team (IRT) deployed a configuration change on a business server tier in attempt to restore service. Although this action may have resulted in some improved performance, it did not fully restore service functionality. The IRT is investigating to identify root cause and determine best course of action to resolve the issue. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Mar 30, 2026, 04:15 PM UTC
Some SAP Concur Expense customers are experiencing issues creating expense reports. Internal performance metrics currently indicate at least a 75% drop in expense report submissions, while internal testing has confirmed affected users encounter various errors and latency within the expense report creation process. Internal testing also shows that attempting to refresh or retry after receiving an error resulted in no changed behavior. As a workaround, affected users can sign-in to the SAP Concur mobile app to create and submit expense reports. The Incident Response Team (IRT) has engaged additional resources for investigation into root cause. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Mar 30, 2026, 05:15 PM UTC
Some SAP Concur Expense customers are experiencing issues creating expense reports. Internal performance metrics currently indicate at least a 75% drop in expense report submissions, while internal testing has confirmed affected users encounter various errors and latency within the expense report creation process or when attempting to access existing expense reports. Internal testing also shows that attempting to refresh or retry after receiving an error resulted in no changed behavior. As a workaround, affected users can sign-in to the SAP Concur mobile app to create and submit expense reports. The Incident Response Team (IRT) executed a restart of core components on a business server tier in attempt to restore service. Although this action may have resulted in some improved performance, it did not fully restore service functionality. The IRT continues investigation to identify root cause and determine best course of action to resolve the issue. Our next scheduled update will be in two hours or sooner should a significant change occur.
- resolved Mar 30, 2026, 06:45 PM UTC
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. Services have returned to normal operating levels. We will continue monitoring performance for the next 45-60 minutes to verify stability. Once verified as stable the incident will be resolved.
- resolved Mar 30, 2026, 07:49 PM UTC
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.
- resolved Apr 13, 2026, 03:55 PM UTC
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.
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