SAP Concur Real Time Status

4 July 2025 | 4:32 am

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

26 June 2025 | 3:28 pm

In the US2 Data Center, logging in via SSO through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced login errors, stating, “Sorry, but we’re having trouble signing you in. SAML message was not properly base 64 encoded” when attempting to log in. 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.

26 June 2025 | 3:10 pm

In the US2 Data Center, logging in via SSO through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced login errors, stating, “Sorry, but we’re having trouble signing you in. SAML message was not properly base 64 encoded” when attempting to log in. 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.

26 June 2025 | 2:38 pm

In the US2 Data Center, logging in via SSO through the SAP Concur website and SAP Concur mobile app is currently unavailable. Affected users may experience login errors, stating, “Sorry, but we’re having trouble signing you in. SAML message was not properly base 64 encoded” when attempting to log in. The Incident Response Team (IRT) is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

26 June 2025 | 2:21 pm

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