SAP Concur incident
Expense, Travel, Imaging, Analysis/Intelligence, Mobile: P1
Resolved after 1 hour 5 minutes, affecting Analysis/Intelligence and Expense and 1 more, on July 24, 2026.
Impact as Reported: We identified a service disruption affecting the availability of the Concur application in the US2 Data Center. All customers hosted in the affected Data Center experienced this impact. On the login page, users received the following error message: "Sorry, Concur is currently unavailable." The error occurred before users could enter their login credentials, preventing access to the application. Users who were already logged in during the impact window were logged out of the system and encountered the same error when attempting to access the Concur application. Root cause: The incident was caused by a failure of edge networking hardware within the infrastructure of SAP Concur’s hyperscale hosting provider. The affected devices were responsible for routing traffic between the US2 region and external network destinations, which resulted in connectivity issues for customers accessing services hosted in that region. The hosting provider is currently conducting a detailed root cause investigation. Once completed, the provider will share the findings, along with any corrective and preventive actions, with SAP Concur. During the initial stages of the incident, the response team assessed that the impact extended beyond the US2 Data Center. This assessment was based on synthetic monitoring tests that were hosted in the same hyperscale region affected by the network hardware failure. As a result, the monitoring data generated false-positive alerts indicating issues in other SAP Concur Data Centers. Following a more detailed validation of service health across all environments, the impact assessment was refined and confirmed to be limited to the US2 Data Center. Corrective Actions: To improve monitoring accuracy and resilience, SAP Concur is migrating its synthetic monitoring tests to a geographically separate hyperscale region. This change will help ensure greater reliability of monitoring signals and reduce the risk of similar false-positive alerts in the future.
Other major vendors with incidents that started within 30 minutes of this one
And 2 more: Notion, Cloudflare.
Affected components
Update timeline
- resolved Jul 24, 2026, 12:41 PM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Jul 24, 2026, 01:00 PM UTC
We identified a service disruption affecting the availability of the Concur application in the APJ1, US2 Data, and Concur Cloud for Public Sector (CCPS) data centers. All customers hosted in the affected data centers experienced this impact. On the login page, users received the following error message: "Sorry, Concur is currently unavailable." The error occurred before users could enter their login credentials, preventing access to the application. Users who were already logged in during the impact window were logged out of the system and encountered the same error when attempting to access the Concur application. No workaround was available during the period of impact. Services have returned to normal operating levels. We will continue to monitor for the next 1-2 hours to verify stability. Once verified as stable the incident will be resolved
- resolved Jul 24, 2026, 02:08 PM UTC
The incident impacted only the US2 Data center. APJ1 and Concur Cloud for Public Sector (CCPS) data centers was not affected by this incident. We apologize for the inconvenience. All other details provided in the resolved communication remain unchanged. When users attempted to access the Concur application, they received the following error message: "Sorry, Concur is currently unavailable." The error was displayed before the login page loaded, preventing users from accessing the application. Users who were already logged in during the impact window were logged out of the system and encountered the same error when attempting to access the Concur application again. The Incident Response Team (IRT) investigated the issue and identified the cause as a network connectivity issue on our hyper-scaler. The appropriate teams implemented corrective actions 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 continue, and a Root Cause Analysis (RCA) report will be provided upon completion of the investigation.
- resolved Jul 24, 2026, 05:16 PM UTC
The incident impacted only the US2 Data center. APJ1 and Concur Cloud for Public Sector (CCPS) data centers was not affected by this incident. We apologize for the inconvenience. All other details provided in the resolved communication remain unchanged. When users attempted to access the Concur application, they received the following error message: "Sorry, Concur is currently unavailable." The error was displayed before the login page loaded, preventing users from accessing the application. Users who were already logged in during the impact window were logged out of the system and encountered the same error when attempting to access the Concur application again. The Incident Response Team (IRT) investigated the issue and identified the cause as a network connectivity issue on our hyper-scaler. The appropriate teams implemented corrective actions 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 continue, and a Root Cause Analysis (RCA) report will be provided upon completion of the investigation.
- resolved Jul 24, 2026, 05:27 PM UTC
The incident impacted only the US2 Data center. APJ1 and Concur Cloud for Public Sector (CCPS) data centers was not affected by this incident. We apologize for the inconvenience. All other details provided in the resolved communication remain unchanged. When users attempted to access the Concur application, they received the following error message: "Sorry, Concur is currently unavailable." The error was displayed before the login page loaded, preventing users from accessing the application. Users who were already logged in during the impact window were logged out of the system and encountered the same error when attempting to access the Concur application again. The Incident Response Team (IRT) investigated the issue and identified the cause as a network connectivity issue on our hyper-scaler. The appropriate teams implemented corrective actions 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 continue, and a Root Cause Analysis (RCA) report will be provided upon completion of the investigation.
- resolved Aug 04, 2026, 08:19 AM UTC
Impact as Reported: We identified a service disruption affecting the availability of the Concur application in the US2 Data Center. All customers hosted in the affected Data Center experienced this impact. On the login page, users received the following error message: "Sorry, Concur is currently unavailable." The error occurred before users could enter their login credentials, preventing access to the application. Users who were already logged in during the impact window were logged out of the system and encountered the same error when attempting to access the Concur application. Root cause: The incident was caused by a failure of edge networking hardware within the infrastructure of SAP Concur’s hyperscale hosting provider. The affected devices were responsible for routing traffic between the US2 region and external network destinations, which resulted in connectivity issues for customers accessing services hosted in that region. The hosting provider is currently conducting a detailed root cause investigation. Once completed, the provider will share the findings, along with any corrective and preventive actions, with SAP Concur. During the initial stages of the incident, the response team assessed that the impact extended beyond the US2 Data Center. This assessment was based on synthetic monitoring tests that were hosted in the same hyperscale region affected by the network hardware failure. As a result, the monitoring data generated false-positive alerts indicating issues in other SAP Concur Data Centers. Following a more detailed validation of service health across all environments, the impact assessment was refined and confirmed to be limited to the US2 Data Center. Corrective Actions: To improve monitoring accuracy and resilience, SAP Concur is migrating its synthetic monitoring tests to a geographically separate hyperscale region. This change will help ensure greater reliability of monitoring signals and reduce the risk of similar false-positive alerts in the future.
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