SAP Concur Real Time Status

13 November 2026 | 1:07 am

A service disruption was identified and resolved affecting the travel search functionality for Legacy Travel customers in the US2, EU2, and APJ1 Data Centers. Affected users encountered the error message "We encountered an issue that prevented us from completing your request." upon submitting search criteria in the travel wizard. The disruption impacted car searches via the Apollo, Galileo, and Travelport+ Global Distribution Systems (GDS). New Concur Travel customers were not affected and retained full search and booking functionality throughout the incident period. Workaround: A workaround for this issue was not available during service impact. As the Incident Response Team (IRT) was gathering, the service self recovered. 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.

10 November 2026 | 9:17 am

Impact as Reported: We identified and resolved a service degradation affecting the Concur Travel service. Full Customer Base Impact will be provided when available. This issue was intermittently affecting travel searches in New Concur Travel. After entering search criteria and clicking the Search button, users may have received the error message: "Sorry, something went wrong." When this error occurred, search results were not returned. Legacy Travel was not impacted by this issue. Root cause: The incident was caused by a capacity constraint within a backend travel service. During a period of sustained demand, requests became concentrated on a portion of the available resources rather than being distributed as intended. This created a bottleneck that reduced the service's ability to respond to requests, resulting in intermittent search failures for customers. The Incident Response Team increased available capacity to alleviate the bottleneck and restore normal service operation. Corrective Actions: The following corrective and preventative actions were identified 1. Increased service capacity to immediately alleviate the bottleneck and restore normal service operation. 2. Improve workload distribution across available resources to prevent traffic from concentrating on a limited subset of service capacity. 3. Enhance monitoring and alerting capabilities to enable earlier detection of capacity constraints and allow remediation before customer impact occurs.

10 November 2026 | 9:16 am

Impact as Reported: We identified and resolved a service degradation affecting the Concur Travel service. Full Customer Base Impact will be provided when available. This issue was intermittently affecting travel searches in New Concur Travel. After entering search criteria and clicking the Search button, users may have received the error message: "Sorry, something went wrong." When this error occurred, search results were not returned. Legacy Travel was not impacted by this issue. Root cause: The incident was caused by a capacity constraint within a backend travel service. During a period of sustained demand, requests became concentrated on a portion of the available resources rather than being distributed as intended. This created a bottleneck that reduced the service's ability to respond to requests, resulting in intermittent search failures for customers. The Incident Response Team increased available capacity to alleviate the bottleneck and restore normal service operation. Corrective Actions: The following corrective and preventative actions were identified 1. Increased service capacity to immediately alleviate the bottleneck and restore normal service operation. 2. Improve workload distribution across available resources to prevent traffic from concentrating on a limited subset of service capacity. 3. Enhance monitoring and alerting capabilities to enable earlier detection of capacity constraints and allow remediation before customer impact occurs.

5 November 2026 | 5:19 am

Impact as Reported: A service disruption has been identified and resolved affecting travel search functionality for Legacy Travel customers in the US2 Data Center. Affected users encountered the error message "We're Sorry… We encountered an issue that prevented us from completing your request" upon submitting search criteria in the travel wizard. The disruption impacted searches for air, hotel, and car travel segments across all Global Distribution Systems (GDSs). New Concur Travel customers were not affected and retained full search and booking functionality throughout the incident period. Root cause: A core database instance experienced a resource constraint during an operation, resulting in service degradation for customers. The issue was traced to a configuration setting that had not been applied as intended during a previous infrastructure update, limiting the database's capacity to support certain processing activities. The configuration has since been corrected, and enhancements have been made to the provisioning process to reduce the likelihood of recurrence. Corrective Actions: The following corrective and preventative actions were identified: 1. Corrected the database configuration to restore the intended operating parameters. 2. Enhance documentation to clearly identify the required configuration adjustment and reduce the risk of omission during future infrastructure updates. 3. Expand automated validation controls to verify the affected setting is applied consistently during future infrastructure deployments

29 October 2026 | 5:08 am

Impact as Reported: We have identified a service degradation impacting Concur Travel. This issue was impacting all air, car, and hotel booking submissions via the Sabre Global Distribution System (GDS) in all Data Centers. Air, car, and hotel searches could be successfully performed. However, when attempting to finalize and submit the booking, an error was presented. This error prevented the successful submission of travel bookings. Additionally, attempts to modify or cancel existing bookings could not be successfully executed. Important: Should an error have been encountered while finalizing a hotel booking, it was important to refrain from re-attempting the booking, as it was possible this could have resulted in duplicate bookings. Please reach out to the hotel directly to prevent potential no show charges if hotel bookings were re-attempted during the time of impact. 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 Action N/A