Personalized SAP Concur Open Updates

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

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

    We identified a functional disruption affecting New Concur Travel air searches through the Travelport+ GDS across all Data Centers. New Concur Travel users received a “No flights available” error after selecting “Search,” regardless of the city pairs or travel dates entered. This prevented users from completing air searches and bookings. Car and hotel searches were unaffected. No workaround was available during the incident. While the Incident Response Team (IRT) was investigating, the service self-recovered. The root cause of the incident has been identified to be a service disruption at our third party GDS vendor Travelport. Corrective Actions: N/A

  1. OPI-6287698 : US2 : Travel : Issue Resolved

    We identified a functional disruption impacting New Concur Travel car searches via the Sabre, Amadeus, and Travelport+ Global Distribution Systems (GDS) in the US2 Data Center. When users entered their search criteria and selected Search, the error message, “An unexpected internal error occurred. Please try again.”, was displayed. The error occurred regardless of the city pairs or travel dates selected and prevented successful car bookings. Air and hotel searches were not affected. There was no workaround available for the issue at the time. While the Incident Response Team (IRT) was investigating, the service self-recovered and car search functionality was 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.

  1. OPI-6287698 : US2 : Travel : Issue Status Update

    We identified a functional disruption impacting New Concur Travel car searches via the Sabre, Amadeus, and Travelport+ Global Distribution Systems (GDS) in the US2 Data Center. When users entered their search criteria and selected Search, the error message, “An unexpected internal error occurred. Please try again.”, was displayed. The error occurred regardless of the city pairs or travel dates selected and prevented successful car bookings. Air and hotel searches were not affected. There was no workaround available for the issue at the time. Services have returned to normal operating levels. We are extending our monitoring for an additional 30 minutes to verify continued stability. Once stability is confirmed, the incident will be resolved.

  1. OPI-6287698 : US2 : Travel : Issue Status Update

    We identified a functional disruption impacting New Concur Travel car searches via the Sabre, Amadeus, and Travelport+ Global Distribution Systems (GDS) in the US2 Data Center. When users entered their search criteria and selected Search, the error message, “An unexpected internal error occurred. Please try again.”, was displayed. The error occurred regardless of the city pairs or travel dates selected and prevented successful car bookings. Air and hotel searches were not affected. There was no workaround available for the issue at the time. 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-6287698 : US2 : Travel : Issue Status Update

    We have identified a functional disruption impacting New Concur Travel car searches via the Sabre, Amadeus, and Travelport+ Global Distribution Systems (GDS) in the US2 Data Center. When users enter their search criteria and select Search, the error message “An unexpected internal error occurred. Please try again.” is displayed. The error occurs regardless of the city pairs or travel dates selected and prevents successful car bookings. Air and hotel searches are not affected. Unfortunately, there is no workaround for the issue at this time. The Incident Response Team (IRT) is currently investigating the issue. Our next scheduled update will be in one hour.