Expense, Travel, Invoice, Request, Imaging, Analysis/Intelligence: P1

Update timeline

1. resolved Mar 15, 2026, 11:39 PM UTC

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

2. resolved Mar 16, 2026, 12:02 AM UTC

   In the Concur Cloud for Public Sector Data Center, a subset of Concur Request users is experiencing an issue when completing Requests. Affected users may encounter Requests becoming stuck at the SAF Fee step during processing. As a result, these Requests cannot proceed to the next stage and remain pending. The Incident Response Team (IRT) is being assembled to start the investigation. Our next scheduled update will be in one hour or sooner should a significant change occur.

3. resolved Mar 16, 2026, 01:06 AM UTC

   In the Concur Cloud for Public Sector Data Center, a Concur Travel and Expense customer is experiencing an issue when completing Requests. Affected users may encounter Requests becoming stuck at the SAF Fee step for GO.gov during processing. As a result, these Requests cannot proceed to the next stage and remain pending. The IRT is currently investigating the issue and has engaged additional resources to determine the root cause. Our next scheduled update will be in one hour or sooner should a significant change occur.

4. resolved Mar 16, 2026, 01:50 AM UTC

   In the Concur Cloud for Public Sector Data Center, all GO.gov users are currently experiencing an issue when completing Requests. Affected users may encounter Requests becoming stuck at the SAF Fee step during processing. As a result, these Requests cannot proceed to the next stage and remain pending. At this time, no workaround is available. The Incident Response Team is actively investigating the issue and running tests to determine the root cause. Additional resources have been engaged to analyze system logs, review recent changes, and monitor related workflows. Updates on progress and any mitigation steps will be communicated as they become available. Our next scheduled update will be in one hour or sooner should a significant change occur.

5. resolved Mar 16, 2026, 02:52 AM UTC

   In the Concur Cloud for Public Sector Data Center, all GO.gov users are currently experiencing issues when completing Requests. Affected users may encounter Requests becoming stuck at the SAF Fee step during processing. As a result, these Requests cannot proceed to the next stage and remain pending. Separately, all Concur Travel and Expense users and Concur Gov users may intermittently experience latency when performing travel searches and may see the following error: "We’re sorry… We encountered an issue that prevented us from completing your request." At this time, no workaround is available for either issue. The IRT is actively investigating the issue to confirm the root cause. They are reviewing system activity, examining recent changes, and monitoring affected processes. Progress updates and any identified mitigation steps will be communicated as they become available. Our next scheduled update will be in one hour or sooner should a significant change occur.

6. resolved Mar 16, 2026, 04:03 AM UTC

   In the Concur Cloud for Public Sector Data Center, while we have seen some improvements, some GO.gov users may continue to encounter Requests becoming stuck at the SAF Fee step during processing. When adding a fee, users may experience a 504 gateway error at the API stage, preventing the Request from proceeding to the next step and leaving it pending. Additionally, the user impact for the travel issue has changed. All users across the Concur Cloud for Public Sector Data Center may intermittently experience latency when performing travel searches. Affected users may be unable to see the dropdown selection options when searching for locations. A workaround for these issues is not available at this time The Incident Response Team has identified connection errors and is actively investigating the issue to determine the underlying cause. We will provide timely updates as new information becomes available. Our next scheduled update will be in one hour or sooner should a significant change occur.

7. resolved Mar 16, 2026, 05:02 AM UTC

   In the Concur Cloud for Public Sector Data Center, while we have seen some improvements, some GO.gov users may continue to encounter Requests becoming stuck at the SAF Fee step during processing. When recalling a Request to add a fee and resubmitting it, users may encounter a 504 gateway error at the API stage, preventing the Request from proceeding to the next step and leaving it in a pending state. Additionally, the user impact for the travel issue has changed. All users across the Concur Cloud for Public Sector Data Center may intermittently experience latency when performing travel searches. Affected users may be unable to see the dropdown selection options when searching for locations. A workaround for these issues is not available at this time. The Incident Response Team is currently performing an instance refresh to determine if it will restore travel services. At the same time, the team is reviewing the Request workflows to identify the cause of the issue. Our next scheduled update will be in two hours or sooner should a significant change occur.

8. resolved Mar 16, 2026, 06:59 AM UTC

   In the Concur Cloud for Public Sector Data Center, while we have seen some improvements, some GO.gov users may continue to encounter Requests becoming stuck at the SAF Fee step during processing. When recalling a Request to add a fee and resubmitting it, users may encounter a 504 gateway error at the API stage, preventing the Request from proceeding to the next step and leaving it in a pending state. A workaround for these issues is not available at this time. The IRT continues to investigate the issue. To provide clear and focused updates, the Travel issue will now have a separate ticket and communication in Concur Open, allowing users to track each issue individually and receive timely updates on its resolution. Our next scheduled update will be in two hours or sooner should a significant change occur.

9. resolved Mar 16, 2026, 09:01 AM UTC

   In the Concur Cloud for Public Sector Data Center, while we have seen some improvements, some GO.gov users may continue to encounter Requests becoming stuck at the SAF Fee step during processing. When recalling a Request to add a fee and resubmitting it, users may encounter a 504 gateway error at the API stage, preventing the Request from proceeding to the next step and leaving it in a pending state. A workaround for these issues is not available at this time The Incident Response Team recycled the pods in the Request cluster, in order to failover the service to the best available servers. Additionally, the team is analyzing the service running on servers to make improvements. Our next scheduled update will be in two hours or sooner should a significant change occur.

10. resolved Mar 16, 2026, 10:59 AM UTC

    In the Concur Cloud for Public Sector Data Center, while we have seen some improvements, some GO.gov users may continue to encounter Requests becoming stuck at the SAF Fee step during processing. When recalling a Request to add a fee and resubmitting it, users may encounter a 504 gateway error at the API stage, preventing the Request from proceeding to the next step and leaving it in a pending state. A workaround for these issues is not available at this time The Incident Response Team has been trying to reproduce the issue in order to deploy a fix. We will also need additional information in order to continue investigation: We ask if someone on customer side to reproduce the behaviour and send a new har. file and the user experience. Our next scheduled update will be in two hours or sooner should a significant change occur.

11. resolved Mar 16, 2026, 01:01 PM UTC

    In the Concur Cloud for Public Sector Data Center, while we have seen some improvements, some GO.gov users may continue to encounter Requests becoming stuck at the SAF Fee step during processing. When recalling a Request to add a fee and resubmitting it, users may encounter a 504 gateway error at the API stage, preventing the Request from proceeding to the next step and leaving it in a pending state. A workaround for these issues is not available at this time The Incident Response Team continues to analyze the issue in order to find a root cause. Our next scheduled update will be in two hours or sooner should a significant change occur.

12. resolved Mar 16, 2026, 03:15 PM UTC

    In the Concur Cloud for Public Sector Data Center, the GO.gov users may continue to encounter Requests becoming stuck at the SAF Fee step during processing. When recalling a Request to add a fee and resubmitting it, users may encounter a 504 gateway error at the API stage, preventing the Request from proceeding to the next step and leaving it in a pending state. A workaround for these issues is not available at this time The Incident Response Team has identified our Network vendor as the likely culprit for the issues you're experiencing. We've also determined that IBM is not the only customer affected by this degradation. We appreciate you providing the additional HAR files—this has enabled our Incident Response Team (IRT) to conduct a deeper analysis while simultaneously monitoring real-time database behaviour. Our next scheduled update will be in two hours or sooner should a significant change occur.

13. resolved Mar 16, 2026, 05:19 PM UTC

    In the Concur Cloud for Public Sector Data Center, GO.gov users may experience intermittent performance issues when attempting to submit Travel Requests. Affected users may find the Requests intermittently fail to process beyond the SAF Fee Step. Recalling the request to add the fee and resubmit the Request may intermittently result in a 504 gateway error at the API stage. As a potential workaround, it may be possible to successfully submit a Travel Request after multiple attempts. The Incident Response Team (IRT) is continuing their close collaboration with the hyperscaler vendor to drive resolution efforts and align on next steps. Our next scheduled update will be in two hours or sooner should a significant change occur.

14. resolved Mar 16, 2026, 07:19 PM UTC

    In the Concur Cloud for Public Sector Data Center, GO.gov users may experience intermittent performance issues when attempting to submit Travel Requests. Affected users may find the Requests intermittently fail to process beyond the SAF Fee Step. Recalling the request to add the fee and resubmit the Request may intermittently result in a 504 gateway error at the API stage. As a potential workaround, it may be possible to successfully submit a Travel Request after multiple attempts. The IRT identified an issue with a specific instance that was experiencing a network disruption. The instance was proactively removed from service and rebooted to restore normal operation. Relevant logs were collected for analysis, and initial findings indicate a potential root cause. Our next scheduled update will be in two hours or sooner should a significant change occur.

15. resolved Mar 16, 2026, 08:44 PM UTC

    User impact since our last update changed. In the Concur Cloud for Public Sector Data Center, usg.concursolutions.com could not be accessed for a short time. When attempting to access the url, a 502 Gateway error was received. There was no workaround for this issue during the time of impact. The Incident Response Team (IRT) performed a complete refresh, which restored the ability to access usg.concursolutions.com. The IRT is currently performing a thorough assessment to confirm current impact. The Incident Response Team (IRT) is currently investigating. Current theory is root cause remains the same. Our next update will be in two hours or sooner if a significant change occurs.

16. resolved Mar 16, 2026, 10:53 PM UTC

    In the Concur Cloud for Public Sector Data Center, users may continue to experience latency or performance issues when attempting to complete various tasks or access services. Due to the intermittent nature of the issue, it may be possible to complete attempted actions with limited interruption. If you experience an error when attempting to complete tasks, multiple attempts may result in success. The Incident Response Team (IRT) is continuing their investigation to ensure system stability and recovery. Our next scheduled update will be in two hours or sooner should a significant change occur.

17. resolved Mar 17, 2026, 12:58 AM UTC

    In the Concur Cloud for Public Sector Data Center, users may continue to experience intermittent latency or performance issues when completing tasks or accessing services. The overall user experience remains unchanged, and some actions may still succeed after multiple attempts. The Incident Response Team (IRT) is actively working on adjustments and conducting tests to help stabilize the affected services and improve performance. The next update will be provided in two hours, or sooner if a significant change occurs.

18. resolved Mar 17, 2026, 02:58 AM UTC

    In the Concur Cloud for Public Sector Data Center, users may continue to experience intermittent latency or performance issues when completing tasks or accessing services. The overall user experience remains unchanged, and some actions may still succeed after multiple attempts. The Incident Response Team (IRT) is actively making updates to key parts of the system to help stabilize services and improve overall performance. As part of this work, the team will perform a system restart and run diagnostics to ensure everything is functioning correctly. The next update will be provided in two hours, or sooner if a significant change occurs.

19. resolved Mar 17, 2026, 04:58 AM UTC

    In the Concur Cloud for Public Sector Data Center, Request services have been improved. Users can now successfully add fees and move to the next steps. However, users may experience workflow routing issues, intermittent latency, or performance delays when completing other tasks or accessing other services. Some actions may require multiple attempts to complete successfully. The Incident Response Team (IRT) is actively working to resolve the issue by updating key software components that require attention. These updates are aimed at improving system stability and performance across the environment. As part of this process, the team will carefully apply the updates, monitor the system for any changes, and perform checks to ensure services are functioning as expected. The next update will be provided in two hours, or sooner if a significant change occurs.

20. resolved Mar 17, 2026, 06:21 AM UTC

    In the Concur Cloud for Public Sector Data Center, GO.gov users experienced performance issues when attempting to submit Travel Requests. Affected users encountered failures when Requests did not process beyond the SAF Fee step. Recalling the Request to add the fee and resubmitting it resulted in a 504 gateway error at the API stage. Other services were also affected, with users experiencing latency when performing various tasks or accessing those services. 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.

21. resolved Mar 17, 2026, 06:38 AM UTC

    In the Concur Cloud for Public Sector Data Center, GO.gov users experienced performance issues when attempting to submit Travel Requests. Affected users encountered failures when Requests did not process beyond the SAF Fee step. Recalling the Request to add the fee and resubmitting it resulted in a 504 gateway error at the API stage. Other services were also affected, with users experiencing latency when performing various tasks or accessing those services. The Incident Response Team (IRT) updated system components, which successfully restored services. 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.

22. resolved Aug 03, 2026, 04:20 PM UTC

    Impact as Reported: In the Concur Public Sector and Government environment user might have experienced intermittent degradation and disruption across multiple services. Root cause: The root cause of the incident has been identified in a previously undetected incompatibility between the Linux kernel version in use in the environment and the version of a security agent deployed on the hosts. The defect resulted in unpredictable and random kernel level issues causing connectivity loss, containers restarts, and other seemingly disconnection problems impacting user experience. After the agent role in the issue was identified and having engaged with its vendor, a newer version of the agent was deployed to stably restore service. Corrective Actions: The following corrective and preventive actions have been identified. - A known good version of the security agent has been rolled out to the impacted environment. - Testing and validation processes for the impacting agent are being revised to provide better detection of potential compatibility issues. - The rollout process of new agents is being revised to provide more granular control and mitigate the impact of possible escaped defects.