SAP Concur incident
Expense, Travel, Invoice, Request, Imaging, Analysis/Intelligence: P1
Resolved after 11 minutes, affecting Analysis/Intelligence and Expense and 1 more, on June 18, 2025.
Impact as Reported: In the US2 Data Center, logins through the SAP Concur website and SAP Concur mobile app were below expected level. Affected users may have encountered the following error when attempting to sign-in, “Sorry, something went wrong.” Root cause: The root cause of the incident has been determined to be some unoptimized application code introduced during a scheduled deployment, that occurring during a high product utilization window, has caused memory constraints for the application servers pool involved in the authentication workflow. The service self restored as the deployment came to conclusion. Corrective Actions: An additional scenario was added to the already existing testing suite, to ensure similar degradation cases will be spotted in pre-production environments. The deployment time window for the affected service has been modified in order to avoid high product utilization windows.
Affected components
Update timeline
- resolved Jun 18, 2025, 03:35 PM UTC
In the US2 Data Center, logins through the SAP Concur website and SAP Concur mobile app were below expected level. Affected users may have encountered the following error when attempting to sign-in, “Sorry, something went wrong.” As the Incident Response Team (IRT) was gathering, the issue self-recovered. 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 Jul 08, 2025, 08:52 AM UTC
Impact as Reported: In the US2 Data Center, logins through the SAP Concur website and SAP Concur mobile app were below expected level. Affected users may have encountered the following error when attempting to sign-in, “Sorry, something went wrong.” Root cause: The root cause of the incident has been determined to be some unoptimized application code introduced during a scheduled deployment, that occurring during a high product utilization window, has caused memory constraints for the application servers pool involved in the authentication workflow. The service self restored as the deployment came to conclusion. Corrective Actions: An additional scenario was added to the already existing testing suite, to ensure similar degradation cases will be spotted in pre-production environments. The deployment time window for the affected service has been modified in order to avoid high product utilization windows.
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.