Training
Fox World Travel Concur Support Desk
Fox World Travel is available to support your Concur questions. Contact support via phone at 608-710-4172 or via chat in the Concur application.
Forgot Password?
Submit a request to Concur for a password reset. Your username is your current institutional email address.
New User Registration
Concur registration for new users. Registration is limited to employees. The use of a university e-mail address is required for user name.
Additional Support
Contact your institution’s travel manager for additional support questions.
Personalized SAP Concur Open Updates
Personalized up-to-the-minute service availability and performance information
-
OPI-6008583 : US2 | EU2 | APJ1 : Travel : Root Cause Analysis
19 May 2025 | 2:29 am
Impact as Reported: In the US,EU2 and APJ Data Centers, air bookings via Galileo, Worldspan and Apollo GDS vendors through the SAP Concur website and SAP Concur mobile app were unavailable. Affected users may have encountered the following error message: “Sorry, we are unable to return search results, which may be due to: your company’s travel policy...” when attempting to perform air bookings. Root cause: The root cause of the incident has been identified to be a service disruption at one of our third party GDS vendors. Corrective Actions: N/A
-
OPI-6002076 : US2 | EU2 | APJ1 : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence : Root Cause Analysis
15 May 2025 | 10:57 am
In the EU2, US2, and APJ1 Data Centers, logging in through the SAP Concur website and SAP Concur mobile app was unavailable. The affected users would get “Sorry, something went wrong” upon trying to access SAP Concur services. An outage on a geo-blocking service responsible for the scanning and validation of incoming traffic origin, necessary to prevent access from embargoed countries, caused all inbound traffic to be blocked. The reason behind the failure was a version upgrade on a core component of the geo-blocking service that resulted in missing certificates information and consequent clients connection failure to both the primary and the back-up endpoints. This resulted in the CTE authentication service to prevent access for all users. The proxy service responsible for handling the connection between CT&E and the geo-blocking service has been updated to a new version that allows dynamic parameters to be used for the TLS handshake, removing the dependency on the information that went missing on the certificate, hence removing the dependency that caused the connection to the geo-blocking back up endpoints to fail.