Resolved after 49 minutes, affecting Expense, on March 16, 2016.
Expense was intermittently unavailable. There were two distinct failures, both related to our load balancing solution, and when combined, created a situation that resulted in an inability to connect to the Concur servers. Both issues have been identified and are known by the vendor of our load balancing solution. They will be issuing a software update that we can then apply in our Data Centers.
Affected components
Update timeline
- investigating Mar 16, 2016, 11:11 PM UTC
An issue was identified and has been resolved. We will provide the root cause analysis as soon as possible.
- investigating Mar 30, 2016, 02:44 PM UTC
Expense was intermittently unavailable. There were two distinct failures, both related to our load balancing solution, and when combined, created a situation that resulted in an inability to connect to the Concur servers. Both issues have been identified and are known by the vendor of our load balancing solution. They will be issuing a software update that we can then apply in our Data Centers.
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