Delayed scaling due to node failure
minor- Started
- Aug 10, 5:05 PM EDT
- Resolved
- —
- Duration
- end time not published
What our checks recorded
We checked Replicate 24 times in the two hours after Replicate's start time (it published no end time), once every five minutes. Every one of them reached Replicate's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 110 ms, against 167 ms over the 24 hours before. Replicate's feed showed the incident by Aug 10, 5:05 PM EDT (we read it every five minutes).
Updates are Replicate's own words from its status page (status: resolved); we never add an inferred cause.