Travel: P1

Update timeline

1. resolved May 13, 2025, 02:55 AM UTC

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

2. resolved May 13, 2025, 03:25 AM UTC

   In the France Data Center, logins through the SAP Concur website were below expected levels. Affected users may have experienced 502 Bad Gateway error intermittently when attempting to login. The Incident Response Team (IRT) updated an application configuration to restore service. 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.

3. resolved May 13, 2025, 03:37 AM UTC

   In the France Data Center, logins through the SAP Concur website are below expected levels. Affected users may have experienced 502 Bad Gateway error intermittently when attempting to login. The Incident Response Team (IRT) updated an application configuration to restore service. We have verified that service performance is stable and will now resolve this 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.

4. resolved May 21, 2025, 04:38 PM UTC

   In the France Data Center, logins through the SAP Concur website are below expected levels. Affected users may experience 502 Bad Gateway error intermittently when attempting to login. Due to human error a test node for a gateway service was indavertently added to a production pool. When a test configuration was applied to the node a defect caused a portion of traffic passing through the gateway service to be blocked - once the issue was identified the node was disabled to restore service. The test node has been removed from the production pool and added to the correct test one. Documentation is being updated to reduce the posibility for similar errors to happen again.