SAP Concur experienced a critical incident on January 9, 2026 affecting Travel, lasting 17m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Jan 09, 2026, 10:45 PM UTC
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.
- resolved Feb 11, 2026, 06:18 PM UTC
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.