Ryver incident

Reports of 500 errors at 9:40am PST

Notice Resolved View vendor source →

Ryver experienced a notice incident on January 27, 2017, lasting 12m. The incident has been resolved; the full update timeline is below.

Started
Jan 27, 2017, 05:48 PM UTC
Resolved
Jan 27, 2017, 06:00 PM UTC
Duration
12m
Detected by Pingoru
Jan 27, 2017, 05:48 PM UTC

Update timeline

  1. monitoring Jan 27, 2017, 05:48 PM UTC

    We got an alert from Amazon AWS of a brief "unhealthy host" in our Elastic Load Balancer. It was switched out immediately, but caused a spike in data access errors. We are monitoring for any further issues.

  2. resolved Jan 27, 2017, 06:00 PM UTC

    We identified one particular web server in a bad state and have corrected that machine.