SAP Concur Real Time Status

15 September 2025 | 2:04 am

Impact as Reported: In the US2, EU2, and APJ1 Data Centers, car and hotel searches using the Apollo, Worldspan and Galileo GDS service were 10% below expected level. Affected users may have encountered an error “We’re sorry. We encountered an issue that prevented us from completing your request” when attempting to perform a search for car and hotel. 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

15 September 2025 | 2:01 am

Impact as Reported: In the US2 Data Center, travel searches in New Concur Travel were 40 % below expected level. Affected users may have experienced an error, “No location found” when attempting to complete travel search criteria. A workaround was not identified Root cause: The deployment of a new version of a travel micro service triggered an autoscaling operation on the cluster hosting it. Another service hosted on the same cluster entered a degraded state when new serving instances were being provisioned due to the auto scaling, as new instances were put into service before having completed their boot strap due to a defect on a life check end point and given the load levels at the time of the operation started receiving traffic before being ready. The resulting errors when calling the service, combined with an aggressive retry logic on the client side, caused the calls volume to spike, further exacerbating the service degradation. The incident response team manually stopped the service and manually scaled it to enable service restoration. Corrective Actions: The following corrective and preventative actions were identified: Stopped all requests and manually increased new instances to remediate the issue Update the health checks to fix the defect and ensure seving instances only start receiving traffic once fully ready Implement a circuit breaker to prevent retry logic to overwhelm the service in case of degradation.

11 September 2025 | 3:40 pm

In the US2, EU2, and Concur Cloud for Public Sector Data Centers, customers using the American Express GL1025 file for credit card transaction feeds may have experienced issues with incorrect transaction labeling for transactions posted on or before September 2. While it was confirmed that American Express deployed a fix on September 2, preventing further impact, incident communications will continue until clean up actions have been executed. Affected users may see payment transactions displayed to employees either with no vendor name or with an "unknown" vendor, while certain fee types may be incorrectly classified as cash advances. A potential workaround for this issue has been identified. Credit card administrators for the impacted customers may be able to hide the impacted transactions or reach out to the Concur Support rep so that they can hide them on your behalf. Additionally, in some situations, it may be possible to create an audit rule to prevent the inclusion of impacted transactions in expense reports.
 The Incident Response Team (IRT) has begun clean-up actions of reclassifying affected transactions and assigning them to the correct categories. Due to the complexity of the issue and sensitivity of the impacted data, the IRT is executing the remediation process on a customer-by-customer basis instead of using a mass automation mentioned in previous incident communications. The remediation process includes reclassifying unassigned transactions, adjusting them to the expected status and visibility based on customers' individual configurations, such as hidden or released in Available Expenses. The IRT advises for customers who have remaining affected transactions, to create a case or update their existing case providing approval for the IRT to complete the remediation process for their entity.
We will post the next incident communication at or before 9:00PM UTC on 24 September 2025.

11 September 2025 | 9:02 am

Impact as Reported: In the US2 Data Center, access to Concur Expense, Concur Request, and Concur Travel through the SAP Concur website and SAP Concur mobile app was below expected level. After logging in, affected users may have encountered a home page with tile alerts indicating service disruption. Root cause: The incident response team has identified that an update to a network component part of the home page service inadvertently introduce a defect causing increased memory utilization that had not manifested during pre-production testing. The increased memory utilization briefly caused some of the calls processed thorugh the home page service to time out and result in customer disurption until the service capacity automatically scaled up and restored service.

6 September 2025 | 2:35 pm

In the US2, EU2, and APJ1 Data Centers, car and hotel searches using the Apollo, Worldspan and Galileo GDS service were 10% below expected level. Affected users may have encountered an error “We’re sorry. We encountered an issue that prevented us from completing your request” when attempting to perform a search. A workaround for this issue was not determined. As the Incident Response Team (IRT) was gathering, services recovered. Upon investigation, the IRT determined that the errors were related to a third party vendor issue. An incident ticket will be opened with Travelport, and the IRT will work with the vendor to determine what may have been the root cause. 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.