SAP Concur Real Time Status

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

29 October 2026 | 5:02 am

Impact as Reported: We identified an intermittent service degradation that affected logins via mobile device. This issue was impacting approximately 1% of customers in the US2 Data Center. When attempting to access the SAP Concur site via mobile device, users may have received the error message, "Sorry, something went wrong," after entering their login credentials. When this error occurred, the login attempted could not be completed during that session. Additionally, it was possible some users may have experienced increased latency after entering their username and password. Users who were already logged in were able to continue working without interruption. Root cause: A code defect within a travel service caused database connections to remain open after processing had completed. Over time, these unreleased connections consumed an increasing amount of database capacity until available resources were exhausted. As the service detected processing delays, it automatically scaled up, creating additional database demand and accelerating the degradation. The Incident Response Team restored service by transitioning operations to healthy infrastructure, which restored available database capacity and resolved the issue. Corrective Actions: The following corrective and preventative actions were identified: 1. Update the travel service to ensure database connections are properly released and to enforce connection limits and maximum connection age thresholds. 2. Update the travel service's autoscaling configuration to establish upper scaling limits and reduce the risk of excessive demand on shared database resources during service degradation events. 3. Enhance monitoring and alerting to provide visibility into database connection utilization and enable earlier detection of abnormal usage patterns. Optimized the travel service's database interactions to reduce unnecessary load and improve overall efficiency.

26 October 2026 | 4:12 pm

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. Workaround: We identified a potential workaround. Because the impact was intermittent, users may have been able to successfully complete their travel searches after making multiple attempts. The Incident Response Team took action to to upgrade an instance type 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 be conducted, and a root cause analysis report provided when that investigation is complete.

26 October 2026 | 3:41 pm

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. Workaround: We identified a potential workaround. Because the impact was intermittent, users may have been able to successfully complete their travel searches after making multiple attempts. Services have returned to normal operating levels. We will continue to monitor for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

26 October 2026 | 2:46 pm

We have identified a service degradation affecting the Concur Travel service. The extent of the customer impact is currently under investigation. Additional details regarding customer impact will be provided as they become available. This issue is intermittently affecting travel searches in New Concur Travel. After entering search criteria and clicking the Search button, users may receive the error message: "Sorry, something went wrong." When this error occurs, search results are not returned. Legacy Travel is not impacted by this issue. Workaround: We have identified a potential workaround. Because the issue is intermittent, users may be able to successfully complete their travel searches after making multiple attempts. The Incident Response Team (IRT) has engaged additional support teams and is currently reviewing internal logs to determine the root cause. In parallel, the team is restarting service pods in an effort to restore normal functionality. Our next scheduled update will be provided within one hour, or sooner if a significant change in status occurs.