SAP Concur incident
Expense, Travel, Invoice, Request, Imaging, Analysis/Intelligence: P1
Resolved after 19 minutes, affecting Analysis/Intelligence and Expense and 1 more, on June 12, 2025.
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 "503 Service Unavailable" error when attempting to log in. Root cause: A configuration defect introduced by human error resulted in a subset of containerized services required by the log in process being improperly set up to redistribute workload. Consequently during a routine maintenance rotating the nodes hosting these services containers the workloads were left without sufficient capacity to support their function; service returned to normal as soon as the maintenance operation was completed and capacity restored. Corrective Actions: The following corrective and preventive actions have been identified: - the defective configuration has been rectified for the affected services; - management of the impacted configuration was found to be using a deprecated deployment mechanism lacking automated checks introduced to prevent the release of this class of defects: this is being updated to use the current and approved management pipeline - the operation team managing the underlying infrastructure is researching the introduction of additional gating mechanisms to prevent the utilization of deprecated deployment mechanisms.
Affected components
Update timeline
- resolved Jun 12, 2025, 06:00 AM UTC
We wish to inform you that we identified and promptly resolved a degradation affecting your service. After completing a post resolution monitoring period, we have confirmed that service is operating at a normal and stable level so have resolved this incident. In the US2 Data Center, logins through the SAP Concur website and SAP Concur mobile app was below expected level. Affected users may have experienced "503 Service Unavailable" error when attempting to log in. As the Incident Response Team (IRT) was gathering, the issue self-recovered.
- resolved Jun 19, 2025, 11:19 AM UTC
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 "503 Service Unavailable" error when attempting to log in. Root cause: A configuration defect introduced by human error resulted in a subset of containerized services required by the log in process being improperly set up to redistribute workload. Consequently during a routine maintenance rotating the nodes hosting these services containers the workloads were left without sufficient capacity to support their function; service returned to normal as soon as the maintenance operation was completed and capacity restored. Corrective Actions: The following corrective and preventive actions have been identified: - the defective configuration has been rectified for the affected services; - management of the impacted configuration was found to be using a deprecated deployment mechanism lacking automated checks introduced to prevent the release of this class of defects: this is being updated to use the current and approved management pipeline - the operation team managing the underlying infrastructure is researching the introduction of additional gating mechanisms to prevent the utilization of deprecated deployment mechanisms.
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.
Amazon Web Services