SAP Concur incident
Expense, Travel, Invoice, Request, Imaging, Analysis/Intelligence: P1
Resolved after 2 hours 23 minutes, affecting Analysis/Intelligence and Expense and 1 more, on March 30, 2026.
Impact as Reported: In the EU2 Data Center, customers are intermittently unable to use the SAP Concur website. After logging in, the users are getting error: “Sorry Concur is currently unavailable”. 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, 08:11 AM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Mar 30, 2026, 08:35 AM UTC
In the EU2 Data Center, customers are intermittently unable to use the SAP Concur website. After logging in, the users are getting error: “Sorry Concur is currently unavailable”. The Incident Response Team have been engaged and are investigating. Our next scheduled update will be in one hour or sooner, should a significant change occur.
- resolved Mar 30, 2026, 09:32 AM UTC
In the EU2 Data Center, customers are intermittently unable to use the SAP Concur website. After logging in, the users are getting error: “Sorry Concur is currently unavailable”. The Incident Response Team has identified a possible issue with a feature displaying SAP Concur services and are working with internal resources on restoring the service. Our next scheduled update will be in one hour or sooner, should a significant change occur. A workaround for this issue is not available at this time.
- resolved Mar 30, 2026, 10:09 AM UTC
In the EU2 Data Center, customers were intermittently unable to use the SAP Concur website. After logging in, the users were getting error: “Sorry Concur is currently unavailable”. Service has been restored to a normal operating level, and we have started a mandatory post recovery monitoring period to ensure service performance stability prior to declaring the incident resolved. We will post the next incident communication at or before 11:30 UTC on 30 March 2026.
- resolved Mar 30, 2026, 11:25 AM UTC
In the EU2 Data Center, customers were intermittently unable to use the SAP Concur website. After logging in, the users were getting error: “Sorry Concur is currently unavailable”. Alternately, users were able to login successfully, but were getting random errors when trying to use SAP Concur services. While the Incident Response Team was investigating, the service recovered during a planned deployment. 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 13, 2026, 03:53 PM UTC
Impact as Reported: In the EU2 Data Center, customers are intermittently unable to use the SAP Concur website. After logging in, the users are getting error: “Sorry Concur is currently unavailable”. 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