SAP Concur incident

Travel: P1

Resolved after 3 hours 10 minutes, affecting Travel, on October 16, 2015.

investigating Oct 28, 2015, 05:16 PM UTC

The cause of this disruption was due to an increase in the logging data collected leading to degraded functionality of the servers. To resolve this issue, old logs were deleted and the service was restarted. We are researching processes and procedures to prevent reoccurrence.

Started
Oct 16, 2015, 01:40 PM UTC
Resolved
Oct 16, 2015, 04:50 PM UTC
Duration
3h 10m
Detected by Pingoru
Oct 16, 2015, 01:40 PM UTC

Affected components

Travel

Update timeline

  1. investigating Oct 16, 2015, 02:35 PM UTC

    We are experiencing a system outage and are investigating. Please check back for updated information. Thank-you.

  2. investigating Oct 16, 2015, 03:02 PM UTC

    Users are experiencing errors or slow processing when performing administrative functions or attempting to search or book travel. We appreciate your patience while we work to resolve this issue.

  3. investigating Oct 16, 2015, 05:06 PM UTC

    Services are available and running normally. We are monitoring the system to ensure expected service levels are sustained before declaring the issue has been resolved.

  4. investigating Oct 16, 2015, 05:54 PM UTC

    We have resolved the issue and will provide the root cause analysis as soon as possible.

  5. investigating Oct 28, 2015, 05:16 PM UTC

    The cause of this disruption was due to an increase in the logging data collected leading to degraded functionality of the servers. To resolve this issue, old logs were deleted and the service was restarted. We are researching processes and procedures to prevent reoccurrence.

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.

Add your stack →