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

  1. OPI-5965420 : US2 | EU2 : Expense | Travel | Invoice | Request | Mobile : Root Cause Analysis

    In the US2 and EU2 Data Centers, access to Concur Expense, Concur Invoice, Concur Travel, and Concur Request was below expected level. Affected users may have experienced errors when attempting to navigate through or complete tasks within the Concur Expense, Concur Invoice, Concur Travel and Concur Request services. The root cause of the incident has been determined to be an abnormally high volume of internal DNS requests that lead to throttling and timeouts on the name server, causing service degradation. The source of the unexpected traffic could not be determined with the available logging capabilities. Enhanced logging has been implemented to enable us to capture the source of the unexpected traffic in the event a similar incident would re-occur. Changes to the DNS resolver configuration have been implemented in order to remove the throttling limit, allowing processing of increased requests volume in the event that would occur. Additional monitoring and alerting will also be configured for better detection and response.

  1. OPI-5960257 : US2 : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence : Intermediate Root Cause Analysis

    Impact as Reported: In the US2 Data Center, logins through the SAP Concur website app and SAP Concur mobile app was below expected levels. Affected users may have experienced intermittent login errors, stating, "Sorry, something went wrong," "Sorry, Concur is currently unavailable." or "502 bad gateway error" when attempting to log in. A possible workaround was identified. Users may have been able to successfully login after refreshing the page. Root cause: The incident response team determined that intermittent connection failures between a gateway component and the containers running the sign in service were causing the gateway component to mark the nodes hosting the containers as unavailable, repeatedly leading to brief intervals during which the component was left with no valid target to send sign in requests to and resulting in sporadic log in errors for the end users. Mitigation was implemented by updating the gateway component configuration to not mark a target as unavailable after a single connection failures - as subsequent findings indicated that some of the nodes hosting the sign in service containers might have been degraded all nodes were replaced to further ensure service stability. The root cause of the connection failures is still under investigation, and it will be provided together with relevant corrective and preventive actions as soon as the investigation is complete. Corrective Actions: NA