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, via email at online@foxworldtravel.com or via chat in the Concur application.
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-6218284 : US2 : Travel : Root Cause Analysis
9 April 2026 | 1:14 am
Impact as Reported: In the US2 Data Center, New Concur Travel bookings were 30% below expected level. Affected users may have experienced latency and performance issues. when accessing the travel page and attempting to perform booking related tasks. Root cause: Due to resource throttling available CPU was increased on a container custer to maintain performance. However, with average CPU usage having been lowered, the containers automatically scaled down to the configured minimum number of pods, which was not sufficient to handle incoming traffic. The Incident Response team increased the number of pods to fully restore the service. Corrective Actions: The following corrective and preventative actions were identified: Additional metrics are being configure as auto-scaling triggers to maintain the optimal number of pods Monitoring is being updated to alert when pods scale down to minimum
-
OPI-6218865 : US2 : Expense | Travel : Root Cause Analysis
9 April 2026 | 1:11 am
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