SAP Concur Real Time Status

8 October 2026 | 11:16 am

We identified an intermittent service degradation that affected logins via mobile device. This issue was impacting approximately 1% of customers in the US2 Data Center. When attempting to access the SAP Concur site using the SAP mobile app, users may have received the error message, "Sorry, something went wrong," after entering their login credentials. When this error occurred, the login attempted could not be completed during that session. Additionally, it was possible some users may have experienced increased latency after entering their username and password. Users who were already logged in were able to continue working without interruption. Workaround: We identified a workaround for you during the time of impact. If you encountered an error message after entering your user name and password, you may have been able to successfully sign in by retrying your login attempt. Additionally, it was possible to login via web without issue. The IRT isolated an underperforming server and took action to perform a failover 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 be conducted , and a root cause analysis report provided when that investigation is complete.

8 October 2026 | 11:05 am

We identified an intermittent service degradation that affected logins via mobile device. This issue was impacting approximately 1% of customers in the US2 Data Center. When attempting to access the SAP Concur site using the SAP mobile app, users may have received the error message, "Sorry, something went wrong," after entering their login credentials. When this error occurred, the login attempted could not be completed during that session. Additionally, it was possible some users may have experienced increased latency after entering their username and password. Users who were already logged in were able to continue working without interruption. Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

8 October 2026 | 10:54 am

We have identified an intermittent service degradation affecting logins via mobile device. This issue is currently impacting approximately 1% of customers in the US2 Data Center. When attempting to access the SAP Concur site via mobile device, users may receive the error message, "Sorry, something went wrong," after entering their login credentials. When this error occurs, the login attempt cannot be completed during that session. Additionally, it is possible some users may experience increased latency after entering their username and password. Users who are already logged in can continue working without interruption. Workaround: We have identified a workaround for you. If you encounter an error message after entering your user name and password, you may be able to successfully sign in by retrying your login attempt. Additionally, it is possible to login via web without issue. The Incident Response Team (IRT) is actively working to restore normal service by restarting servers that have been identified as underperforming. Our next scheduled update will be provided within one hour, or sooner if a significant change in status occurs.

8 October 2026 | 10:34 am

We are working to determine the user impact and will provide information as it becomes available.

2 October 2026 | 6:49 am

Impact as Reported: We identified and resolved a service degradation affecting user logins in the US2 Data Center. All customers hosted on a particular server were affected. During the time of impact, users attempting to sign in using either Single Sign-On (SSO) or a username and password may have encountered the following error message: 'Sorry, something went wrong.' As a result, users were unable to access Concur and would have experienced errors with various services during the downtime. Users that were already logged in during the time of impact were able to continue with their work. Root cause: The incident was caused by a large-scale database update that modified approximately 360000 records in a heavily utilized application table, creating extensive locking and resource contention that rendered the database unresponsive. Due to a human error the operation was executed directly against production without following an established review process, bypassing validation and impact assessment controls. Corrective Actions: Investigate and reduce higher-level user privileges on Concur production databases and migrate legacy manual update workflows to more controlled execution mechanisms. Enforce a governed execution mechanisms that provide additional validation, oversight, and operational safeguards.Impact as Reported: We identified and resolved a service degradation affecting user logins in the US2 Data Center. All customers hosted on a particular server were affected. During the time of impact, users attempting to sign in using either Single Sign-On (SSO) or a username and password may have encountered the following error message: 'Sorry, something went wrong.' As a result, users were unable to access Concur and would have experienced errors with various services during the downtime. Users that were already logged in during the time of impact were able to continue with their work. Root cause: The incident was caused by a large-scale database update that modified approximately 360000 records in a heavily utilized application table, creating extensive locking and resource contention that rendered the database unresponsive. Due to a human error the operation was executed directly against production without following an established review process, bypassing validation and impact assessment controls. Corrective Actions: Investigate and reduce higher-level user privileges on Concur production databases and migrate legacy manual update workflows to more controlled execution mechanisms. Enforce a governed execution mechanisms that provide additional validation, oversight, and operational safeguards.