SAP Concur incident

Travel: P1

Critical Resolved View vendor source →

SAP Concur experienced a critical incident on June 30, 2026 affecting Travel, lasting 2h 15m. The incident has been resolved; the full update timeline is below.

Started
Jun 30, 2026, 10:16 AM UTC
Resolved
Jun 30, 2026, 12:31 PM UTC
Duration
2h 15m
Detected by Pingoru
Jun 30, 2026, 10:16 AM UTC

Affected components

Travel

Update timeline

  1. resolved Jun 30, 2026, 01:55 PM UTC

    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. As the Incident Response Team gathered, the service 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.

  2. resolved Aug 03, 2026, 04:36 PM UTC

    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