Resolved after 1 hour 1 minute, affecting Expense and Request and 1 more, on June 13, 2025.
Impact as Reported: In the Concur Cloud for Public Sector Data Center (CCPS), logging in through the SAP Concur website was unavailable. Affected users s may have experienced the error “ Sorry something went wrong.” or time out "error 502 bad gateway" when trying to login. ConcurGov users may have experienced the error “An error occurred while processing your request” when attempting to login. 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 13, 2025, 02:59 AM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Jun 13, 2025, 03:15 AM UTC
In the Concur Cloud for Public Sector Data Center (CCPS), logging in through the SAP Concur website is currently unavailable. Affected users s may experience the error “ Sorry something went wrong.” or time out error 502 bad gateway" when trying to login. ConcurGov users may experience the error “ An error occurred while processing your request” when attempting to login. The Incident Response Team is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Jun 13, 2025, 03:57 AM UTC
In the Concur Cloud for Public Sector Data Center (CCPS), logging in through the SAP Concur website were unavailable. Affected users s may have experienced the error “ Sorry something went wrong.” or time out error 502 bad gateway" when trying to login. ConcurGov users may have experienced the error “ An error occurred while processing your request” when attempting to login. 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.
- resolved Jun 13, 2025, 04:04 AM UTC
In the Concur Cloud for Public Sector Data Center (CCPS), logging in through the SAP Concur website were unavailable. Affected users s may have experienced the error “ Sorry something went wrong.” or time out error 502 bad gateway" when trying to login. ConcurGov users may have experienced the error “ An error occurred while processing your request” when attempting to login. As the Incident Response Team was making a review, the system self-recovered. 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.
- resolved Jun 19, 2025, 11:16 AM UTC
Impact as Reported: In the Concur Cloud for Public Sector Data Center (CCPS), logging in through the SAP Concur website was unavailable. Affected users s may have experienced the error “ Sorry something went wrong.” or time out "error 502 bad gateway" when trying to login. ConcurGov users may have experienced the error “An error occurred while processing your request” when attempting to login. 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