Resolved after 2 hours 15 minutes, affecting Request, on October 1, 2025.
Impact as Reported: In the US2 Data Center, completing Concur Requests through the SAP Concur website and SAP Concur mobile app was below expected level. Affected users may have experienced an error: “Sorry, but something went wrong" when attempting to create Concur Request, while other customers might have experienced latency mainly when they attempt to cancel request. Root cause: The root cause of the incident has been identified in a capacity issue occurred during a scheduled maintenance carried on by our cloud services provider, where several servers were mistakenly re-provisioned with lower specifications, causing resources to be exhausted during peak traffic and generating a domino effect that ultimately led to impairment on our DNS capabilities. Corrective Actions: The affected servers were re-provisioned with correct specifications, leading to full service restoration. Several initiatives have been initiated in cooperation with our cloud services provider, with the goal of improving the capacity management for the affected portion of infrastructure, as well as to improve communication prior to maintenance activities. Additionally, monitoring and alerting are being reviewed and improved to allow for faster detection and response.
Affected components
Update timeline
- resolved Oct 01, 2025, 09:44 AM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Oct 01, 2025, 10:27 AM UTC
In the US2 Data Center, completing Concur Request through the SAP Concur website and SAP Concur mobile app is below expected level. Affected users may experience an error: “Sorry, but something went wrong" when attempting to create Concur Request, while other customers might experience latency mainly when they attempt to cancel request. The Incident Response Team (IRT) is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Oct 01, 2025, 11:22 AM UTC
In the US2 Data Center, completing Concur Requests through the SAP Concur website and SAP Concur mobile app was below expected level. Affected users may have experienced an error: “Sorry, but something went wrong" when attempting to create Concur Request, while other customers might have experienced latency mainly when they attempted to cancel request. 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 Oct 01, 2025, 11:48 AM UTC
In the US2 Data Center, completing Concur Requests through the SAP Concur website and SAP Concur mobile app was below expected level. Affected users may have experienced an error: “Sorry, but something went wrong" when attempting to create Concur Request, while other customers might have experienced latency mainly when they attempted to cancel request. As the Incident Response Team was being assembled, the service automatically 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.
- resolved Oct 31, 2025, 09:08 AM UTC
Impact as Reported: In the US2 Data Center, completing Concur Requests through the SAP Concur website and SAP Concur mobile app was below expected level. Affected users may have experienced an error: “Sorry, but something went wrong" when attempting to create Concur Request, while other customers might have experienced latency mainly when they attempt to cancel request. Root cause: The root cause of the incident has been identified in a capacity issue occurred during a scheduled maintenance carried on by our cloud services provider, where several servers were mistakenly re-provisioned with lower specifications, causing resources to be exhausted during peak traffic and generating a domino effect that ultimately led to impairment on our DNS capabilities. Corrective Actions: The affected servers were re-provisioned with correct specifications, leading to full service restoration. Several initiatives have been initiated in cooperation with our cloud services provider, with the goal of improving the capacity management for the affected portion of infrastructure, as well as to improve communication prior to maintenance activities. Additionally, monitoring and alerting are being reviewed and improved to allow for faster detection and response.
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