Personalized SAP Concur Open Updates
Personalized up-to-the-minute service availability and performance information
-
OPI-5960257 : US2 : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence : Issue Resolved
20 December 2024 | 3:12 pm
In the US2 Data Center, logins through the SAP Concur website app and SAP Concur mobile app was below expected levels. Affected users may have experienced intermittent login errors, stating, "Sorry, something went wrong," "Sorry, Concur is currently unavailable." or "502 bad gateway error" when attempting to log in. A possible workaround was identified. Users may have been able to successfully login after refreshing the page. The Incident Response Team (IRT) performed a configuration change 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.
-
OPI-5960257 : US2 : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence : Issue Status Update
20 December 2024 | 2:43 pm
In the US2 Data Center, logins through the SAP Concur website app and SAP Concur mobile app was below expected levels. Affected users may have experienced intermittent login errors, stating, "Sorry, something went wrong," "Sorry, Concur is currently unavailable." or "502 bad gateway error" when attempting to log in. A possible workaround was identified. Users may have been able to successfully login after refreshing the page. 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-5960257 : US2 : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence : Issue Status Update
20 December 2024 | 2:06 pm
In the US2 Data Center, login activity through both the SAP Concur website and the SAP Concur mobile app is below expected levels. Affected users may encounter intermittent login errors, such as "Sorry, something went wrong," "Sorry, Concur is currently unavailable," or a "502 Bad Gateway" error. A possible workaround has been identified. Users may be able to successfully login after refreshing the page. The Incident Response Team (IRT) is continuing their investigation to identify a fix. Our next scheduled update will be in one hour or sooner should a significant change occur.
-
OPI-5960257 : US2 : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence : Issue Status Update
20 December 2024 | 1:07 pm
In the US2 Data Center, login activity through both the SAP Concur website and the SAP Concur mobile app is below expected levels. Affected users may encounter intermittent login errors, such as "Sorry, something went wrong," "Sorry, Concur is currently unavailable," or a "502 Bad Gateway" error. A possible workaround has been identified. Users may be able to successfully login after refreshing the page. The Incident Response Team (IRT) has identified blocking on a server tier and is currently investigating the best course of action to resolve the issue. While they have already performed some performance optimization actions, they are still observing some instability and are actively working to resolve the problem.
-
OPI-5960257 : US2 : Expense | Travel | Invoice | Request | Imaging | Analysis/Intelligence : Issue Status Update
20 December 2024 | 12:07 pm
User impact since the last update remains unchanged. In the US2 Data Center, login activity through both the SAP Concur website and the SAP Concur mobile app is below expected levels. Affected users may encounter intermittent login errors, such as "Sorry, something went wrong," "Sorry, Concur is currently unavailable," or a "502 Bad Gateway" error. A possible workaround has been identified. Users may be able to successfully login after refreshing the page. The Incident Response Team (IRT) has engaged additional resources and is collecting further data for a more thorough investigation. Our next update will be provided in one hour or sooner if a significant change occurs.