SAP Concur Real Time Status

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.

2 October 2026 | 6:44 am

Impact as Reported: We have identified and resolved a service degradation that affected new Concur Travel bookings for air, hotel, and car through the Sabre Global Distribution System (GDS). During the impact period, approximately 60% of Sabre bookings in the US2 Data Center and 40% of Sabre bookings in the EU2 and USPSCC Data Centers were affected. Affected users encountered the following error after selecting a travel option and clicking “Book and Continue” on the Review and Book page: “An unclassified error has occurred.” Legacy Concur Travel bookings were not affected. Root cause: The root cause of the incident has been identified to be a service disruption within our third party Global Distribution System (GDS) Sabre. Corrective Actions: N/A

2 October 2026 | 6:42 am

Impact as Reported: We identified a functional disruption that impacted New Concur Travel hotel searches through the Travelport+ Global Distribution System (GDS) in the US2 Data Center. Travel customers received the error, “There has been a technical issue. Please reload the page and try again” after selecting Search, which prevented users from searching and booking hotels. Car and air searches were not affected. Unfortunately, no workaround was available during the period of impact. Root cause: The root cause of the incident has been identified to be a service disruption within our third party Global Distribution System (GDS) Travelport. Corrective Actions: N/A

28 September 2026 | 6:46 pm

We have identified and resolved a service disruption impacting access to Concur Expense and Invoice. This is impacting all customers in the US2 datacenter. After logging in and trying to access Concur Expense and Invoice, users encountered the following error “Sorry,but something went wrong with this task.Try refreshing the pager sign out and sign in again.” Workaround: Unfortunately, no workaround was available during this period of impact. 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.

25 September 2026 | 5:00 am

We have identified and resolved a service degradation that affected New Concur Travel bookings for air, hotel, and car through the Sabre Global Distribution System (GDS). During the impact period, approximately 60% of Sabre bookings in the US2, 40% of Sabre bookings in the EU2 and Concur Cloud for Public Sector (CCPS) Data Centers were affected. Affected users encountered the following error after selecting a travel option and clicking “Book and Continue” on the Review and Book page: “An unclassified error has occurred.” Legacy Concur Travel bookings were not affected. Unfortunately, there was no way for you to workaround the issue during the time of impact. The Incident Response Team (IRT) determined that the issue was caused by a problem involving a third-party vendor during the process of calling the Sabre GDS to complete bookings. 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.