SAP Concur incident

Travel: P1

Resolved after 1 day 5 hours, affecting Travel, on August 18, 2015.

investigating Oct 15, 2015, 12:48 AM UTC

Travel was intermittently unavailable. Users were unable to log in and if already logged in, were logged out. Users experienced errors or slow processing when performing administrative functions or attempting to see arch or book travel. The cause of this issue was due to increased memory pressure on our servers leading to an increased error rate. To resolve the issue, a hotfix was applied. We have created an automatic process to detect and prevent future reoccurrence.

Started
Aug 18, 2015, 01:48 PM UTC
Resolved
Aug 19, 2015, 07:29 PM UTC
Duration
1d 5h
Detected by Pingoru
Aug 18, 2015, 01:48 PM UTC

Affected components

Travel

Update timeline

  1. investigating Aug 18, 2015, 05:43 PM UTC

    Initial Impact Assessment: We are experiencing a system partial performance issue and are investigating. Please check back for updated information. Thank-you.

  2. investigating Aug 18, 2015, 09:41 PM UTC

    Update: We have partially resolved the incident and continue to work on a resolution for the issue impacting performance for our clients using Sabre.

  3. investigating Aug 19, 2015, 04:13 PM UTC

    Update: Users may continue to experience errors or slow processing when attempting to search or book travel via Sabre. However, less than 5 percent of all activity is impacted.

  4. investigating Aug 19, 2015, 08:29 PM UTC

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

  5. investigating Oct 15, 2015, 12:48 AM UTC

    Users may continue to experience errors or slow processing when attempting to search or book travel via Sabre. However, less than 5 percent of all activity is impacted.

  6. investigating Oct 15, 2015, 12:48 AM UTC

    Travel was intermittently unavailable. Users were unable to log in and if already logged in, were logged out. Users experienced errors or slow processing when performing administrative functions or attempting to see arch or book travel. The cause of this issue was due to increased memory pressure on our servers leading to an increased error rate. To resolve the issue, a hotfix was applied. We have created an automatic process to detect and prevent future 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 →