SAP Concur Real Time Status

6 May 2025 | 6:51 am

Impact as Reported: In the EU2, US2, and APJ1 Data Centers, logging in through the SAP Concur website and SAP Concur mobile app was unavailable. The affected users would get “Sorry, something went wrong” upon trying to access SAP Concur services. Root cause: An outage within the service responsible for the scanning and validation of incoming traffic origin, necessary to prevent access from embargoed countries, has caused all the inbound traffic to be blocked. The reason behind the failure and the lack of an efficient failover mechanism are still under investigation. Corrective Actions: N/A

6 May 2025 | 3:03 am

Impact as Reported: In the US2 Data Center, logins through the SAP Concur website and SAP Concur mobile app were below expected level. Affected users may have experienced intermittent errors when attempting to log in. Root cause: As part of a standard maintenance operation users were being moved from a container cluster providing gateway services to a new cluster. The service team performing the operation failed to realize that the new cluster was not scaling up capacity quickly enough to support the incoming load, resulting in latency and timeouts. The incident response team moved all users back to the original cluster, restoring service to normal levels. The migration operation was then completed after manually scaling the capacity of the new cluster to match the old one. Corrective Actions: Add a step to the deployment process to manually scale the secondary cluster to the same as production instead of relying on auto-scaling.

6 May 2025 | 3:00 am

Impact as Reported: In the US2 Data Center, logins through the SAP Concur website and SAP Concur mobile app were below expected level. Affected users may have experienced intermittent errors when attempting to log in. Root cause: As part of a standard maintenance operation users were being moved from a container cluster providing gateway services to a new cluster. The service team performing the operation failed to realize that the new cluster was not scaling up capacity quickly enough to support the incoming load, resulting in latency and timeouts. The incident response team moved all users back to the original cluster, restoring service to normal levels. The migration operation was then completed after manually scaling the capacity of the new cluster to match the old one. Corrective Actions: Add a step to the deployment process to manually scale the secondary cluster to the same as production instead of relying on auto-scaling.

28 April 2025 | 5:49 pm

In the US2 Data Center, air travel searches in the new Concur Travel, using the Sabre and Amadeus GDS services through the SAP Concur website was below expected level. Affected users may have experienced an error, “AR-40000” when attempting to perform travel searches. New Concur Travel users should now be able to search for car and hotel. As the Incident Response Team was investigating, Issue service self-recovered. 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.

28 April 2025 | 5:29 pm

In the US2 Data Center, air travel searches in the new Concur Travel, using the Sabre and Amadeus GDS services through the SAP Concur website was below expected level. Affected users may have experienced an error, “AR-40000” when attempting to perform travel searches. New Concur Travel users should now be able to search for car and hotel. 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.