Personalized SAP Concur Open Updates

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

  1. OPI-6008583 : US2 | EU2 | APJ1 : Travel : Root Cause Analysis

    Impact as Reported: In the US,EU2 and APJ Data Centers, air bookings via Galileo, Worldspan and Apollo GDS vendors through the SAP Concur website and SAP Concur mobile app were unavailable. Affected users may have encountered the following error message: “Sorry, we are unable to return search results, which may be due to: your company’s travel policy...” when attempting to perform air bookings. Root cause: The root cause of the incident has been identified to be a service disruption at one of our third party GDS vendors.  Corrective Actions: N/A

  1. OPI-6002076 : US2 | EU2 | APJ1 : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence : Root Cause Analysis

    In the EU2, US2, and APJ1 Data Centers, logging in through the SAP Concur website and SAP Concur mobile app was unavailable. The affected users would get “Sorry, something went wrong” upon trying to access SAP Concur services. An outage on a geo-blocking service responsible for the scanning and validation of incoming traffic origin, necessary to prevent access from embargoed countries, caused all inbound traffic to be blocked. The reason behind the failure was a version upgrade on a core component of the geo-blocking service that resulted in missing certificates information and consequent clients connection failure to both the primary and the back-up endpoints. This resulted in the CTE authentication service to prevent access for all users. The proxy service responsible for handling the connection between CT&E and the geo-blocking service has been updated to a new version that allows dynamic parameters to be used for the TLS handshake, removing the dependency on the information that went missing on the certificate, hence removing the dependency that caused the connection to the geo-blocking back up endpoints to fail.

  1. OPI-6008583 : US2 | EU2 | APJ1 : Travel : Issue Resolved

    In the US,EU2 and APJ Data Centers, air bookings via Galileo, worldspan and Apollo GDS vendors through the SAP Concur website and SAP Concur mobile app were unavailable. Affected users may have encountered the following error message: “Sorry, we are unable to return search results, which may be due to: your company’s travel policy...” when attempting to perform air bookings. The services automatically self-recovered as the Incident Response Team (IRT) was investigating. The IRT received communication from Travelport indicating a service disruption. The IRT will follow-up with Travelport regarding the Root Cause Analysis. 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.

  1. OPI-6008583 : US2 | EU2 | APJ1 : Travel : Issue Status Update

    In the US,EU2 and APJ Data Centers, air bookings via Galileo, worldspan and Apollo GDS vendors through the SAP Concur website and SAP Concur mobile app were unavailable. Affected users may have encountered the following error message: “Sorry, we are unable to return search results, which may be due to: your company’s travel policy...” when attempting to perform air bookings. 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.

  1. OPI-6008583 : US2 | EU2 | APJ1 : Travel : Issue Status Update

    In the US,EU2 and APJ Data Centers, air bookings via Galileo, worldspan and Apollo GDS vendors through the SAP Concur website and SAP Concur mobile app are currently unavailable. Affected users may encounter the following error message: “Sorry, we are unable to return search results, which may be due to: your company’s travel policy...” when attempting to perform air bookings. The Incident Response Team (IRT) is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.