Resolved after 50 minutes, affecting Travel, on January 20, 2026.
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.
Affected components
Update timeline
- resolved Jan 21, 2026, 09:37 PM UTC
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.
- resolved Feb 11, 2026, 06:24 PM UTC
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.
Your product runs on more than SAP Concur
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services