InterviewStream incident

Unable to Access RIVS

Critical Resolved View vendor source →

InterviewStream experienced a critical incident on May 23, 2022 affecting interviewstream on demand and interviewstream connect and 1 more component, lasting 48m. The incident has been resolved; the full update timeline is below.

Started
May 23, 2022, 10:44 PM UTC
Resolved
May 23, 2022, 11:32 PM UTC
Duration
48m
Detected by Pingoru
May 23, 2022, 10:44 PM UTC

Affected components

interviewstream on demandinterviewstream connectinterviewstream schedulerinterviewstream builderinterviewstream API

Update timeline

  1. investigating May 23, 2022, 10:44 PM UTC

    We are investigating an incident with on demand, connect, and scheduler. Affected users may experience: An error message when attempting to access the rivs.com site We will provide another update as soon as we learn more. Our apologies for any disruption this incident may cause to your user experience. Best Regards, Interviewstream support https://support.interviewstream.com

  2. monitoring May 23, 2022, 11:09 PM UTC

    A fix has been implemented and we are monitoring the results. We expect that the fix applied should resolve the incident. Users who may have been experiencing an error message should no longer experience the issue. Our apologies for any disruption this incident may have caused to your user experience. Best Regards, Interviewstream support https://support.interviewstream.com

  3. resolved May 23, 2022, 11:32 PM UTC

    The incident affecting RIVS on demand, connect, scheduler, and builder has been resolved. Our apologies for any disruption this incident may have caused to your user experience. If you have any questions, please submit a request to our technical support team. Best Regards, Interviewstream support https://support.interviewstream.com

  4. postmortem Jun 02, 2022, 12:42 PM UTC

    ### **Root Cause Analysis:** This incident was due to a hardware failure on our Amazon Web Service \(AWS\) instance. The auto-restore failed due to an outdated codebase on our server. ### **Resolution Details:** The development team identified the failure and restored the code. Once restored the system behavior returned to operational. ### **Remediation Items:** Review and improve our codebase.