Personalized SAP Concur Open Updates
Personalized up-to-the-minute service availability and performance information
-
OPI-6138380 : US2 : Travel : Root Cause Analysis
12 November 2025 | 2:26 am
Impact as Reported: New Concur Travel bookings dropped up to 50 % below expected level for 31 minutes in the US2 Data Center. Affected users may have experienced latency, no response, or errors when attempting to perform travel searches or complete travel bookings. Root cause: An application tier supporting travel related workflows experienced performance degradation, resulting in intermittent time outs that impacted users ability to search or book. The Incident Response Team identified an issue with the service infrastructure configuration allocating insufficient memory to process increased load, causing application nodes to fail life checks and be taken out of service, reducing the available processing capacity. Service was restored by increasing the affected application tier capacity. Corrective Actions: The following corrective and preventive actions were identified: Increase the application tier baseline capacity Increase the memory allocated to the tier nodes Review service dependencies and remove unnecessary checks Review auto-scaling configurations for the impacted service to improve scale up parameters to better respond to load changes.
-
OPI-6151556 : US2 | EU2 : Travel : Issue Resolved
3 November 2025 | 10:55 pm
In the US2 and EU2 Data Centers, completing travel searches in Legacy Travel using the GDS services Apollo and Galileo was below the expected level. The SAP Concur mobile app did not appear to be affected. Affected Legacy Travel users may have encountered the following error message when searching for travel “We’re Sorry… We encountered an issue that prevented us from completing your request.” The Incident Response Team received confirmation that issue was caused by our Concur partner vendor and actions were taken to restore service. 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.
-
OPI-6151556 : US2 | EU2 : Travel : Issue Status Update
3 November 2025 | 10:42 pm
In the US2 and EU2 Data Centers, completing travel searches in Legacy Travel using the GDS services Apollo and Galileo was below the expected level. The SAP Concur mobile app did not appear to be affected. Affected Legacy Travel users may have encountered the following error message when searching for travel “We’re Sorry… We encountered an issue that prevented us from completing your request.” 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.
-
OPI-6151556 : US2 | EU2 : Travel : Issue Status Update
3 November 2025 | 10:20 pm
In the US2 and EU2 Data Centers, when doing travel searches in Legacy Travel using the GDS services Apollo and Galileo is currently below expected level. The SAP Concur mobile app does not appear to be affected. Affected Legacy Travel users may encounter the following error message when searching for travel “We’re Sorry… We encountered an issue that prevented us from completing your request.” There is no workaround available at this time. The Incident Response Team, together with our Concur partner vendor, is actively working on a fix. The next scheduled update will be provided in one hour, or sooner if a significant change occurs.
-
OPI-6151556 : US2 | EU2 : Travel : Issue Status Update
3 November 2025 | 9:35 pm
In the US2 and EU2 Data Centers, completing travel searches through the SAP Concur website using the GDS services Apollo and Galileo is currently unavailable. SAP Concur mobile app does not appear to be affected. Affected users may encounter the following error message when searching for hotels: “We’re Sorry… We encountered an issue that prevented us from completing your request.” There is no workaround available at this time. The Incident Response Team is actively investigating. The next scheduled update will be provided in one hour, or sooner if a significant change occurs.