SAP Concur Real Time Status

23 April 2026 | 3:23 pm

SAP Concur New Travel customers experienced a disruption to the New Concur Travel service. Performance metrics indicated approximately a 90% drop in overall New Concur Travel bookings, while internal testing confirmed the issue symptom to be upstream from the travel search and booking process, specifically affecting access to the New Concur Travel service. Upon signing in, all users were redirected back to the legacy SAP Concur Travel service. Internal testing also indicated refreshing the page or logging out and logging back in, had no effect on bringing users back to the New Concur Travel service. A potential workaround was identified, all affected users may have been able to successfully complete travel searches and bookings despite being in legacy Concur Travel. The Incident Response Team (IRT) rolled back a recent change 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 now be conducted, and a root cause analysis report provided when that investigation is complete.

23 April 2026 | 3:09 pm

SAP Concur New Travel customers experienced a disruption to the New Concur Travel service. Performance metrics indicated approximately a 90% drop in overall New Concur Travel bookings, while internal testing confirmed the issue symptom to be upstream from the travel search and booking process, specifically affecting access to the New Concur Travel service. Upon signing in, all users were redirected back to the legacy SAP Concur Travel service. Internal testing also indicated refreshing the page or logging out and logging back in, had no effect on bringing users back to the New Concur Travel service. A potential workaround was identified, all affected users may have been able to successfully complete travel searches and bookings despite being in legacy Concur Travel. Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

23 April 2026 | 2:19 pm

SAP Concur New Travel customers are experiencing a disruption to the New Concur Travel service. Current performance metrics indicate approximately 90% drop in overall New Concur Travel bookings, while internal testing confirms the issue symptom to be upstream from the travel search and booking process, specifically affecting access to the New Concur Travel service. Upon signing in, all users are being redirected back to the legacy SAP Concur Travel service. Internal testing also indicates refreshing the page or logging out and logging back, does not improve performance. A workaround for this issue is not available at this time. The Incident Response Team is engaged and currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

23 April 2026 | 1:49 pm

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

22 April 2026 | 3:18 pm

SAP Concur New Travel Customers experienced an issue searching for Amtrak rail. All rail travelers searching for a trip via Amtrak would have encountered the following error after entering trip details and clicking the Search Trains button, “An unexpected internal error occurred. Please try search again.” A workaround for this issue was not identified during service degradation. The Incident Response Team (IRT) has received confirmation from Amtrak that an issue on their side has been identified and resolved. 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.