Personalized SAP Concur Open Updates

Personalized up-to-the-minute service availability and performance information

  1. OPI-6235278 : US2 | EU2 | CONCUR CLOUD FOR PUBLIC SECTOR : Travel : Root Cause Analysis

    Impact as Reported: 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. 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

  1. OPI-6251235 : US2 | EU2 | CONCUR CLOUD FOR PUBLIC SECTOR : Travel : Root Cause Analysis

    Impact as Reported: All Sabre customers in the US2,EU2 and Concur Cloud for Public Sector Data Centers Data Centers experienced approximately 95% functional degradation when attempting to book Hilton properties. At the Review and Book stage, users may have encountered the error: “We are unable to complete your booking at this time. Please wait and try again later.” This error occurred after selecting Book and Continue, preventing completion of the reservation. Root cause: The root cause of the incident has been identified to be a service disruption at our third party GDS partner Sabre. Corrective Actions: N/A

  1. OPI-6257695 : US2 | EU2 | CONCUR CLOUD FOR PUBLIC SECTOR | APJ1 : Travel : Root Cause Analysis

    Impact as Reported:
 All Travelport customers in the US2, EU2, Concur Cloud for Public Sector, and APJ1 Data Centers experienced functional disruption when trying to search for car rentals with corporate rates. After entering search details and clicking the Search button, all travellers received a ‘No rates found’ message. Non corporate rates were available during the outage.
 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

  1. OPI-6267869 : US2 : Expense | Travel | Imaging | Analysis/Intelligence | Mobile : Issue Resolved

    The incident impacted only the US2 Data center. APJ1 and Concur Cloud for Public Sector (CCPS) data centers was not affected by this incident. We apologize for the inconvenience. All other details provided in the resolved communication remain unchanged. When users attempted to access the Concur application, they received the following error message: "Sorry, Concur is currently unavailable." The error was displayed before the login page loaded, preventing users from accessing the application. Users who were already logged in during the impact window were logged out of the system and encountered the same error when attempting to access the Concur application again. The Incident Response Team (IRT) investigated the issue and identified the cause as a network connectivity issue on our hyper-scaler. The appropriate teams implemented corrective actions 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 continue, and a Root Cause Analysis (RCA) report will be provided upon completion of the investigation.

  1. OPI-6267869 : US2 : Expense | Travel | Imaging | Analysis/Intelligence | Mobile : Issue Resolved

    The incident impacted only the US2 Data center. APJ1 and Concur Cloud for Public Sector (CCPS) data centers was not affected by this incident. We apologize for the inconvenience. All other details provided in the resolved communication remain unchanged. When users attempted to access the Concur application, they received the following error message: "Sorry, Concur is currently unavailable." The error was displayed before the login page loaded, preventing users from accessing the application. Users who were already logged in during the impact window were logged out of the system and encountered the same error when attempting to access the Concur application again. The Incident Response Team (IRT) investigated the issue and identified the cause as a network connectivity issue on our hyper-scaler. The appropriate teams implemented corrective actions 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 continue, and a Root Cause Analysis (RCA) report will be provided upon completion of the investigation.