Resolved after 2 hours 30 minutes, affecting Expense, on March 10, 2025.
Impact as Reported: In the Concur Cloud for Public Sector (CCPS) Data Center, access to Concur Expense through the SAP Concur website is 25% below expected level. Affected users may encounter extreme latency when attempting to access Concur Expense or when attempting to create and submit expense reports. Users may be able to complete tasks provided they wait for the latency to complete. Root cause: An Expense service experienced higher latency than normal, leading to performance degradation when attempting to create an expense report. The Incident Response Team restarted an application pool to restore the service to normal levels. We are continuing the investigation into the root cause of the higher latency issue. Corrective Actions: Corrective actions will be determined once root cause has been fully identified.
Affected components
Update timeline
- resolved Mar 10, 2025, 05:55 PM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Mar 10, 2025, 06:19 PM UTC
In the Concur Cloud for Public Sector (CCPS) Data Center, access to Concur Expense through the SAP Concur website is 25% below expected level. Affected users may encounter extreme latency when attempting to access Concur Expense or when attempting to create and submit expense reports. Users may be able to complete tasks provided they wait for the latency to complete. The Incident Response Team is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Mar 10, 2025, 07:06 PM UTC
User impact since the last update is unchanged. In the Concur Cloud for Public Sector (CCPS) Data Center, access to Concur Expense through the SAP Concur website is 25% below expected level. Affected users may encounter extreme latency when attempting to access Concur Expense or when attempting to create and submit expense reports. Users may be able to complete tasks provided they wait for the latency to complete. The Incident Response Team (IRT) has engaged additional resources to assist with executing a restart of a business service tier. Our next scheduled update will be in one hour or sooner should a significant change occur.
- resolved Mar 10, 2025, 07:40 PM UTC
In the Concur Cloud for Public Sector (CCPS) Data Center, access to Concur Expense through the SAP Concur website was 25% below expected level. Affected users may have encountered extreme latency when attempting to access Concur Expense or when attempting to create and submit expense reports. Users may have been able to complete tasks provided they waited for latency to be complete. 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 Mar 10, 2025, 07:48 PM UTC
In the Concur Cloud for Public Sector (CCPS) Data Center, access to Concur Expense through the SAP Concur website was 25% below expected level. Affected users may have encountered extreme latency when attempting to access Concur Expense or when attempting to create and submit expense reports. Users may have been able to complete tasks provided they waited for the latency to be completed. The Incident Response Team (IRT) restarted a business server tier 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 be conducted, and a root cause analysis report provided when that investigation is complete.
- resolved Mar 18, 2025, 11:53 AM UTC
Impact as Reported: In the Concur Cloud for Public Sector (CCPS) Data Center, access to Concur Expense through the SAP Concur website is 25% below expected level. Affected users may encounter extreme latency when attempting to access Concur Expense or when attempting to create and submit expense reports. Users may be able to complete tasks provided they wait for the latency to complete. Root cause: An Expense service experienced higher latency than normal, leading to performance degradation when attempting to create an expense report. The Incident Response Team restarted an application pool to restore the service to normal levels. We are continuing the investigation into the root cause of the higher latency issue. Corrective Actions: Corrective actions will be determined once root cause has been fully identified.
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.