SAP Concur incident
Expense, Travel, Invoice, Request, Imaging, Analysis/Intelligence: P1
Resolved after 41 minutes, affecting Analysis/Intelligence and Expense and 1 more, on July 29, 2025.
In the Concur Cloud for Public Sector Data Center, logins via the SAP Concur website and mobile app were performing below expected levels. Concur Travel and Expense users may have encountered slowness with the error message “An error occurred while processing your request,” or a “502 Bad Gateway” error when attempting to access the CTE production environment. ConcurGov users may also have experienced slowness, become stuck on the login page, or received a “502 Bad Gateway” error when attempting to access the ConcurGov production environment. While the Incident Response Team (IRT) was actively investigating the issue, we observed that the affected service began to recover without manual intervention. We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause is underway, and a root cause analysis report will be provided once it is complete.
Affected components
Update timeline
- resolved Jul 29, 2025, 04:31 AM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Jul 29, 2025, 04:38 AM UTC
In the Concur Cloud for Public Sector Data Center, logins via the SAP Concur website and mobile app are performing below expected levels. Concur Travel and Expense users may encounter slowness with the error message “An error occurred while processing your request,” or a “502 Bad Gateway” error when attempting to access the production environment. ConcurGov users may also experience slowness, become stuck on the login page, or receive a “502 Bad Gateway” error. The Incident Response Team (IRT) is actively investigating the issue. Our next update will be provided within one hour, or sooner if there is a significant development.
- resolved Jul 29, 2025, 04:41 AM UTC
In the Concur Cloud for Public Sector Data Center, logins via the SAP Concur website and mobile app were performing below expected levels. Concur Travel and Expense users may have encountered slowness with the error message “An error occurred while processing your request,” or a “502 Bad Gateway” error when attempting to access the CTE production environment. ConcurGov users may also have experienced slowness, become stuck on the login page, or received a “502 Bad Gateway” error when attempting to access the ConcurGov production environment. 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 Jul 29, 2025, 04:50 AM UTC
In the Concur Cloud for Public Sector Data Center, logins via the SAP Concur website and mobile app were performing below expected levels. Concur Travel and Expense users may have encountered slowness with the error message “An error occurred while processing your request,” or a “502 Bad Gateway” error when attempting to access the CTE production environment. ConcurGov users may also have experienced slowness, become stuck on the login page, or received a “502 Bad Gateway” error when attempting to access the ConcurGov production environment. While the Incident Response Team (IRT) was actively investigating the issue, we observed that the affected service began to recover without manual intervention. We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause is underway, and a root cause analysis report will be provided once it is complete.
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