SAP Concur Outage History

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.

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.

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.

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

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.