Repsly incident

[Web] [Mobile] Service degraded

Major Resolved View vendor source →

Repsly experienced a major incident on February 4, 2019 affecting Web and Mobile, lasting 6h 39m. The incident has been resolved; the full update timeline is below.

Started
Feb 04, 2019, 05:42 AM UTC
Resolved
Feb 04, 2019, 12:21 PM UTC
Duration
6h 39m
Detected by Pingoru
Feb 04, 2019, 05:42 AM UTC

Affected components

WebMobile

Update timeline

  1. investigating Feb 04, 2019, 05:42 AM UTC

    We have identified and are working on resolving an issue with our service at the moment. We're working hard to solve this problem as soon as possible. Please try again later or reach out to [email protected] to request an update when this issue has been resolved.

  2. identified Feb 04, 2019, 06:37 AM UTC

    The issues we're experiencing are directly related to Elasticsearch cluster service we're using. Those issues have been mitigated and the service is in the process of recovery at this moment.

  3. identified Feb 04, 2019, 08:10 AM UTC

    All services operational except Activity feed and Scheduling on both web and mobile apps. We are working on a full recovery.

  4. monitoring Feb 04, 2019, 10:13 AM UTC

    All systems in both web and mobile apps are now operational and we're monitoring the results. If you experience any issues please contact us at [email protected].

  5. resolved Feb 04, 2019, 12:21 PM UTC

    All systems in both web and mobile apps are now operational