Resolved after 1 hour 40 minutes, affecting Analysis/Intelligence, on May 17, 2025.
Impact as Reported: In the China Data Center, access to the Analysis/Intelligence service through the SAP Concur website was below expected level. Affected users may have experienced following error: "Warning. Either ReportNet is currently unavailable or there was a problem with login authorisation. Please try again. If there is a problem persists, contact your expense administrator or assistance" when attempting to access the Reporting tab. Root cause: A scheduled database maintenance promoted a secondary node to primary, but due to DNS unexpectedly failing to update the Analytics service was unable to connect to the database after the promotion. The Incident Response team restored the previous database to primary to return service to normal. The cause for the failed DNS update is still being investigated, and a full root cause with relevant corrective actions will be posted as soon as available. Corrective Actions: Corrective actions will be determined once the root cause has been fully identified.
Affected components
Update timeline
- resolved May 17, 2025, 08:01 PM UTC
We are working to determine the user impact and will provide information as it becomes available.
- resolved May 17, 2025, 08:21 PM UTC
In the China Data Center, access to the Analysis/Intelligence service through the SAP Concur website is below expected level. Affected users may experience following error: "Warning. Eather ReoirtNet is currently unavailable or there was a problem with login authorisation. Please try again. If there is a problem persists, contact your expense administrator or assistance." When attempting to access the Reporting tab. The Incident Response Team (IRT) has been engaged and are investigating. Our next scheduled update will be in one hour or sooner, should a significant change occur
- resolved May 17, 2025, 08:48 PM UTC
In the China Data Center, access to the Analysis/Intelligence service through the SAP Concur website was below expected level. Affected users may have experienced following error: "Warning. Eather ReportNet is currently unavailable or there was a problem with login authorisation. Please try again. If there is a problem persists, contact your expense administrator or assistance." When attempting to access the Reporting tab. 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.
- resolved May 17, 2025, 09:00 PM UTC
In the China Data Center, access to the Analysis/Intelligence service through the SAP Concur website was below expected level. Affected users may have experienced following error: "Warning. Eather ReportNet is currently unavailable or there was a problem with login authorisation. Please try again. If there is a problem persists, contact your expense administrator or assistance." When attempting to access the Reporting tab. The Incident Response Team (IRT) performed a failover on the database server tier to restore the 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.
- resolved May 30, 2025, 01:38 PM UTC
Impact as Reported: In the China Data Center, access to the Analysis/Intelligence service through the SAP Concur website was below expected level. Affected users may have experienced following error: "Warning. Either ReportNet is currently unavailable or there was a problem with login authorisation. Please try again. If there is a problem persists, contact your expense administrator or assistance" when attempting to access the Reporting tab. Root cause: A scheduled database maintenance promoted a secondary node to primary, but due to DNS unexpectedly failing to update the Analytics service was unable to connect to the database after the promotion. The Incident Response team restored the previous database to primary to return service to normal. The cause for the failed DNS update is still being investigated, and a full root cause with relevant corrective actions will be posted as soon as available. Corrective Actions: Corrective actions will be determined once the root cause has been fully identified.
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