SAP Concur Real Time Status

11 February 2026 | 12:24 pm

Impact as Reported: Some New Concur Travel customers were unable to perform successful travel searches. Our internal monitoring tools measuring successful travel submissions detected a 95% drop in travel submissions. Further investigation confirmed impact to successful travel submissions was caused by an error, "Sorry something went wrong" when attempting to perform an air, car, and hotel travel search. If you experienced impact, you may have been able to successfully perform a search by trying again Root cause: A service configuration update reducing a session timeout for a travel service connections to a central database with the intent of implementing better session management inadvertently resulted in increased session termination and creation, leading to excessive load on the target database and consequent degradation for all services connecting to it. The change was reverted to restore service to normal. Corrective Actions: The following corrective and preventive actions have been identified: The configuration change has been reverted; The pre-release testing is being revised to ensure appropriate load is applied to detect this type of potential issues.

11 February 2026 | 12:18 pm

Impact as Reported: New Concur Travel users experienced an issue completing travel bookings. Affected users may have encountered the following error when attempting to complete their travel booking from the Review and Book page, "Sorry, something went wrong." There was no workaround identified during service disruption. Root cause: A zero downtime patching operation on a vendor managed data store unexpectedly resulted in a temporary loss of connectivity resulting in degradation for services depending on it. Service returned to normal once the operation completed. The vendor has indicated that the issue likely was the result of the operation happening while the data store was under high load and has provided recommendation that are being implemented as preventative actions. Corrective Actions: The following preventative actions have been identified: The zero downtime patching process has been updated to restrict execution to low traffic times and to include validations to ensure no large workload is being processed when the operation takes place; The interval between database connection retries has been increased to reduce the chance of saturating the number of available connections.

21 January 2026 | 3:37 pm

A system outage caused a delay in posting incident communications. The issue has since been resolved, and communications for incidents that occurred during the outage are now being published. Most New Concur Travel customers were unable to perform successful travel searches for 50 minutes. Our internal monitoring tools measuring successful travel submissions detected a 95% drop in travel submissions during the incident. Further investigation confirmed successful travel submissions were impacted by an error, "Sorry something went wrong" after entering your desired search parameters and clicking the Search button when performing air, car, and hotel searches.. If you experienced impact, you may have been able to successfully perform a search by trying again. The Incident Response Team (IRT) quickly took action to revert a recent change to restore service. 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.

9 January 2026 | 4:45 pm

New Concur Travel users experienced an issue completing travel bookings. Our internal observability tools detected a 100% drop in travel bookings for approximately 17 minutes. Affected users may have encountered the following error when attempting to complete their travel booking from the Review and Book page, "Sorry, something went wrong." There was no workaround identified during service disruption. As the Incident Response Team (IRT) was gathering, services self-recovered. We have verified that service performance is stable and will now resolve the 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.

6 January 2026 | 2:25 pm

Expense customers using American Express (AMEX) files for credit card transaction feeds experienced duplicate transactions being imported. Affected users observed duplicate or triplicate AMEX transactions listed in Available Expenses. A duplicate credit card transaction issue was identified and resolved by American Express on 16 December 2025. Since then, American Express has issued reversal credit transactions for all duplicate transactions via customer file feeds. Additionally, the Incident Response Team (IRT) has provided three corrective actions customers are advised to take to clean-up and process all duplicate, triplicate, and reversal credit transactions. We have completed an extended post-recovery corrective measure monitoring period and will now resolve this incident.