Resolved after 13 minutes, affecting Analysis/Intelligence, on February 10, 2025.
In the EU2 Data Center, access to the Analysis/Intelligence service through the SAP Concur website was unavailable for 82% of customers. Affected users may have encountered an error, "403 Forbidden" when attempting to access the Analysis/Intelligence link under the Reporting tab. An update deployed to the Analytic service caused connectivity issues between it and the rest of the Concur product. The incident response team identified found that a configuration value needed to allow connectivity had been inadvertently left out from the update. The configuration was updated to restore connectivity. Corrective Actions: The following corrective actions were identified: - Update the code to include the additional configuration value - Add a dashboard to our monitoring to better track the errors for quicker triaging and resolution.
Affected components
Update timeline
- resolved Feb 10, 2025, 09:43 PM UTC
In the EU2 Data Center, access to the Analysis/Intelligence service through the SAP Concur website was unavailable for 82% of customers. Affected users may have encountered an error, "403 Forbidden" when attempting to access the Analysis/Intelligence link under the Reporting tab. The Incident Response Team (IRT) determined the root cause was a recent change, and immediately took action to update the necessary configuration to restore service. 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.
- resolved Mar 13, 2025, 08:01 PM UTC
In the EU2 Data Center, access to the Analysis/Intelligence service through the SAP Concur website was unavailable for 82% of customers. Affected users may have encountered an error, "403 Forbidden" when attempting to access the Analysis/Intelligence link under the Reporting tab. An update deployed to the Analytic service caused connectivity issues between it and the rest of the Concur product. The incident response team identified found that a configuration value needed to allow connectivity had been inadvertently left out from the update. The configuration was updated to restore connectivity. Corrective Actions: The following corrective actions were identified: - Update the code to include the additional configuration value - Add a dashboard to our monitoring to better track the errors for quicker triaging and resolution.
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