SAP Concur Real Time Status

21 September 2026 | 2:40 am

Impact as Reported: 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. Root Cause: The incident was caused by high concurrency against a profile data retrieval process that is executed as part of real-time profile synchronization. Under elevated demand, the process experienced database lock contention on temporary data structures, causing requests to block one another and resulting in a buildup of queued sessions. This degraded response times for dependent services and led to customer-facing failures.Analysis determined that the issue primarily affected requests configured to bypass cached profile data and instead perform a real-time profile refresh before profile retrieval. This design, intended to ensure the most current profile information is returned, significantly increased the number of concurrent executions of the affected database process. The analysis concluded that customer impact occurred because dependent services timed out waiting for profile responses; those profile responses were delayed by blocked database sessions; the blocking was caused by locking behavior within the database process under high concurrency; and the high concurrency was driven by real-time profile synchronization requests. The condition self-resolved as request volume and contention levels decreased. Preventive Actions: The following preventive and corrective actions were identified: Remove locking-prone temporary data structures from the affected database process to eliminate unnecessary contention under high concurrency. Reduce unnecessary executions of the profile retrieval process during synchronization workflows where the data is not required. Decrease reliance on real-time profile synchronization for profile retrieval scenarios that can be served without an immediate refresh. Improve monitoring and alerting for database blocking, lock contention, and concurrency trends to enable earlier detection and response. Incident Mitigation: No immediate corrective action was required during the event, as service recovered automatically once contention subsided. The actions above have been identified to reduce the likelihood and impact of recurrence.

21 September 2026 | 2:34 am

Impact as Reported: We identified a functional degradation that impacted hotel bookings via the Travelport+ GDS. This issue affected all US2 and EU2 Data Centre customers booking hotels through the Travelport+ GDS. After entering the desired hotel search parameters and clicking "Search," a list of available hotels was displayed. Users were able to successfully view available room options and rates. However, after selecting a room and clicking "Book and Continue" or "Reserve," users may have encountered error code HL750087, which prevented them from completing the hotel booking. The issue was reproduced across multiple hotels when booking through Travelport+. 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

16 September 2026 | 3:06 am

Impact as reported: In the US2 Data Center, a service degradation impacted access to Concur services, including Expense, Travel Request, Travel, Invoice, and Analysis and Intelligence. After logging in, users are encountering the following error: “You are currently not set up to use any Concur products. Contact your Concur Administrator for assistance.” Users already logged in were not impacted. Root Cause: The incident occurred when all instances of a service invoked while initiating user sessions after log in were restarted during routine infrastructure activity and were unable to successfully start, resulting in a temporary service outage and downstream customer-facing errors. Although a legacy access permission had been removed earlier, the issue did not surface immediately because existing instances continued operating normally. The outage occurred only after all instances restarted and attempted to validate access using an outdated configuration path, which prevented them from becoming operational. The root cause was an unintended dependency on a legacy configuration path that remained active after a related access change. To permanently address the issue, the service configuration was updated to use a supported, actively used validation path and the legacy dependency was removed. As an interim measure, the required access was restored to ensure service stability while the permanent fix was implemented, tested, and deployed. Corrective Actions: The following preventive and corrective actions were identified: Update service configuration to use only supported secret paths for startup validation and eliminate reliance on legacy validation mechanisms. Implement automated regression testing to verify that only approved secret locations are referenced by the application. Add validation checks to ensure application configuration changes are reviewed against secret-management and access-policy changes before deployment. Enhance change management procedures to identify and assess dependencies between application configurations and access-control modifications. Introduce proactive production monitoring and alerting for service startup failures, unavailable service instances, and repeated initialization errors. Establish direct availability alerts so operational teams are notified of service outages before downstream systems are affected. Validate secret-access configurations and application behavior in pre-production environments whenever secret-management policies or permissions are modified. Reduce single points of failure by ensuring that a denied request to a nonessential or legacy configuration path cannot prevent the entire service from starting. Maintain temporary access restoration procedures as a contingency measure during rollout of configuration-related fixes and remove temporary permissions once the permanent solution is confirmed in production.

7 September 2026 | 12:56 pm

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

5 September 2026 | 10:21 pm

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.