Travel: P1

Update timeline

1. investigating Oct 26, 2026, 07:11 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Oct 26, 2026, 07:46 PM UTC

   We have identified a service degradation affecting the Concur Travel service. The extent of the customer impact is currently under investigation. Additional details regarding customer impact will be provided as they become available. This issue is intermittently affecting travel searches in New Concur Travel. After entering search criteria and clicking the Search button, users may receive the error message: "Sorry, something went wrong." When this error occurs, search results are not returned. Legacy Travel is not impacted by this issue. Workaround: We have identified a potential workaround. Because the issue is intermittent, users may be able to successfully complete their travel searches after making multiple attempts. The Incident Response Team (IRT) has engaged additional support teams and is currently reviewing internal logs to determine the root cause. In parallel, the team is restarting service pods in an effort to restore normal functionality. Our next scheduled update will be provided within one hour, or sooner if a significant change in status occurs.

3. resolved Oct 26, 2026, 08:41 PM UTC

   We identified and resolved a service degradation affecting the Concur Travel service. Full Customer Base Impact will be provided when available. This issue was intermittently affecting travel searches in New Concur Travel. After entering search criteria and clicking the Search button, users may have received the error message: "Sorry, something went wrong." When this error occurred, search results were not returned. Legacy Travel was not impacted by this issue. Workaround: We identified a potential workaround. Because the impact was intermittent, users may have been able to successfully complete their travel searches after making multiple attempts. Services have returned to normal operating levels. We will continue to monitor for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

4. resolved Oct 26, 2026, 09:12 PM UTC

   We identified and resolved a service degradation affecting the Concur Travel service. Full Customer Base Impact will be provided when available. This issue was intermittently affecting travel searches in New Concur Travel. After entering search criteria and clicking the Search button, users may have received the error message: "Sorry, something went wrong." When this error occurred, search results were not returned. Legacy Travel was not impacted by this issue. Workaround: We identified a potential workaround. Because the impact was intermittent, users may have been able to successfully complete their travel searches after making multiple attempts. The Incident Response Team took action to to upgrade an instance type to restore service. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will be conducted, and a root cause analysis report provided when that investigation is complete.