SAP Concur Real Time Status

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.

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.