SAP Concur Real Time Status

22 September 2026 | 10:27 pm

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. As the Incident Response Team (IRT) was being assembled, the service self-recovered and functionality was restored. Further investigation confirmed that the issue was caused by a service degradation affecting the vendor, which resulted in delayed responses during hotel searches and prevented some hotel search requests from completing successfully. 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 will be provided when that investigation is complete.

21 September 2026 | 2:20 pm

We resolved a functional disruption in the US2 Data Center that affected access to Expense, Travel, Request, Invoice and Analysis/Intelligence services. The majority of US2 customers may have experienced error “Sorry, Concur is currently unavailable” when attempting to sign-in, or an error 500 after successfully signing in and clicking Expense, Travel, Request, Invoice or Reporting tabs. Affected users may have also encountered a home page displaying tiles indicating outages for the impacted services. Executing tasks within each service, such as creating an expense report or searching for travel, may have also resulted in various errors. Workaround: No workaround was identified during service disruption. The Incident Response Team (IRT) executed a configuration change on a database server tier 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 now be conducted, and a root cause analysis report provided when that investigation is complete.

21 September 2026 | 2:00 pm

A functional disruption was identified in the US2 Data Center affecting access to Expense, Travel, Request, Invoice and Analysis/Intelligence services. The majority of US2 customers may have experienced error “Sorry, Concur is currently unavailable” when attempting to sign-in, or an error 500 after successfully signing in and clicking Expense, Travel, Request, Invoice or Reporting tabs. Affected users may have also encountered a home page displaying tiles indicating outages for the impacted services. Executing tasks within each service, such as creating an expense report or searching for travel, may have also resulted in various errors. Workaround: No workaround was identified during service disruption. 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.

21 September 2026 | 1:27 pm

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

21 September 2026 | 5:10 am

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. Unfortunately, no workaround was available during the period of impact. As the Incident Response Team (IRT) was gathering, the service 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.