Autoqueue Status

Methodology

What this status page measures

Autoqueue sends an HTTPS GET request every 60 seconds to two minimal health endpoints. A check passes only when the response is HTTP 200 and the complete JSON body is exactly {"ok":true}. Redirects, timeouts, malformed bodies, non-200 responses, and explicit unhealthy responses fail.

State transitions

One failed check is degraded. Two consecutive failed checks are an outage. Recovery requires two consecutive passed checks; the first moves an automatic incident to monitoring. A component becomes unknown when its latest scheduled evidence is more than three minutes old or cannot be read safely.

Scheduled-check success

The displayed percentage is passed scheduled intervals divided by expected scheduled intervals. Failed, unknown, and missing intervals remain in the denominator. A partially observed activation day is marked partial and excluded from the headline; it remains visible in history.

Limits

These checks do not prove continuous availability, source coverage, retailer availability, end-to-end alert delivery, inbox placement, browser execution, queue entry, stock, or purchase.