SAP Concur incident

Expense, Travel, Invoice, Request, Imaging, Analysis/Intelligence: P1

Resolved after 15 minutes, affecting Analysis/Intelligence and Expense and 1 more, on September 19, 2025.

resolved Oct 06, 2025, 07:04 AM UTC

Impact as Reported: In the US2 Data Center, logging in through the SAP Concur website and SAP Concur mobile app was unavailable for approximately 15 minutes. Affected users may have encountered, “Sorry, something went wrong” after entering SAP Concur username or SSO credentials. A workaround was not identified during service disruption. Root cause: A vendor providing a DNS layer security service suffered a brief outage that resulted in an unexpected impact to name resolution within the SAP Concur US2 data centre, causing loss of connectivity and consequently service unavailabilty. As soon as the incident was resolved by the vendor service was restored. Corrective Actions: The following corrective or preventive actions have been identified: monitoring of the third party service is being revised to ensure prompt detection of issues alternative security services are being explored to allow the configuration of a fall back in case of outages the network team is exploring the option of implementing an additional caching layer to mitigate the impact of incidents on the DNS layer security service.

Started
Sep 19, 2025, 07:39 PM UTC
Resolved
Sep 19, 2025, 07:54 PM UTC
Duration
15m
Detected by Pingoru
Sep 19, 2025, 07:39 PM UTC

Affected components

Analysis/IntelligenceExpenseImagingInvoiceRequestTravel

Update timeline

  1. resolved Sep 19, 2025, 09:11 PM UTC

    In the US2 Data Center, logging in through the SAP Concur website and SAP Concur mobile app was unavailable for approximately 15 minutes. Affected users may have encountered, “Sorry, something went wrong” after entering SAP Concur username or SSO credentials. A workaround was not identified during service disruption. As the Incident Response Team was being assembled, the service self-restored. 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 Oct 06, 2025, 07:04 AM UTC

    Impact as Reported: In the US2 Data Center, logging in through the SAP Concur website and SAP Concur mobile app was unavailable for approximately 15 minutes. Affected users may have encountered, “Sorry, something went wrong” after entering SAP Concur username or SSO credentials. A workaround was not identified during service disruption. Root cause: A vendor providing a DNS layer security service suffered a brief outage that resulted in an unexpected impact to name resolution within the SAP Concur US2 data centre, causing loss of connectivity and consequently service unavailabilty. As soon as the incident was resolved by the vendor service was restored. Corrective Actions: The following corrective or preventive actions have been identified: monitoring of the third party service is being revised to ensure prompt detection of issues alternative security services are being explored to allow the configuration of a fall back in case of outages the network team is exploring the option of implementing an additional caching layer to mitigate the impact of incidents on the DNS layer security service.

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.

Add your stack →