SAP Concur Real Time Status

10 July 2025 | 4:45 pm

In the US2 Data Center, travel bookings using the New Concur Travel through the SAP Concur website and SAP Concur mobile app were 10% below expected level. Affected users may have encountered no rates or an error when attempting to complete the travel search and book workflow for all travel segments. The Incident Response Team downgraded a business service tier to a previous version 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.

10 July 2025 | 3:04 pm

After further investigation, we determined a separate issue with a different root cause resulted in the degraded service performance to New Concur Travel customers. The Incident Response Team made this determination during a subsequent review of observability tools and the actions taken to restore service. The issue that affected New Concur Travel customers will be processed and communicated as a separate incident. Travel has been removed as an affected service from this incident and from Concur Open.

10 July 2025 | 1:14 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. An update deployed to the authentication workflow to migrate single sign-on services still using a legacy SAML endpoint to the current one due to a code defect that had not surfaced during testing resulted in some SSO Identity Providers returning an error and in a failed user log. The Incident Response Team deployed an update to use the encoding that was required for these Identity Providers. This resolved the issue and allowed the logins to authenticate successfully. The following corrective actions were identified: -Deployed an update to use the encoding required by some Identity Providers -Add additional tests to validate SSO response matches encoding requirements for all identity providers

10 July 2025 | 11:51 am

In the US2 Data Center, intermittent drops in expense report submits, request submits, and travel bookings impacting both the SAP Concur website and the SAP Concur mobile app was observed. Affected users may have encountered latency while navigating and performing tasks in Concur Expense, Concur Request, and Concur Travel Services. The Incident Response Team (IRT) identified a capacity issue and proceeded to make a configuration change to scale up capacity and 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.

10 July 2025 | 11:38 am

In the US2 Data Center, intermittent drops in expense report submits, request submits, and travel bookings impacting both the SAP Concur website and the SAP Concur mobile app was observed. Affected users may have encountered latency while navigating and performing tasks in Concur Expense, Concur Request, and Concur Travel Services. To ensure continued stability before officially closing the incident, the Incident Response Team has decided to extend the mandatory post-recovery monitoring period for the next 20 minutes to verify stability.