SAP Concur incident
Expense, Travel, Invoice, Request, Analysis/Intelligence: P1
Resolved after 16 minutes, affecting Analysis/Intelligence and Expense and 1 more, on July 23, 2025.
Impact as Reported: In the EU2 and APJ1 Data Centers, logins through the SAP Concur website and SAP Concur mobile app was below expected levels. Affected users may have encountered the following error: “Sorry, something went wrong.”, when attempting to sign-in. Additionally, users who were already logged in should have been able to use SAP Concur services successfully. Root cause: The networking team identified a brief increase in internet connections to the European region causing an increase in latency leading the authentication service briefly experiencing intermittent timeouts in calls between environments that are part of the initial steps of the log in workflow. The latency returned to normal and service degradation stopped once traffic decreased. Corrective Actions: Additional alerting has been configured for latency on the affected services. Additional logging is being implemented on network traffic to better trace source of traffic increases.
Affected components
Update timeline
- resolved Jul 23, 2025, 12:49 PM UTC
In the EU2 and APJ1 Data Centers, logins through the SAP Concur website and SAP Concur mobile app was below expected levels. Affected users may have encountered the following error: “Sorry, something went wrong.”, when attempting to sign-in. Additionally, users who were already logged in should have been able to use SAP Concur services successfully. 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 Aug 28, 2025, 01:08 PM UTC
Impact as Reported: In the EU2 and APJ1 Data Centers, logins through the SAP Concur website and SAP Concur mobile app was below expected levels. Affected users may have encountered the following error: “Sorry, something went wrong.”, when attempting to sign-in. Additionally, users who were already logged in should have been able to use SAP Concur services successfully. Root cause: The networking team identified a brief increase in internet connections to the European region causing an increase in latency leading the authentication service briefly experiencing intermittent timeouts in calls between environments that are part of the initial steps of the log in workflow. The latency returned to normal and service degradation stopped once traffic decreased. Corrective Actions: Additional alerting has been configured for latency on the affected services. Additional logging is being implemented on network traffic to better trace source of traffic increases.
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.