Travel: P1

Update timeline

1. resolved Mar 17, 2026, 07:27 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Mar 17, 2026, 08:05 PM UTC

   In the Concur Cloud for Public Sector Data Center, Lodging Per Diem rates are incorrectly calculated for go.gov customers. When hotel search results are returned, the Lodging Per Diem limit is calculated at $55 for all locations, which is incorrectly flagging most hotels as a policy violation. A workaround has not been identified at this time. The Incident Response Team (IRT) has gathered and an investigation has begun. An update will be provided in one hour or sooner should a significant change occur.

3. resolved Mar 17, 2026, 08:58 PM UTC

   In the Concur Cloud for Public Sector Data Center, Lodging Per Diem rates are incorrectly calculated for go.gov customers. When hotel search results are returned, the Lodging Per Diem limit is calculated at $55 for all locations, which is incorrectly flagging most hotel as a policy violation. A workaround has not been identified at this time. The Incident Response Team (IRT) has performed a review of internal logs. An additional investigation is underway regarding a recent change as a potential root cause. An update will be provided in two hours or sooner should a significant change occur.

4. resolved Mar 17, 2026, 10:33 PM UTC

   In the Concur Cloud for Public Sector Data Center, Lodging Per Diem rates are incorrectly calculated for GO.gov customers. When hotel search results are returned, the Lodging Per Diem limit is calculated at $55 for all locations, which is incorrectly flagging most hotels as a policy violation. A workaround has not been identified at this time. The Incident Response Team (IRT) is continuing their investigation, focusing on a recent change as the potential root cause. An update will be provided in two hours or sooner should a significant change occur.

5. resolved Mar 18, 2026, 12:30 AM UTC

   In the Concur Cloud for Public Sector Data Center, Lodging Per Diem rates are incorrectly calculated for GO.gov customers. When hotel search results are returned, the Lodging Per Diem limit is calculated at $55 for all locations, which is incorrectly flagging most hotels as a policy violation. A workaround has not been identified at this time. Following a thorough investigation, it was determined that the root cause of this issue was a recent fix deployed for a P2 issue that addressed the inability to use the “Add Hotel” function for previously reserved reservations or trips on hold. To resolve the incorrect lodging per diem calculations, the recent change has been reverted. A fix is being prepared and tested, and once it’s confirmed to be working, it will be deployed to the production environment. Please note that the Incident Response Team (IRT) will continue working to restore the “Add Hotel” functionality with the proper urgency assigned to a P2 impacted business process. An update will be provided in two hours or sooner should a significant change occur.

6. resolved Mar 18, 2026, 02:30 AM UTC

   In the Concur Cloud for Public Sector Data Center, Lodging Per Diem rates are incorrectly calculated for GO.gov customers. When hotel search results are returned, the Lodging Per Diem limit is calculated at $55 for all locations, which is incorrectly flagging most hotels as a policy violation. A workaround has not been identified at this time. The Incident Response Team (IRT) has deployed the fix to an internal test environment with successful results. The team is now working to deploy the fix to the production environment. An update will be provided in two hours or sooner should a significant change occur.

7. resolved Mar 18, 2026, 04:30 AM UTC

   In the Concur Cloud for Public Sector Data Center, Lodging Per Diem rates are incorrectly calculated for GO.gov customers. When hotel search results are returned, the Lodging Per Diem limit is calculated at $55 for all locations, which is incorrectly flagging most hotels as a policy violation. A workaround for this issue is not available at this time The Incident Response Team (IRT) continues to work on deploying the fix to the production environment to restore service. An update will be provided in two hours or sooner should a significant change occur.

8. resolved Mar 18, 2026, 06:30 AM UTC

   In the Concur Cloud for Public Sector Data Center, Lodging Per Diem rates are incorrectly calculated for GO.gov customers. When hotel search results are returned, the Lodging Per Diem limit is calculated at $55 for all locations, which is incorrectly flagging most hotels as a policy violation. A workaround for this issue is not available at this time The Incident Response Team (IRT) addressed a minor issue encountered during deployment. The team is continuing the rollout to restore full service as quickly as possible. An update will be provided in two hours or sooner should a significant change occur.

9. resolved Mar 18, 2026, 08:07 AM UTC

   In the Concur Cloud for Public Sector Data Center, lodging per diem rates were incorrectly calculated for GO.gov customers. When hotel search results were returned, the lodging per diem limit was calculated at $55 for all locations, which incorrectly flagged most hotels as policy violations. Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

10. resolved Mar 18, 2026, 08:41 AM UTC

    In the Concur Cloud for Public Sector Data Center, Lodging Per Diem rates were incorrectly calculated for go.gov customers. When hotel search results were returned, the Lodging Per Diem limit was calculated at $55 for all locations, which is incorrectly flagging most hotel as a policy violation. Following a thorough investigation, it was determined that the root cause was a recent fix deployed for a P2 issue that addressed the inability to use the “Add Hotel” function for previously reserved reservations or trips on hold. To resolve the miscalculated lodging per diem rates, that change has been reverted. Please note that the Incident Response Team (IRT) will continue working to restore the “Add Hotel” functionality with the proper urgency assigned to a P2 impacted business process. The system revert has been completed and lodging per diem rates are now calculating as expected. A root cause investigation will be conducted, and a report will be shared once the investigation is complete.

11. resolved Aug 03, 2026, 04:36 PM UTC

    Impact as Reported: Per-diem rate being shown is incorrect which is affecting users booking hotel locations in the US. Root cause: A code change was deployed on March 16, 2026 to fix an existing per-diem issue. A new Hotel specific function deployed as part of the change was incorrectly used in the shopping processing page, resulting in faulty requests being sent to the Per Diem service and responses with an incorrect default value being returned. The code change was rolled back to restore service to normal. Corrective Actions: Our testing capabilities for per-diem features are being reviewed and additional test scenarios added to ensure faulty code is detected prior to deployments. Additional monitoring and alerting will be implement to provide early detection of per-diem failures and strengthen our observability and reaction to incidents. Triaging and troubleshooting documentation is also being updated.