SAP Concur incident

Travel: P1

Resolved after 1 hour, affecting Travel, on February 15, 2016.

investigating Feb 19, 2016, 01:57 PM UTC

Travel was intermittently unavailable. Users experienced errors or slow processing when attempting to search and book travel. The cause of this issue was due to improper handling of a database cluster during the maintenance window. To resolve this issue, multiple databases were moved back to their original host. To prevent reoccurrence, we are updating our documents and providing additional training.

Started
Feb 15, 2016, 03:50 PM UTC
Resolved
Feb 15, 2016, 04:50 PM UTC
Duration
1h
Detected by Pingoru
Feb 15, 2016, 03:50 PM UTC

Affected components

Travel

Update timeline

  1. investigating Feb 15, 2016, 06:05 PM UTC

    An issue was identified and has been resolved. We will provide the root cause analysis as soon as possible.

  2. investigating Feb 19, 2016, 01:57 PM UTC

    Travel was intermittently unavailable. Users experienced errors or slow processing when attempting to search and book travel. The cause of this issue was due to improper handling of a database cluster during the maintenance window. To resolve this issue, multiple databases were moved back to their original host. To prevent reoccurrence, we are updating our documents and providing additional training.

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 →