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

Update timeline

1. resolved Mar 16, 2026, 05:51 AM UTC

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

2. resolved Mar 16, 2026, 06:00 AM UTC

   All Travel 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 this issue is not available at this time The IRT has been assembled and is currently taking steps to restore service. Our next scheduled update will be in two hours or sooner should a significant change occur.

3. resolved Mar 16, 2026, 07:57 AM UTC

   All Travel 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 this issue is not available at this time. The Incident Response Team (IRT) is continuing to investigate the root cause of the issue to facilitate resolution of the incident. Our next scheduled update will be in two hours or sooner should a significant change occur.

4. resolved Mar 16, 2026, 09:57 AM UTC

   All Travel 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 this issue is not available at this time. The Incident Response Team (IRT) has refreshed the pods to check if it resolves the issue, but the problem persists. The IRT is now engaging additional resources to continue the investigation. Our next scheduled update will be in four hours or sooner should a significant change occur.

5. resolved Mar 16, 2026, 02:14 PM UTC

   Since our previous update the impact has changed. Travel users across the Concur Cloud for Public Sector Data Center may be able to successfully search for airports, but may still occasionally experience intermittent latency when performing travel searches. A workaround for this issue is not available at this time. The Incident Response Team (IRT) continues investigation with our Network vendor. Currently they are analyzing the node logs with the vendor in order to find a root cause. Our next scheduled update will be in four hours or sooner should a significant change occur.

6. resolved Mar 16, 2026, 05:56 PM UTC

   In the Concur Cloud for Public Sector Data Center, when attempting to perform Flight Searches, you may experience intermittent latency and performance issues. As a workaround, it may be possible to successfully perform a Flight Search 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 four hours or sooner should a significant change occur.

7. resolved Mar 16, 2026, 08:42 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.

8. resolved Mar 16, 2026, 10:51 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.

9. 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.

10. 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.

11. resolved Mar 17, 2026, 04: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 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.

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

    In the Concur Cloud for Public Sector Data Center, users experienced latency or performance issues when attempting to complete various tasks or access 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.

13. resolved Mar 17, 2026, 06:37 AM UTC

    In the Concur Cloud for Public Sector Data Center, users experienced latency or performance issues when attempting to complete various tasks or access 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.

14. resolved Aug 03, 2026, 04:25 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.