SAP Concur incident

Expense, Travel, Invoice, Request, Imaging, Analysis/Intelligence: P1

Resolved after 21 minutes, affecting Analysis/Intelligence and Expense and 1 more, on April 30, 2025.

resolved May 15, 2025, 04:01 PM UTC

In the APJ1 Data Center, access through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced an error, “Sorry, Concur is unavailable” when logging in. A gateway service deployed an update to its secondary and primary clusters. The secondary cluster completed the update and new traffic was successfully gradually migrated to it. Once the primary cluster was updated as well, traffic was inadvertently migrate back at once rather than in a gradual fashion, subsequently resulting in connection failures. The Incident Response Team identified that the update on the original primary cluster caused issues resulting in the incident; the updates were reverted to restore connectivity to services. The following corrective and preventative actions were identified: Reverted the update to restore connectivity Update the deployment documentation to ensure traffic moves between clusters are always performed in a phased manner.

Started
Apr 30, 2025, 06:57 PM UTC
Resolved
Apr 30, 2025, 07:18 PM UTC
Duration
21m
Detected by Pingoru
Apr 30, 2025, 06:57 PM UTC

Affected components

Analysis/IntelligenceExpenseImagingInvoiceRequestTravel

Update timeline

  1. resolved Apr 30, 2025, 07:20 PM UTC

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

  2. resolved Apr 30, 2025, 07:45 PM UTC

    In the APJ1 Data Center, access through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced an error, “Sorry, Concur is unavailable” when logging 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.

  3. resolved Apr 30, 2025, 07:57 PM UTC

    In the APJ1 Data Center, access through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced an error, “Sorry, Concur is unavailable” when logging 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.

  4. resolved May 15, 2025, 02:28 AM UTC

    In the US,EU2 and APJ Data Centers, air bookings via Galileo, worldspan and Apollo GDS vendors through the SAP Concur website and SAP Concur mobile app were unavailable. Affected users may have encountered the following error message: “Sorry, we are unable to return search results, which may be due to: your company’s travel policy...” when attempting to perform air 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.

  5. resolved May 15, 2025, 04:01 PM UTC

    In the APJ1 Data Center, access through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced an error, “Sorry, Concur is unavailable” when logging in. A gateway service deployed an update to its secondary and primary clusters. The secondary cluster completed the update and new traffic was successfully gradually migrated to it. Once the primary cluster was updated as well, traffic was inadvertently migrate back at once rather than in a gradual fashion, subsequently resulting in connection failures. The Incident Response Team identified that the update on the original primary cluster caused issues resulting in the incident; the updates were reverted to restore connectivity to services. The following corrective and preventative actions were identified: Reverted the update to restore connectivity Update the deployment documentation to ensure traffic moves between clusters are always performed in a phased manner.

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.

Add your stack →