SAP Concur Real Time Status

21 July 2026 | 11:30 am

We identified and resolved a functional degradation affecting Hilton hotel bookings through the Sabre Global Distribution System (GDS). During the period of impact, approximately 87% of Hilton hotel bookings in the US2, EU2, and Concur Cloud for Public Sector Data Centers were affected. Users were able to search for Hilton properties successfully; however, when attempting to complete a booking for a Hilton hotel, an error was generated and the reservation could not be finalized. Reservations for other hotel chains continued to function normally. Workaround: Unfortunately, no workaround was available during the period of impact. The Incident Response Team (IRT) determined that the issue was caused by a problem involving a third-party hotel vendor during the process of calling the Sabre GDS to complete hotel bookings. A root cause analysis report will be provided upon completion.

20 July 2026 | 6:54 pm

A functional disruption was identified impacting Legacy Concur Travel users in the US2, EU2, APJ1, and Concur Cloud for Public Sector Data Centers when performing air, car, and hotel travel searches using the Worldspan Global Distribution Service (GDS). Users received the error message, "We encountered an issue that prevented us from completing your request," after clicking the Search button. As a result, they were unable to complete their travel bookings. No workaround was available during the incident. This issue was limited to Legacy Concur Travel. New Concur Travel users were not affected. As the Incident Response Team (IRT) was investigating, 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.

20 July 2026 | 8:42 am

Impact as Reported:
 We identified a functional disruption impacting travel searches via the Galileo and Apollo Global Distribution System (GDS) This issue affected all legacy travel customers in the US2, EU2, AJP1, and Concur Cloud for Public Sector data centers. Users encountered an intermittent error where no results were returned when attempting to search for air, car, and hotel. Root cause: The root cause of the incident has been identified to be a service disruption within our third party Global Distribution System (GDS).
 Corrective Actions: N/A

15 July 2026 | 11:04 pm

We identified a functional disruption impacting travel searches via the Galileo and Apollo Global Distribution System (GDS) This issue affected all legacy travel customers in the US2, EU2, AJP1, and Concur Cloud for Public Sector data centers. Users encountered an intermittent error where no results were returned when attempting to search for air, car, and hotel. Workaround: Users may be able to bypass this issue by refreshing the page or retrying search. The Incident Response Team (IRT) has confirmed that the issue was caused by our partner vendor, they have applied a fix, and the service is now being restored. 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.

15 July 2026 | 10:52 pm

We have identified a functional disruption impacting travel searches via the Galileo and Apollo Global Distribution System (GDS). This issue affected all legacy travel customers in the US2, EU2, AJP1, and Concur Cloud for Public Sector data centers. Users encountered an intermittent error where no results were returned when attempting to search for air, car, and hotel. Workaround: Users may be able to bypass this issue by refreshing the page or retrying search. The Incident Response Team (IRT) has confirmed that the issue was caused by our partner vendor, they have applied a fix, and the service is now being restored. 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.