SAP Concur Real Time Status

3 December 2025 | 4:59 am

In the US2 and EU2 Data Centers, travel searches and bookings in the new Concur Travel using the Sabre GDS were unavailable. Affected users may have encountered the following errors, "No flights available" Or "We weren't able to load this content", when attempting to perform any travel search. The Incident Response Team (IRT) has received confirmation that the root cause resides on Sabre’s end and that Sabre has taken action to restore the service. 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.

3 December 2025 | 4:45 am

In the US2 and EU2 Data Centers, travel searches and bookings in the new Concur Travel using the Sabre GDS were unavailable. Affected users may have encountered the following errors, "No flights available" Or "We weren't able to load this content", when attempting to perform any travel search. 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.

3 December 2025 | 3:52 am

In the US2 and EU2 Data Centers, travel searches and bookings in the new Concur Travel using the Sabre GDS is currently unavailable. Affected users may encounter the following errors, "No flights available" Or "We weren't able to load this content", when attempting to perform any travel search. The Incident Response Team (IRT) is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

3 December 2025 | 3:24 am

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

1 December 2025 | 12:22 pm

New Concur Travel customers may have experienced an error message when attempting to submit a travel booking. Additionally, some users may have experienced latency when attempting to complete a booking or perform tasks. It may have been possible to complete bookings and tasks with multiple attempts. As the Incident Response Team (IRT) was gathering, services recovered. 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.