SAP Concur incident
Expense, Travel, Request, Imaging, Analysis/Intelligence: P1
Resolved after 31 minutes, affecting Analysis/Intelligence and Expense and 1 more, on June 28, 2026.
Impact as Reported: We identified a service degradation impacting logins. This issue impacted all users in the Concur Cloud for Public Sector Data Center. Internal monitoring and manual testing confirm systems have now recovered, and users are able to login successfully. Concur Travel and Expense users received a "Sorry Something went Wrong" error on the home page after logging in during the time of impact. Root cause: A routine automated infrastructure node rotation triggered an outage within the environment supporting authentication services. During the rotation, newly provisioned nodes were introduced into service and were incorrectly determined to be healthy based on the existing health validation mechanism. While the nodes were accepting network connections, they were not fully ready to process application traffic. As a result, customer requests were routed to nodes that had not completed initialization of all required service components. Authentication requests sent to these nodes failed, preventing users from successfully logging in and resulting in the observed user-facing errors. The investigation was unable to conclusively determine why the newly created service instances did not become fully operational. However, it identified a gap in the health validation process, which relied on basic connectivity checks rather than verifying end-to-end application readiness. This allowed traffic to be directed to partially initialized nodes and created the conditions for customer impact. Corrective Actions: Implement more comprehensive health checks that validate application readiness rather than basic connectivity alone. Introduce additional validation mechanisms to ensure newly provisioned nodes can successfully process customer traffic before being placed into service.
Affected components
Update timeline
- resolved Jun 28, 2026, 07:56 AM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved Jun 28, 2026, 08:49 AM UTC
We identified a service degradation impacting logins. This issue impacted all users in the Concur Cloud for Public Sector Data Center. Internal monitoring and manual testing confirm systems have now recovered, and users are able to login successfully. Concur Travel and Expense users received a "Sorry Something went Wrong" error on the home page after logging in during the time of impact. Workaround: During the time of impact no workaround was available. We will continue to monitor performance for the next 15 to 30 minutes to verify stability. Once stability is confirmed, this incident will be officially resolved.
- resolved Jun 28, 2026, 09:09 AM UTC
We identified a service degradation impacting logins. This issue impacted all users in the Concur Cloud for Public Sector Data Center. Concur Travel and Expense users received a "Sorry Something went Wrong" error on the home page after logging in during the time of impact. Workaround: During the time of impact no workaround was available. As the Incident Response Team (IRT) was gathering, the service self recovered. We have verified that service performance is stable and will now resolve this 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.
- resolved Aug 03, 2026, 04:58 PM UTC
Impact as Reported: We identified a service degradation impacting logins. This issue impacted all users in the Concur Cloud for Public Sector Data Center. Internal monitoring and manual testing confirm systems have now recovered, and users are able to login successfully. Concur Travel and Expense users received a "Sorry Something went Wrong" error on the home page after logging in during the time of impact. Root cause: A routine automated infrastructure node rotation triggered an outage within the environment supporting authentication services. During the rotation, newly provisioned nodes were introduced into service and were incorrectly determined to be healthy based on the existing health validation mechanism. While the nodes were accepting network connections, they were not fully ready to process application traffic. As a result, customer requests were routed to nodes that had not completed initialization of all required service components. Authentication requests sent to these nodes failed, preventing users from successfully logging in and resulting in the observed user-facing errors. The investigation was unable to conclusively determine why the newly created service instances did not become fully operational. However, it identified a gap in the health validation process, which relied on basic connectivity checks rather than verifying end-to-end application readiness. This allowed traffic to be directed to partially initialized nodes and created the conditions for customer impact. Corrective Actions: Implement more comprehensive health checks that validate application readiness rather than basic connectivity alone. Introduce additional validation mechanisms to ensure newly provisioned nodes can successfully process customer traffic before being placed into service.
Your product runs on more than SAP Concur
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services