SAP Concur Outage History

Started Oct 20, 2026, 03:34 PM UTC· resolved Oct 20, 2026, 10:20 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 16, 2026, 02:03 PM UTC· resolved Oct 16, 2026, 04:21 PM UTC

1. resolved Oct 16, 2026, 04:36 PM UTC

   A service disruption has been identified and resolved affecting travel search functionality for Legacy Travel customers in the US2 Data Center. Affected users encountered the error message "We're Sorry… We encountered an issue that prevented us from completing your request" upon submitting search criteria in the travel wizard. The disruption impacted searches for air, hotel, and car travel segments across all Global Distribution Systems (GDSs). New Concur Travel customers were not affected and retained full search and booking functionality throughout the incident period. A workaround for this issue was not available during service disruption. As the Incident Response Team (IRT) was gathering, the service 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.

Read the full incident report →

Started Oct 13, 2026, 08:41 PM UTC· resolved Oct 13, 2026, 09:20 PM UTC

1. resolved Oct 13, 2026, 11:22 PM UTC

   We have identified and resolved a service disruption in the Concur Cloud for Public Sector Data Center. The incident impacted access and functionality across the Expense, Travel, Request, and Analysis/Intelligence services. All Concur Travel and Expense (CTE) and Go.gov customers experienced latency and errors when navigating between service tabs following login. Expense users encountered delays when accessing Manage Expenses and when creating or submitting expense reports. Travel users may have experienced missing date fields during travel searches. Attempting to refresh or retry failed actions resulted in no changed behavior. Workaround: A workaround was not available during service disruption. The Incident Response Team (IRT) executed a configuration change on a database 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 now be conducted, and a root cause analysis report provided when that investigation is complete.

Read the full incident report →

Started Oct 08, 2026, 02:20 PM UTC· resolved Oct 08, 2026, 03:50 PM UTC

1. resolved Oct 08, 2026, 03:34 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Oct 08, 2026, 03:54 PM UTC

   We have identified an intermittent service degradation affecting logins via mobile device. This issue is currently impacting approximately 1% of customers in the US2 Data Center. When attempting to access the SAP Concur site via mobile device, users may receive the error message, "Sorry, something went wrong," after entering their login credentials. When this error occurs, the login attempt cannot be completed during that session. Additionally, it is possible some users may experience increased latency after entering their username and password. Users who are already logged in can continue working without interruption. Workaround: We have identified a workaround for you. If you encounter an error message after entering your user name and password, you may be able to successfully sign in by retrying your login attempt. Additionally, it is possible to login via web without issue. The Incident Response Team (IRT) is actively working to restore normal service by restarting servers that have been identified as underperforming. Our next scheduled update will be provided within one hour, or sooner if a significant change in status occurs.

3. resolved Oct 08, 2026, 04:05 PM UTC

   We identified an intermittent service degradation that affected logins via mobile device. This issue was impacting approximately 1% of customers in the US2 Data Center. When attempting to access the SAP Concur site using the SAP mobile app, users may have received the error message, "Sorry, something went wrong," after entering their login credentials. When this error occurred, the login attempted could not be completed during that session. Additionally, it was possible some users may have experienced increased latency after entering their username and password. Users who were already logged in were able to continue working without interruption. 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.

4. resolved Oct 08, 2026, 04:16 PM UTC

   We identified an intermittent service degradation that affected logins via mobile device. This issue was impacting approximately 1% of customers in the US2 Data Center. When attempting to access the SAP Concur site using the SAP mobile app, users may have received the error message, "Sorry, something went wrong," after entering their login credentials. When this error occurred, the login attempted could not be completed during that session. Additionally, it was possible some users may have experienced increased latency after entering their username and password. Users who were already logged in were able to continue working without interruption. Workaround: We identified a workaround for you during the time of impact. If you encountered an error message after entering your user name and password, you may have been able to successfully sign in by retrying your login attempt. Additionally, it was possible to login via web without issue. The IRT isolated an underperforming server and took action to perform a failover 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.

Read the full incident report →

Started Sep 28, 2026, 10:46 PM UTC· resolved Sep 28, 2026, 10:56 PM UTC

1. resolved Sep 28, 2026, 11:46 PM UTC

   We have identified and resolved a service disruption impacting access to Concur Expense and Invoice. This is impacting all customers in the US2 datacenter. After logging in and trying to access Concur Expense and Invoice, users encountered the following error “Sorry,but something went wrong with this task.Try refreshing the pager sign out and sign in again.” Workaround: Unfortunately, no workaround was available during this period of impact. 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.

Read the full incident report →

Started Sep 26, 2026, 08:12 AM UTC· resolved Sep 26, 2026, 08:22 AM UTC

1. resolved Sep 26, 2026, 09:12 AM UTC

   We identified a service disruption that impacted access to the Analysis and Intelligence service in the US2 Data Center. All users with access to the service received the error, “An error has occurred. Please try again. If the problem persists, contact your Company Administrator or Help Desk for assistance,” when attempting to log in to Reporting. No workaround was available during the incident. As the Incident Response Team (IRT) was being assembled, the service self-recovered and functionality was restored. 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 will be provided when that investigation is complete.

2. resolved Oct 12, 2026, 08:22 AM UTC

   Impact as Reported: We identified a service disruption that impacted access to Analysis and Intelligence service in the US2 Data Center. All users with access to the service received the error, “An error has occurred. Please try again. If the problem persists, contact your Company Administrator or Help Desk for assistance,” when attempting to log in to Reporting. No workaround was available during the incident. Root cause: The Analysis and Intelligence service authentication workflow relies on a downstream service to retrieve connection information needed to complete user authentication and related transactions. During the incident, this dependency experienced elevated CPU utilization, resulting in increased response times and repeated service restarts. The investigation determined that a previous infrastructure change, implemented to address memory-related stability concerns, included a reduction in available CPU capacity, and under elevated production workload conditions, the configured CPU limit was insufficient. As utilization reached the assigned limit, service performance degraded, leading to increased latency and intermittent restarts. Corrective Actions: The service configuration was updated to provide adequate CPU resources, eliminating the constraint that contributed to the performance degradation and restarts. Proactive monitoring and alerting for resource utilization, performance degradation, and service health is being implemented to enable earlier detection of capacity issues and reduce the risk of customer impact from service instability.

Read the full incident report →

Started Sep 24, 2026, 07:50 AM UTC· resolved Sep 24, 2026, 08:24 AM UTC

1. resolved Sep 24, 2026, 09:20 AM UTC

   We wish to inform you of a service degradation that affected your service but was promptly and successfully detected and resolved by our Incident Response Team. After completing a post resolution monitoring period, we have confirmed that service is operating at a normal and stable level so have resolved this incident. We identified and resolved a service degradation that affected user logins and caused latency and slow response times when accessing various services in the Concur for EU2 data center. During the impact period, users who attempted to sign in using either Single Sign-On (SSO) or a username and password may have encountered the following error message: “Sorry, something went wrong.” Users who were already logged in during the impact period may have experienced various symptoms, including blank pages and generally slow page loading. Unfortunately, no workaround was available during the period of impact. The Incident Response Team (IRT) performed a rollback of a recent change to restore service.

Read the full incident report →

Started Sep 21, 2026, 08:59 AM UTC· resolved Sep 21, 2026, 09:09 AM UTC

1. resolved Sep 21, 2026, 10:10 AM UTC

   We identified and resolved a service degradation affecting user logins in the US2 data center. All customers hosted on a particular server were affected. During the time of impact, users attempting to sign in using either Single Sign-On (SSO) or a username and password may have encountered the following error message: 'Sorry, something went wrong.' As a result, users were unable to access Concur and would have experienced errors with various services during the downtime. Users that were already logged in during the time of impact were able to continue with their work. Unfortunately, no workaround was available during the period of impact. As the Incident Response Team (IRT) was gathering, the service 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.

2. resolved Oct 02, 2026, 11:49 AM UTC

   Impact as Reported: We identified and resolved a service degradation affecting user logins in the US2 Data Center. All customers hosted on a particular server were affected. During the time of impact, users attempting to sign in using either Single Sign-On (SSO) or a username and password may have encountered the following error message: 'Sorry, something went wrong.' As a result, users were unable to access Concur and would have experienced errors with various services during the downtime. Users that were already logged in during the time of impact were able to continue with their work. Root cause: The incident was caused by a large-scale database update that modified approximately 360000 records in a heavily utilized application table, creating extensive locking and resource contention that rendered the database unresponsive. Due to a human error the operation was executed directly against production without following an established review process, bypassing validation and impact assessment controls. Corrective Actions: Investigate and reduce higher-level user privileges on Concur production databases and migrate legacy manual update workflows to more controlled execution mechanisms. Enforce a governed execution mechanisms that provide additional validation, oversight, and operational safeguards.Impact as Reported: We identified and resolved a service degradation affecting user logins in the US2 Data Center. All customers hosted on a particular server were affected. During the time of impact, users attempting to sign in using either Single Sign-On (SSO) or a username and password may have encountered the following error message: 'Sorry, something went wrong.' As a result, users were unable to access Concur and would have experienced errors with various services during the downtime. Users that were already logged in during the time of impact were able to continue with their work. Root cause: The incident was caused by a large-scale database update that modified approximately 360000 records in a heavily utilized application table, creating extensive locking and resource contention that rendered the database unresponsive. Due to a human error the operation was executed directly against production without following an established review process, bypassing validation and impact assessment controls. Corrective Actions: Investigate and reduce higher-level user privileges on Concur production databases and migrate legacy manual update workflows to more controlled execution mechanisms. Enforce a governed execution mechanisms that provide additional validation, oversight, and operational safeguards.

Read the full incident report →

Started Aug 17, 2026, 01:37 PM UTC· resolved Aug 17, 2026, 06:04 PM UTC

1. resolved Aug 17, 2026, 03:23 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Aug 17, 2026, 04:05 PM UTC

   We have identified a functional disruption impacting Travel Request submissions. This issue is affecting all Travel Request users in the APJ1 Data Center. When attempting to submit a previously created Travel Request from "Manage Requests", a blank page is presented after the page refreshes, preventing the Travel Request details from loading. When attempting to submit a newly created Travel Request, the blank screen is presented after selecting "Create New Request". In both scenarios, attempting to select "Submit Request" results in an error, and the Travel Request cannot be submitted. Additionally, we identified a functional degradation impacting the creation of a Travel Allowance within expense reports. This issue is also impacting all users in the APJ1 Data Center. When attempting to complete the Start or End Location in the Travel Allowance an error, "An error occurred when processing your request" occurs. Clicking "OK" and completing the template multiple times may result in successful Travel Allowance creations. Workaround: Unfortunately there is no way for you to workaround the issue impacting Travel Request submissions for previously created Requests. You may be able to workaround the issue impacting adding a Travel Allowance to an existing expense report by performing multiple attempts. The Incident Response Team (IRT) has gathered, and are currently performing a review of recent changes. In parallel, a review of internal error logs is underway. A potential root cause has been identified, and additional teams have been engaged to address and provide input with respect to the current theory. Our next scheduled update will be in one hour.

3. resolved Aug 17, 2026, 05:31 PM UTC

   User impact has changed. We have identified a functional disruption impacting Travel Request submissions. This issue is affecting all Travel Request users in the APJ1 Data Center. When attempting to submit a newly created Travel Request, a blank page is presented after clicking "Create New Request", preventing the Travel Request details from loading. The Travel Request cannot be submitted. When attempting to access a previously created Travel Request, the header is missing from the Request when the screen refreshes. The Travel Request cannot be submitted. Additionally, we identified a functional degradation impacting the creation of a Travel Allowance within expense reports. This issue is also impacting all users in the APJ1 Data Center. When attempting to complete the Start or End Location in the Travel Allowance an error, "An error occurred when processing your request" occurs. Clicking "OK" and completing the template multiple times may result in successful Travel Allowance creations. Workaround: Unfortunately there is no way for you to workaround the issue impacting Travel Request submissions for previously created Requests. You may be able to workaround the issue impacting adding a Travel Allowance to an existing expense report by performing multiple attempts. The Incident Response Team (IRT) performed a revert of a recent change in an attempt to restore service. Unfortunately, subsequent testing confirmed this revert was not successful in restoring service. The IRT is currently performing validation steps from the revert and reviewing internal logs to determine next steps. Our next scheduled update will be in one hour.

4. resolved Aug 17, 2026, 06:21 PM UTC

   We identified a functional disruption impacting Travel Request submissions. This issue was affecting all Travel Request users in the APJ1 Data Center. When attempting to submit a newly created Travel Request, a blank page was presented after clicking "Create New Request", preventing the Travel Request details from loading. The Travel Request could not be submitted. When attempting to access a previously created Travel Request, the header was missing from the Request when the screen refreshed. The Travel Request could not be submitted. Additionally, we identified a functional degradation impacting the creation of a Travel Allowance within expense reports. This issue was also impacting all users in the APJ1 Data Center. When attempting to complete the Start or End Location in the Travel Allowance an error, "An error occurred when processing your request" occurred. Clicking "OK" and completing the template multiple times may have resulted in successful Travel Allowance creations. Workaround: Unfortunately there was no way for you to workaround the issue impacting Travel Request submissions for previously created Requests. You may have been able to workaround the issue impacting adding a Travel Allowance to an existing expense report by performing multiple attempts. 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.

5. resolved Aug 17, 2026, 06:35 PM UTC

   We have resolved a functional disruption impacting Travel Request submissions. This issue was affecting all Travel Request users in the APJ1 Data Center. When attempting to submit a newly created Travel Request, a blank page was presented after clicking "Create New Request", preventing the Travel Request details from loading. The Travel Request could not be submitted. When attempting to access a previously created Travel Request, the header was missing from the Request when the screen refreshed. The Travel Request could not be submitted. Additionally, we have resolved a functional degradation impacting the creation of a Travel Allowance within expense reports. This issue was also impacting all users in the APJ1 Data Center. When attempting to complete the Start or End Location in the Travel Allowance an error, "An error occurred when processing your request" occurred. Clicking "OK" and completing the template multiple times may have resulted in successful Travel Allowance creations. Workaround: Unfortunately there was no way for you to workaround the issue impacting Travel Request submissions for previously created Requests. You may have been able to workaround the issue impacting adding a Travel Allowance to an existing expense report by performing multiple attempts. The IRT completed the revalidation steps pertaining to the original revert that was performed. Following this action, a second revert was performed. Subsequent testing confirmed positive results. 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.

6. resolved Sep 01, 2026, 09:35 AM UTC

   Impact as Reported: We identified a functional disruption impacting Travel Request submissions. This issue was affecting all Travel Request users in the APJ1 Data Center. When attempting to submit a newly created Travel Request, a blank page was presented after clicking "Create New Request", preventing the Travel Request details from loading. The Travel Request could not be submitted. When attempting to access a previously created Travel Request, the header was missing from the Request when the screen refreshed. The Travel Request could not be submitted. Additionally, we identified a functional degradation impacting the creation of a Travel Allowance within expense reports. This issue was also impacting all users in the APJ1 Data Center. When attempting to complete the Start or End Location in the Travel Allowance an error, "An error occurred when processing your request" occured. Clicking "OK" and completing the template multiple times may have resulted in successful Travel Allowance creations. Root cause: Travel Requests experienced an issue related to the interaction between the Expense and Travel services. The Incident Response Team determined that a software defect was introduced with an update to a core travel component. The update prevented information required for request processing from being passed correctly between services, Engineering reverted the update to restore services.

Read the full incident report →

Started Aug 05, 2026, 11:09 PM UTC· resolved Aug 06, 2026, 01:55 AM UTC

1. resolved Aug 06, 2026, 01:08 AM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Aug 06, 2026, 01:27 AM UTC

   We have identified a functional degradation impacting Expense Report submissions in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users may intermittently encounter the following error after selecting Submit, when the Report Totals pop-up window is displayed: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” As a workaround, users can close the error message, then select Submit Report from the Report Totals pop-up window, followed by Accept & Continue. This approach has successfully allowed users to submit their Expense Reports. The Incident Response Team (IRT) has been engaged and is currently investigating to determine the cause of the issue. The next update will be provided within one hour or sooner as additional information becomes available.

3. resolved Aug 06, 2026, 01:59 AM UTC

   We identified a functional degradation impacting Expense Report submissions in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users intermittently encountered the following error after selecting Submit, when the Report Totals pop-up window was displayed: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” As a workaround, users were able to close the error message, then select Submit Report from the Report Totals pop-up window, followed by Accept & Continue. This approach successfully allowed users to submit their Expense Reports. 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.

4. resolved Aug 06, 2026, 02:10 AM UTC

   We identified a functional degradation impacting Expense Report submissions in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users intermittently encountered the following error after selecting Submit, when the Report Totals pop-up window was displayed: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” As a workaround, users were able to close the error message, then select Submit Report from the Report Totals pop-up window, followed by Accept & Continue. This approach successfully allowed users to submit their Expense Reports. The Incident Response Team (IRT) determined that the issue was caused by a recent service update. The team reverted the update, which resolved the issue and restored normal Expense Report submission functionality. 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.

5. resolved Aug 17, 2026, 08:43 AM UTC

   FRCA Impact as reported: A functional degradation impacted Expense Report submissions in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users intermittently encountered the following error after selecting Submit, when the Report Totals pop-up window was displayed: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” Closing the pop-up windows and continuing with the submission would successfully complete the poeration. Root Cause: A customer-impacting issue was introduced following an application update that depended on a data field not consistently available across all components involved in report processing. For affected users, submitting an expense report triggered a pop-up message stating: “Sorry, but something went wrong with this task. Try refreshing the page, or sign out and sign in again.” While this message incorrectly indicated that the submission had failed, the issue was limited to the application's error handling and validation workflow. In practice, users could dismiss the message and their expense reports were still submitted successfully. Initial incident response was delayed because alerts generated by synthetic monitoring were misdiagnosed as a defect in the monitoring test itself rather than an indication of a customer-facing issue. Once engineers correlated the alerts with customer behavior and confirmed the impact, the source of the issue was identified as a mismatch between newly deployed application components and a required dependency, causing the application to incorrectly generate an error message during report submission. Service was restored by rolling back the recent deployment and returning the environment to a known-good version. The root cause was a gap in dependency and deployment coordination across multiple teams and environments, which did not provide sufficient visibility to verify that prerequisite changes had been fully deployed before dependent releases were built and promoted.

Read the full incident report →

Started Jul 24, 2026, 10:57 AM UTC· resolved Jul 24, 2026, 12:02 PM UTC

1. resolved Jul 24, 2026, 12:41 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. 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

3. 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.

4. 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.

5. 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.

6. 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.

Read the full incident report →

Started Jul 23, 2026, 09:17 PM UTC· resolved Jul 23, 2026, 09:47 PM UTC

1. resolved Jul 23, 2026, 09:41 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Jul 23, 2026, 10:14 PM UTC

   We identified and resolved a service degradation affecting user logins in the US2 and EU2 Data Centers. The Incident Response Team (IRT) is working to provide the overall Customer Base Impact and will provide this information when available. During the time of impact, users attempting to sign in using either Single Sign-On (SSO) or a username and password may have intermittently encountered the following error message: "Sorry, something went wrong." When this error occurred, users may have been able to successfully login and access services after multiple attempts. Users that were already logged in during the time of impact were able to continue with their work. Workaround: During the impact period, users may have been able to successfully access services after multiple login attempts. Services have returned to normal operating levels. We will continue to monitor for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

3. resolved Jul 23, 2026, 10:46 PM UTC

   We identified a service degradation affecting user logins in the US2 and EU2 Data Centers. During the time of impact approximately 48% of attempted logins in the US2 Data Center were blocked, and approximately 10% of attempted logins in the EU2 Data Center were blocked. Users attempting to sign in using either Single Sign-On (SSO) or a username and password may have intermittently encountered the following error message: "Sorry, something went wrong." When this error occurred, users may have been able to successfully login and access services after multiple attempts. Users that were already logged in during the time of impact were able to continue with their work. Workaround: During the impact period, users may have been able to successfully access services after multiple login attempts. The Incident Response Team (IRT) determined that a recent change caused intermittent login issues for some users. The issue was resolved by updating the affected authentication configuration, restoring normal login functionality. 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.

4. resolved Aug 06, 2026, 09:04 AM UTC

   Impact as Reported: We identified and resolved a service degradation affecting user logins in the US2 and EU2 Data Centers. The Incident Response Team (IRT) is working to provide the overall Customer Base Impact and will provide this information when available. During the time of impact, users attempting to sign in using either Single Sign-On (SSO) or a username and password may have intermittently encountered the following error message: "Sorry, something went wrong." When this error occurred, users may have been able to successfully login and access services after multiple attempts. Users that were already logged in during the time of impact were able to continue with their work. Root Cause: Intermittent login failures occurred during a planned authentication service migration. As part of the change, a routine automated cleanup process inadvertently removed an active authentication configuration that was still being used by other environments. This prevented the affected environments from communicating with a dependent identity service required for user authentication. The investigation determined that the automation process did not adequately validate that the configuration being removed was associated only with the environment undergoing the migration. As a result, an active shared configuration was unintentionally deleted, causing authentication requests to fail in the affected environments. Service was restored by generating and deploying replacement configuration values, re-establishing connectivity to the identity service. Corrective Actions: The following corrective and preventive actions were identified: Replaced the affected configuration with new values to restore connectivity and resume normal authentication operations. Temporarily disabled the automated cleanup process until all migration activities and related configuration updates have been completed and fully validated. Updated the implementation approach to execute future migrations in multiple controlled phases, with validation checkpoints between each phase to reduce risk and improve change oversight. Enhanced automation safeguards and validation checks to ensure that only configurations associated with the intended environment can be modified or removed. Expanded testing and operational procedures to address environment migration scenarios and identify potential cross-environment dependencies before changes are implemented.

Read the full incident report →

Started Jul 14, 2026, 08:25 AM UTC· resolved Jul 14, 2026, 09:37 AM UTC

1. resolved Jul 14, 2026, 09:55 AM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Jul 14, 2026, 10:44 AM UTC

   A limited subset of customers in the EU2 Data Center experienced a functional disruption with Invoice, Expense, Request, and Imaging service. When working with Expenses, Requests, and Invoices, customers were unable to attach receipts, upload and retrieve images. On the Imaging side, customers were not seeing attached Images, getting “Receipt not available” error. Service has been restored to a normal operating level, and we have started a mandatory post recovery monitoring period to ensure service performance stability prior to declaring the incident resolved. We will post the next incident communication at or before 11:30 AM UTC on 14 July 2026.

3. resolved Jul 14, 2026, 11:03 AM UTC

   A limited subset of customers in the EU2 Data Center experienced a functional disruption with Invoice, Expense, Request, and Imaging service. When working with Expenses, Requests, and Invoices, customers were unable to attach receipts, upload and retrieve images. On the Imaging side, customers were not seeing attached Images, getting “Receipt not available” error. The Incident Response Team rolled back a recent deployment to restore service. 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.

4. resolved Jul 23, 2026, 11:13 AM UTC

   Impact as reported: A limited subset of customers in the EU2 Data Center experienced a functional disruption with Invoice, Expense, Request, and Imaging service. When working with Expenses, Requests, and Invoices, customers were unable to attach receipts, upload and retrieve images. On the Imaging side, customers were not seeing attached Images, getting “Receipt not available” error. Root cause: A service deployment introduced a change that validated cache connection authentication on every request instead of performing periodic validation. Although the broader security enhancement being deployed was not enabled and was not the direct cause, this connection-validation behaviour significantly increased load on the shared cache infrastructure. The additional overhead caused CPU saturation on one cache shard in the EU2 environment, leading to degraded cache performance, application errors, HTTP 500 responses, and failed transactions. The issue was not identified during pre-production testing because: Canary deployments did not generate enough sustained load to expose the problem. Performance testing focused on application behaviour rather than infrastructure stress limits. Monitoring did not provide early visibility into cache CPU saturation. The EU2 environment had less capacity headroom than another region where similar changes had been deployed. Corrective Actions: The deployment was rolled back and service restored. The authentication validation has been changed from "every request" to "periodic checks". The cache cluster capacity has been increased in the affected region.

Read the full incident report →

Started Jun 28, 2026, 07:28 AM UTC· resolved Jun 28, 2026, 07:59 AM UTC

1. resolved Jun 28, 2026, 07:56 AM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Jun 28, 2026, 08:49 AM UTC

   We identified a service degradation impacting logins. This issue impacted all users in the Concur Cloud for Public Sector Data Center. Internal monitoring and manual testing confirm systems have now recovered, and users are able to login successfully. Concur Travel and Expense users received a "Sorry Something went Wrong" error on the home page after logging in during the time of impact. Workaround: During the time of impact no workaround was available. We will continue to monitor performance for the next 15 to 30 minutes to verify stability. Once stability is confirmed, this incident will be officially resolved.

3. resolved Jun 28, 2026, 09:09 AM UTC

   We identified a service degradation impacting logins. This issue impacted all users in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users received a "Sorry Something went Wrong" error on the home page after logging in during the time of impact. Workaround: During the time of impact no workaround was available. As the Incident Response Team (IRT) was gathering, the service 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.

4. resolved Aug 03, 2026, 04:58 PM UTC

   Impact as Reported: We identified a service degradation impacting logins. This issue impacted all users in the Concur Cloud for Public Sector Data Center. Internal monitoring and manual testing confirm systems have now recovered, and users are able to login successfully. Concur Travel and Expense users received a "Sorry Something went Wrong" error on the home page after logging in during the time of impact. Root cause: A routine automated infrastructure node rotation triggered an outage within the environment supporting authentication services. During the rotation, newly provisioned nodes were introduced into service and were incorrectly determined to be healthy based on the existing health validation mechanism. While the nodes were accepting network connections, they were not fully ready to process application traffic. As a result, customer requests were routed to nodes that had not completed initialization of all required service components. Authentication requests sent to these nodes failed, preventing users from successfully logging in and resulting in the observed user-facing errors. The investigation was unable to conclusively determine why the newly created service instances did not become fully operational. However, it identified a gap in the health validation process, which relied on basic connectivity checks rather than verifying end-to-end application readiness. This allowed traffic to be directed to partially initialized nodes and created the conditions for customer impact. Corrective Actions: Implement more comprehensive health checks that validate application readiness rather than basic connectivity alone. Introduce additional validation mechanisms to ensure newly provisioned nodes can successfully process customer traffic before being placed into service.

Read the full incident report →

Started Jun 23, 2026, 06:49 PM UTC· resolved Jun 24, 2026, 02:30 PM UTC

1. resolved Jun 24, 2026, 02:30 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Jun 24, 2026, 02:45 PM UTC

   Importing and Exporting files via sFTP server is currently unavailable in the Concur Cloud for Public Sector Data Center. Connection attempts return an error, resulting in failures to successfully submit and process sFTP file transfers. Concur Travel and Expense Admins will experience widespread errors when attempting to import or export files via sFTP server. Concur Gov Admins will experience an error, Access Denied when sending files back to Concur for updates, leaving all documents in a pending status. The Incident Response Team (IRT) is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

3. resolved Jun 24, 2026, 03:04 PM UTC

   Importing and Exporting files via sFTP server was unavailable in the Concur Cloud for Public Sector. Connection attempts returned an error, resulting in failures to successfully submit and process sFTP file transfers. Concur Travel and Expense Admins experienced widespread errors when attempting to import or export files via sFTP server. Concur Gov Admins experienced an error, "Access Denied" when sending files back to Concur for updates, leaving all documents in a pending status. 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.

4. resolved Jun 24, 2026, 03:24 PM UTC

   Importing and Exporting files via sFTP server was unavailable in the Concur Cloud for Public Sector. Connection attempts returned an error, resulting in failures to successfully submit and process sFTP file transfers. To ensure all impacted files and documents are processed correctly, please re-upload any files that failed to upload during the affected time period. Additionally, any files that were not downloaded during the incident will need to be downloaded. Concur Travel and Expense Admins experienced widespread errors when attempting to import or export files via sFTP server. Concur Gov Admins experienced an error, "Access Denied" when sending files back to Concur for updates, leaving all documents in a pending status. The Incident Response Team took action to revert a recent change to restore service.

5. resolved Aug 03, 2026, 04:52 PM UTC

   Impact as Reported: Importing and Exporting files via sFTP server was unavailable in the Concur Cloud for Public Sector. Connection attempts returned an error, resulting in failures to successfully submit and process sFTP file transfers. Concur Travel and Expense Admins experienced widespread errors when attempting to import or export files via sFTP server. Concur Gov Admins experienced an error, "Access Denied" when sending files back to Concur for updates, leaving all documents in a pending status. Root cause: A configuration change was deployed as part of a security vulnerability remediation. While the change had been successfully implemented in other environments, the affected environment uses a unique cloud configuration that required a different partition identifier. This environment-specific difference was not identified during deployment, resulting in file transfer traffic being blocked. The issue was not detected immediately because post-deployment validation relied on application logs, which showed no errors due to the low volume and scheduled nature of traffic in the affected environment. Infrastructure logs that would have indicated the configuration issue were not included in the initial validation process. Corrective Actions: The configuration was identified as the cause, the change was rolled back, restoring normal service. Following preventive action items have been identified and will be implemented in the near future: Update deployment validation procedures to include both infrastructure and application log verification. Introduce functional post-deployment testing by performing test file transfers in every environment following infrastructure or file transfer changes. Add delayed post-deployment health checks to verify expected traffic and system behavior after changes are implemented. Review and enhance monitoring and alerting capabilities to improve detection of similar issues, particularly in low-traffic environments.

Read the full incident report →

Started Jun 04, 2026, 02:00 AM UTC· resolved Jun 04, 2026, 03:09 AM UTC

1. resolved Jun 04, 2026, 04:18 AM UTC

   In the APJ1 Data Center, Expense, Analysis and Intelligence,Imaging, Invoice,Travel Request services were unavailable. Users could not view any SAP Concur products after logging in. They were getting error : You are currently not set up to use Any Concur products.Contact your Administrator for assistance. " As the Incident Response Team (IRT) was investigating, the service 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.

2. resolved Jun 15, 2026, 06:08 PM UTC

   In the APJ1 Data Center, Expense, Analysis and Intelligence, Imaging, Invoice, and Travel Request services were unavailable. Users could not view any SAP Concur products after logging in. They were getting error, “You are currently not set up to use Any Concur products. Contact your Administrator for assistance." Root Cause The incident response team determined that all containers supporting a service critical to expense-related functionality had entered a crash loop state. Investigation revealed that the issue was caused by insufficient memory allocation to these containers. Service was restored by increasing the allocated memory. Further analysis indicated that the service had been operating with overly optimized (minimal) memory settings for some time, leaving it close to capacity limits. Additionally, a misconfigured alert prevented early detection of the growing resource constraint, delaying proactive remediation. Correct Measures The following corrective and preventive actions have been implemented: -Memory allocation for the affected service has been increased across all SAP Concur environments to ensure sufficient capacity and reduce the risk of recurrence. -Monitoring and alerting for container crashes and restarts have been corrected to enable earlier detection and proactive resolution before customer impact occurs.

Read the full incident report →

Started May 18, 2026, 09:55 AM UTC· resolved May 18, 2026, 12:15 PM UTC

1. resolved May 18, 2026, 10:43 AM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved May 18, 2026, 11:09 AM UTC

   In the US2 Data Center, both Client Managed Capture and Concur Managed Capture are operating incorrectly and affecting 19% of Invoice customers. The affected customers can receive invoice batches but cannot create Invoices from Invoice Capture. When trying to access Verification for a specific batch, the affected users will receive “Application Error: Unexpected System Error”. Manually uploading batches also results in Application error. Additionally, Invoice Capture is not receiving emails. We have provided details of the incident known at this time, and are currently assessing and verifying the full extent of the user impact and assembling a specialized Incident Response Team (IRT) to investigate and resolve the issue. We will post the next incident communication at or before 12:00 PM UTC on 18 May 2026.

3. resolved May 18, 2026, 11:59 AM UTC

   In the US2 Data Center, both Client Managed Capture and Concur Managed Capture are operating incorrectly and affecting 19% of Invoice customers. The affected customers can receive invoice batches but cannot create Invoices from Invoice Capture. When trying to access Verification for a specific batch, the affected users will receive “Application Error: Unexpected System Error”. Manually uploading batches also results in Application error. Additionally, Invoice Capture is not receiving emails. The Incident Response Team has identified that the application servers are currently experiencing connection issues with one of our internal services. They are currently investigating the root cause. We will post the next incident communication at or before 1:00 PM UTC on 18 May 2026.

4. resolved May 18, 2026, 12:27 PM UTC

   In the US2 Data Center, both Client Managed Capture and Concur Managed Capture were operating incorrectly and affecting 19% of Invoice customers. The affected customers could receive invoice batches but not create Invoices from Invoice Capture. When trying to access Verification for a specific batch, the affected users would receive “Application Error: Unexpected System Error”. Manually uploading batches also resulted in Application error. Additionally, Invoice Capture was not receiving emails. Service has been restored to a normal operating level, and we have started a mandatory post recovery monitoring period to ensure service performance stability prior to declaring the incident resolved. We will post the next incident communication at or before 2:00 PM UTC on 18 May 2026

5. resolved May 18, 2026, 12:49 PM UTC

   In the US2 Data Center, both Client Managed Capture and Concur Managed Capture were operating incorrectly and affecting 19% of Invoice customers. The affected customers could receive invoice batches but not create Invoices from Invoice Capture. When trying to access Verification for a specific batch, the affected users would receive “Application Error: Unexpected System Error”. Manually uploading batches also resulted in Application error. Additionally, Invoice Capture was not receiving emails. 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.

6. resolved May 26, 2026, 04:59 PM UTC

   In the US2 Data Center, both Client Managed Capture and Concur Managed Capture were operating incorrectly and affecting 19% of Invoice customers. The affected customers could receive invoice batches but not create Invoices from Invoice Capture. When trying to access Verification for a specific batch, the affected users would receive “Application Error: Unexpected System Error”. Manually uploading batches also resulted in Application error. Additionally, Invoice Capture was not receiving emails. Root cause: A database supporting the Invoice Capture service ran out of available storage space. Once storage was fully consumed, the database stopped accepting new connections, causing the service to enter a continuous error state. Service was restored after increasing the database storage capacity, allowing connections and normal operations to resume. Corrective Actions: The following corrective and preventative actions were identified. -Implement and review enhanced alerts for database storage thresholds. -Identify high-growth tables and optimize storage usage. -Establish proactive capacity planning to account for growth trends.

Read the full incident report →

Started Apr 24, 2026, 08:16 PM UTC· resolved Apr 24, 2026, 08:56 PM UTC

1. resolved Apr 24, 2026, 08:34 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Apr 24, 2026, 09:05 PM UTC

   SAP Concur Expense customers are experiencing an issue with image functionality within expense reports. Internal performance metrics indicate approximately an 85% drop in expense report submit metrics, while the user experience symptom is upstream affecting various image processes. All affected users may encounter an error when attempting to upload an image, view an image, or trigger e-bunsho timestamp functionality. A workaround for this issue has not yet been identified. The Incident Response Team is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

3. resolved Apr 24, 2026, 09:08 PM UTC

   SAP Concur Expense customers experienced an issue with image functionality within expense reports. Internal performance metrics indicated approximately an 85% drop in expense report submit metrics, while the user experience symptom was upstream affecting various image processes. All affected users encountered an error when attempting to upload an image, view an image, or trigger e-bunsho timestamp functionality. A workaround was not identified during service degradation. 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.

4. resolved Apr 24, 2026, 09:19 PM UTC

   SAP Concur Expense customers experienced an issue with image functionality within expense reports. Internal performance metrics indicated approximately an 85% drop in expense report submit metrics, while the user experience symptom was upstream affecting various image processes. All affected users encountered an error when attempting to upload an image, view an image, or trigger e-bunsho timestamp functionality. A workaround was not identified during service degradation. The Incident Response Team (IRT) reverted a recent configuration change 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 now be conducted, and a root cause analysis report provided when that investigation is complete.

5. resolved May 11, 2026, 11:10 AM UTC

   Impact as Reported: SAP Concur Expense customers experienced an issue with image functionality within expense reports. Internal performance metrics indicated approximately an 85% drop in expense report submit metrics, while the user experience symptom was upstream affecting various image processes. All affected users encountered an error when attempting to upload an image, view an image, or trigger e-bunsho timestamp functionality. A workaround was not identified during service degradation. Root cause: An infrastructure deployment in the EU2 environment unintentionally replaced critical existing resources with a new set of configurations. This occurred because two infrastructure templates used the same name, leading the deployment process to overwrite essential components rather than add new ones. As a result, key system permissions and supporting resources required for processing and transferring images were temporarily removed. This prevented image uploads and downloads from functioning correctly. The issue was identified within minutes of deployment, and recovery actions were initiated immediately. The affected infrastructure was restored, and missing permissions were reattached to fully re-enable functionality. Corrective Actions: The following corrective and preventative actions were identified: Update the configuration to prevent conflicts between the two services. Clearer separation and labeling of infrastructure components will be enforced to avoid unintended overwrites. Review and update the thresholds for alerts to trigger to improve triaging the issues.

Read the full incident report →

Started Apr 09, 2026, 02:02 AM UTC· resolved Apr 09, 2026, 02:32 AM UTC

1. resolved Apr 09, 2026, 03:22 AM UTC

   In the Concur Cloud for Public Sector Data Center, users experienced degraded performance and access issues across multiple services. When attempting to access Concur Expense, Travel Request, and Analysis and Intelligence, affected users encountered the following error message: “You are currently not set up to use any Concur products. Contact your Concur Administrator for assistance”. As the Incident Response Team (IRT) was being assembled, the service 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.

2. resolved Aug 03, 2026, 04:51 PM UTC

   Impact as Reported: In the Concur Cloud for Public Sector Data Center, users experienced degraded performance and access issues across multiple services. When attempting to access Concur Expense, Travel Request, and Analysis and Intelligence, affected users encountered the following error message: “You are currently not set up to use any Concur products. Contact your Concur Administrator for assistance”. Root cause: A code defect intermittently affected credential management for a reporting service, causing it to attempt connections to an expense database host using invalid credentials. This eventually led to the service account being locked. Because the same account was shared by other expense-related services accessing the same database, the lockout caused widespread service disruption. Service was initially restored by unlocking the affected account. Corrective Actions: The following preventive and corrective actions have been identified: The reporting service has moved to use a dedicated service account. The credentials management code is being rewritten to address the defect

Read the full incident report →

Started Mar 23, 2026, 04:05 PM UTC· resolved Mar 23, 2026, 05:46 PM UTC

1. resolved Mar 23, 2026, 04:27 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Mar 23, 2026, 04:53 PM UTC

   In the US2 Data Center, expense report submission metrics and travel booking metrics were 40% below expected level. Internal monitoring and testing suggest affected travel users may have encountered an issue with searching for car or hotel segments encountering errors or latency. Affected expense users may have encountered errors or latency when attempting to create or submit expense reports. 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.

3. resolved Mar 23, 2026, 05:34 PM UTC

   In the US2 Data Center, expense report submissions metrics and travel booking metrics are 40% below expected level. Internal testing shows that affected users may encounter a home page indicating a disruption to services, after logging in. Users who are already logged-in may encounter errors and general latency while attempting to navigate and perform tasks within SAP Concur Travel and SAP Concur Expense services. We have observed a new disruption to our services during the monitoring period. The Incident Response Team (IRT) is investigating the issue. Our next scheduled update will be in one hour or sooner, should a significant change occur.

4. resolved Mar 23, 2026, 06:18 PM UTC

   In the US2 Data Center, expense report submissions metrics and travel booking metrics were 40% below expected level. Internal testing showed that affected users may have encountered a home page indicating a disruption to services, after logging in. Users who were already logged-in may have encountered errors and general latency while attempting to navigate and perform tasks within SAP Concur Travel and SAP Concur Expense services. 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.

5. resolved Mar 23, 2026, 06:32 PM UTC

   In the US2 Data Center, expense report submissions metrics and travel booking metrics were 40% below expected level. Internal testing showed that affected users may have encountered a home page indicating a disruption to services, after logging in. Users who were already logged-in may have encountered errors and general latency while attempting to navigate and perform tasks within SAP Concur Travel and SAP Concur Expense services. The Incident Response Team performed a failover on a database 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 now be conducted, and a root cause analysis report provided when that investigation is complete.

6. resolved Apr 09, 2026, 06:11 AM UTC

   Impact as Reported: In the US2 Data Center, expense report submissions metrics and travel booking metrics were 40% below expected level. Internal testing showed that affected users may have encountered a home page indicating a disruption to services, after logging in. Users who were already logged-in may have encountered errors and general latency while attempting to navigate and perform tasks within SAP Concur Travel and SAP Concur Expense services. Root cause: A core database suffered performance degradation that affected several services. The Incident Response Team identified a stored procedure that was exhausting the resources on the database. The database team switched over to a secondary instance to quickly remove all existing connections. This resolved the degradation and restored all the services. Corrective Actions: The following corrective and preventative actions were identified: Update the stored procedure plan to use less parallelism to prevent it from overloading the database Update the stored procedure to run on read-only secondary instances to prevent it from affecting the primary database instance

Read the full incident report →

Started Jan 19, 2026, 09:35 AM UTC· resolved Jan 19, 2026, 11:00 AM UTC

1. resolved Jan 21, 2026, 10:15 PM UTC

   A system outage caused a delay in posting incident communications. The issue has since been resolved, and communications for incidents that occurred during the outage are now being published. In the US2, EU2, and APJ1 data centers, generating an eBunsho timestamp was unavailable for 85 minutes. Affected users experienced an error “Timestamp: Requested,” when attempting to attach an image in Concur Expense. As the Incident Response Team (IRT) was being assembled, services self recovered. We have verified that service performance is stable and will now resolve this incident. A continued investigation into the root cause of this incident will be conducted, and a root cause analysis report provided when that investigation is complete.

2. resolved Jan 21, 2026, 10:24 PM UTC

   In the US2, EU2, and APJ1 data centers, generating an eBunsho timestamp was unavailable for 85 minutes. Affected users experienced an error “Timestamp: Requested,” when attempting to attach an image in Concur Expense. The root cause of the incident has been identified to be a service disruption within our third party Japanese Trust timestamp provider. Corrective Actions: N/A

Read the full incident report →

Started Oct 23, 2025, 01:19 AM UTC· resolved Oct 23, 2025, 03:20 AM UTC

1. resolved Oct 23, 2025, 01:50 AM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Oct 23, 2025, 02:02 AM UTC

   In the US2 Data Center, uploading, attaching, and viewing images through the SAP Concur website and SAP Concur mobile app is unavailable. Affected users may receive an error when attempting to upload, attach, or view an image. The Incident Response Team is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

3. resolved Oct 23, 2025, 02:54 AM UTC

   In the US2 Data Center, users are currently unable to upload, attach, or view images in the Expense and Invoice services when using both the SAP Concur website and the SAP Concur mobile app. When attempting to perform image-related actions, users may encounter various error messages depending on the interface being used. In Expense (Web), the error “The following files failed to upload” may appear after attempting to attach a file. In the mobile app, users may receive the message “We’re unable to attach your receipt. Please try again.” In Invoice, users may experience an application error displaying “Unexpected system error. Please try your action one more time.” A workaround for this issue is not available at this time. The IRT has identified the potential root cause and is continuing to investigate an issue affecting the connection between services responsible for processing image uploads and retrievals. Our next scheduled update will be in one hour or sooner should a significant change occur.

4. resolved Oct 23, 2025, 03:55 AM UTC

   In the US2 Data Center, users were unable to upload, attach, or view images in the Expense and Invoice services when using both the SAP Concur website and the SAP Concur mobile app. When attempting to perform image-related actions, users encountered various error messages depending on the interface used. In Expense (Web), the message “The following files failed to upload” appeared after attempting to attach a file. In the mobile app, users received the message “We’re unable to attach your receipt. Please try again.” In Invoice, users experienced an application error displaying “Unexpected system error. Please try your action one more time.” A workaround for this issue was not identified during the service disruption. Services have returned to normal operating levels. We will continue monitoring performance for the next 45-60 minutes to verify stability. Once verified as stable, the incident will be resolved.

5. resolved Oct 23, 2025, 04:54 AM UTC

   In the US2 Data Center, users were unable to upload, attach, or view images in the Expense and Invoice services when using both the SAP Concur website and the SAP Concur mobile app. When attempting to perform image-related actions, users encountered various error messages depending on the interface used. In Expense (Web), the message “The following files failed to upload” appeared after attempting to attach a file. In the mobile app, users received the message “We’re unable to attach your receipt. Please try again.” In Invoice, users experienced an application error displaying “Unexpected system error. Please try your action one more time.” The Incident Response Team (IRT) updated an application configuration and restarted related system services 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 now be conducted, and a root cause analysis report provided when that investigation is complete.

6. resolved Oct 31, 2025, 08:07 AM UTC

   Impact as Reported: In the US2 Data Center, users were unable to upload, attach, or view images in the Expense and Invoice services when using both the SAP Concur website and the SAP Concur mobile app. When attempting to perform image-related actions, users may have encountered various error messages depending on the interface being used. In Expense (Web), the error “The following files failed to upload” may appear after attempting to attach a file. In the mobile app, users may receive the message “We’re unable to attach your receipt. Please try again.” In Invoice, users may experience an application error displaying “Unexpected system error. Please try your action one more time.” Root cause: The incident response team found that a typo was inadvertently introduced to an environmental variable in the startup configuration file for a containerized application tier part of the imaging infrastructure. When the application nodes were restarted due to a routine maintenance on the container cluster hosting them, they were unable to connect to their data stores resulting in the imaging service being disrupted. Once the typo was identified the incident response team rectified the configuration file and restarted the impacted tier to load the correct configuration and restore service. Corrective Actions: The following corrective and preventive actions have been identified: during the incident it was found that the startup logging for the impacted service was insufficient to support a prompt identification of the cause for the issue: log level is being enhanced to ensure the appropriate level of diagnostic is recorded; further findings indicated that the change records kept for the service contained insufficient details to support troubleshooting: process and practices for the team operating the service are being reviewed and refreshed to enforce diligent record keeping; the code review process for configuration files changes is being reviewed and revised to ensure the appropriate level of due diligence is performed to mitigate the chance of human error; to address the challenge of identifying environment specific defects in configuration files during pre-production testing, the change deployment process is being revised to include an immediate canary test when changes are introduced, which will allow immediate defect detection without user preceivable service disruption.

Read the full incident report →

Started Oct 20, 2025, 08:02 PM UTC· resolved Oct 20, 2025, 08:12 PM UTC

1. resolved Oct 20, 2025, 09:36 PM UTC

   In the EU2 Data Center, access to Concur Travel and Analysis/Intelligence services was 90% below expected level. Affected users may have experienced a missing Travel tab, a missing Analysis or Intelligence tab, or latency when attempting to navigate to the Concur Travel and Analysis/Intelligence services. A workaround for this issue was not identified during service degradation. The Incident Response Team reverted a database server change 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 now be conducted, and a root cause analysis report provided when that investigation is complete.

2. resolved Nov 06, 2025, 09:23 AM UTC

   Impact as Reported: In the EU2 Data Center, access to Concur Travel and Analysis/Intelligence services was 90% below expected level. Affected users may have experienced a missing Travel tab, a missing Analysis or Intelligence tab, or latency when attempting to navigate to the Concur Travel and Analysis/Intelligence services. Root cause: A database supporting travel and profile related workflow was degraded, causing impact for service dependent on it.. The Incident Response Team identified that a recently implemented configuration management script being run against the impacted database was poorly optimized and was causing blocking, resulting in the service degradation . The script was stopped to restore service. Corrective Actions: The following corrective and preventative actions have been identified identified: The offending script was stopped The script has been updated to remove the causes of blocking on the target database The pre-production testing process is being updated to ensure appropriate load testing and detection of potential performance issues The development playbook for this class of scripts are being updated to implement better guidelines on optimization and performance management

Read the full incident report →

Started Sep 26, 2025, 03:05 PM UTC· resolved Sep 26, 2025, 03:28 PM UTC

1. resolved Sep 26, 2025, 04:58 PM UTC

   In the US2 Data Center, Concur Travel, Concur Expense, Concur Request, and Analysis/Intelligence customers intermittently experienced performance issues in the SAP Concur website and SAP Concur mobile app. Affected users may have been able to login however, once logged in could have encountered errors or latency when attempting to access Analysis or Intelligence, submit expense reports, submit requests, or search and book travel. A workaround was not identified during service degradation. The Incident Response Team identified and quickly resolved an issue on a database server tier. 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.

Read the full incident report →

Started Sep 22, 2025, 10:18 AM UTC· resolved Sep 22, 2025, 01:16 PM UTC

1. resolved Sep 22, 2025, 11:30 AM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Sep 22, 2025, 12:26 PM UTC

   In the China Data Center, access to the Analysis/Intelligence and Expense services through the SAP Concur website is currently below expected levels. Affected Analysis users may experience intermittent login issues or encounter the error message “Sorry, something went wrong..” upon login, while Expense users may be unable to view or access their expense Reports. The Incident Response Team is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

3. resolved Sep 22, 2025, 01:25 PM UTC

   In the China Data Center, access to the Analysis/Intelligence and Expense services through the SAP Concur website is currently below expected levels. Affected Analysis users may experience intermittent login issues or encounter the error message “Sorry, something went wrong..” upon login, while Expense users may be unable to view or access their Expense Reports. The Incident Response Team (IRT) has engaged additional resources and is actively investigating the issue. Our next scheduled update will be in one hour or sooner should a significant change occur.

4. resolved Sep 22, 2025, 01:36 PM UTC

   In the China Data Center, access to the Analysis/Intelligence and Expense services through the SAP Concur website was below expected levels. Affected Analysis users may have experienced intermittent login issues or encounter the error message “Sorry, something went wrong..” upon login, while Expense users were unable to view or access their Expense Reports. 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.

5. resolved Sep 22, 2025, 01:45 PM UTC

   In the China Data Center, access to the Analysis/Intelligence and Expense services through the SAP Concur website was below expected levels. Affected Analysis users may have experienced intermittent login issues or encounter the error message “Sorry, something went wrong..” upon login, while Expense users were unable to view or access their Expense Reports. The Incident Response Team (IRT) updated an application configuration 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 now be conducted, and a root cause analysis report provided when that investigation is complete.

6. resolved Oct 02, 2025, 02:12 PM UTC

   Impact as Reported: In the China Data Center, access to the Analysis/Intelligence and Expense services through the SAP Concur website was below expected levels. Affected Analysis users may have experienced intermittent login issues or encounter the error message “Sorry, something went wrong.” upon login, while Expense users may have been unable to view or access their Expense Reports. Root cause: The root cause of the incident has been identified in the failure of an automated process used for certificate management, causing an expiring certificate not to be renewed. The certificate was manually rotated to restore service. Corrective Actions: The certificate management process automation monitoring is being reviewed and improved to ensure failures are appropriately detected and alerted for.

Read the full incident report →