Status
Uptime history from an external prober's own record - not Vetrail reporting on itself. A service that only measures its own uptime can't see its own outages.
Last 90 days
Each square is one day. A day is marked down if any availability check that day failed, or an outage was reported for it below - an average across the day would hide a real outage inside a mostly-good one.
Reported outages
None reported in the last 90 days.
How this is measured
A check suite runs against the live site every six hours, and again immediately after every deploy - the same suite that gates whether a deploy is considered to have actually worked, not a separate marketing measurement. Each run reports here whether its availability checks passed: the site answering, its public pages loading, and HTTPS working. The suite's other checks - DNS records, the deployed version, page wording - alert our team, but a failure in one of them doesn't mean anyone was turned away, so it doesn't mark a day down.
Six-hour granularity means a short outage between checks may not be caught by the prober. When we know of one, we report it above and mark its day down; a report can only mark a day down, never up, and the uptime percentage counts the checks alone. This page covers availability.
Until 30 Sep 2026, a failure in any check marked a day down. The one day that changed, 29 Sep 2026, failed a check on how a refused request is answered while every availability check passed, so it now shows as up.