Stayntouch incident

Performance and Interface Communication Issues

Major Resolved View vendor source →

Stayntouch experienced a major incident on September 21, 2018 affecting Stayntouch PMS and Interfaces, lasting 3d 6h. The incident has been resolved; the full update timeline is below.

Started
Sep 21, 2018, 12:50 PM UTC
Resolved
Sep 24, 2018, 07:30 PM UTC
Duration
3d 6h
Detected by Pingoru
Sep 21, 2018, 12:50 PM UTC

Affected components

Stayntouch PMSInterfaces

Update timeline

  1. investigating Sep 21, 2018, 12:50 PM UTC

    We have identified an issue in Rover that is resulting in slow performance and a loss of communication between the PMS and some external interfaces.

  2. investigating Sep 21, 2018, 12:51 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Sep 21, 2018, 01:07 PM UTC

    IFC appears to be stable now and database is running. Performance also appears to have been improved. We are continuing to monitor and look into the core issues. It is recommended to run a resync from the external CRS with Rover PMS to match inventory and reservations.

  4. monitoring Sep 21, 2018, 07:55 PM UTC

    We are continuing to monitor this issue over the weekend and have implemented an improved retry mechanism and error reporting to prevent recurrence.

  5. monitoring Sep 21, 2018, 07:56 PM UTC

    We are continuing to monitor this issue over the weekend and have implemented an improved retry mechanism and error reporting to prevent recurrence.

  6. monitoring Sep 24, 2018, 03:35 PM UTC

    StayNTouch's applications and platform vendor, Rackspace, has identified an intermittent performance issue with their systems and is working to resolve it. The reported issues from last week were a result of this. Rackspace will update us shortly with the timeframe within which they will be performing the steps needed to correct the performance issue. The maintenance window will be notified via the StayNTouch status page and announcement portal.

  7. monitoring Sep 24, 2018, 07:29 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved Sep 24, 2018, 07:30 PM UTC

    This incident has been resolved.