Ruvna incident

Issues with Scheduled Screening Instances

Minor Resolved View vendor source →

Ruvna experienced a minor incident on November 25, 2020, lasting 18h 45m. The incident has been resolved; the full update timeline is below.

Started
Nov 25, 2020, 11:46 PM UTC
Resolved
Nov 26, 2020, 06:31 PM UTC
Duration
18h 45m
Detected by Pingoru
Nov 25, 2020, 11:46 PM UTC

Update timeline

  1. identified Nov 25, 2020, 11:46 PM UTC

    We're currently experiencing delays and increased failure rates when creating automatically scheduled screening instances. Some instances are being created up to 4 minutes later than their scheduled time, and others are failing to be created. Our team is investigating the issue which is a result of an ongoing AWS service disruption. We will provide updates here as they become available. This incident does not affect manually-created screening instances. If your instance is not created within 5 minutes after its scheduled creation time, we recommend creating the instance manually (by selecting "Create Off-Schedule Instance").

  2. identified Nov 26, 2020, 03:30 AM UTC

    We are continuing to investigate this issue.

  3. resolved Nov 26, 2020, 06:31 PM UTC

    This incident has been resolved.