Resolved after 1 hour 57 minutes, affecting Travel, on June 24, 2025.
Impact as Reported: In the US2 Data Center, travel bookings in the new Concur Travel through the SAP Concur website and SAP Concur mobile app were unavailable. Affected New Concur Travel users may have experienced being reverted back to the Legacy Concur Travel page when attempting to make travel bookings. Root cause: A configuration defect inadvertently introduced in a service supporting the routing of users to either New or Legacy Concur Travel caused connections time out and resulted to all users to be routed to the legacy version. The issue was initially mitigated by increasing capacity of the impacted service to address the time outs, and ultimately resolved by rectifying the incorrect configuration. Corrective Actions: The following corrective actions were identified: The configuration defect was rectified The impacted configuration items has been moved to a different configuration store to prevent it from being inadvertently modified The design of the service configuration is being reviewed to identify and address any other potential issues Service restart playbook is being updated to ensure additional capacity is added during restart to eliminate potential "thundering herd" issues
Affected components
Update timeline
- resolved Jun 24, 2025, 02:00 PM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Jun 24, 2025, 02:23 PM UTC
In the US2 Data Center, travel bookings in the new Concur Travel through the SAP Concur website and SAP Concur mobile app are unavailable. Affected users may see the Legacy Concur Travel booking screen and will not be able to make travel bookings using the new Concur Travel experience. The Incident Response Team (IRT) is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Jun 24, 2025, 03:16 PM UTC
In the US2 Data Center, travel bookings in the new Concur Travel through the SAP Concur website and SAP Concur mobile app are currently unavailable. Affected New Concur Travel users may experience being reverted back to the Legacy Concur Travel page when attempting to make travel bookings. The Incident Response Team (IRT) continues in taking action to increase space and capacity on a business service tier. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Jun 24, 2025, 03:28 PM UTC
In the US2 Data Center, travel bookings in the new Concur Travel through the SAP Concur website and SAP Concur mobile app were unavailable. Affected New Concur Travel users may have experienced being reverted back to the Legacy Concur Travel page when attempting to make travel bookings. 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.
- resolved Jun 24, 2025, 03:49 PM UTC
In the US2 Data Center, travel bookings in the new Concur Travel through the SAP Concur website and SAP Concur mobile app were unavailable. Affected New Concur Travel users may have experienced being reverted back to the Legacy Concur Travel page when attempting to make travel bookings. The Incident Response Team (IRT) restarted a business service tier 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.
- resolved Jul 04, 2025, 09:32 AM UTC
Impact as Reported: In the US2 Data Center, travel bookings in the new Concur Travel through the SAP Concur website and SAP Concur mobile app were unavailable. Affected New Concur Travel users may have experienced being reverted back to the Legacy Concur Travel page when attempting to make travel bookings. Root cause: A configuration defect inadvertently introduced in a service supporting the routing of users to either New or Legacy Concur Travel caused connections time out and resulted to all users to be routed to the legacy version. The issue was initially mitigated by increasing capacity of the impacted service to address the time outs, and ultimately resolved by rectifying the incorrect configuration. Corrective Actions: The following corrective actions were identified: The configuration defect was rectified The impacted configuration items has been moved to a different configuration store to prevent it from being inadvertently modified The design of the service configuration is being reviewed to identify and address any other potential issues Service restart playbook is being updated to ensure additional capacity is added during restart to eliminate potential "thundering herd" 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