Degraded outbound DNS from runners
DEGRADEDPERFORMANCE- Started
- Jun 29, 7:14 PM EDT
- Resolved
- —
- Duration
- end time not published
What our checks recorded
We checked fal 24 times in the two hours after fal.ai's start time (it published no end time), once every five minutes. Every one of them reached fal'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 101 ms, against 105 ms over the 24 hours before. fal.ai's feed showed the incident by Jun 29, 7:25 PM EDT (we read it every five minutes).
Updates are fal.ai's own words from its status page (status: resolved); we never add an inferred cause.