TornadoAPIStatus
SERVICE STATUS

Keeping you in the loop.

Current service health and a transparent record of availability.

Waiting for the first update

Services

HTTP checks every minute All dates in UTC

Loading observations…
OperationalSome checks failedChecks failedNo data / incomplete day

Percentages show successful HTTP checks over the observed period. Missing observations are never counted as success. These checks do not measure media job completion or constitute an SLA.

Incident history

Automatically detected interruptions and recoveries.

Last 90 days
Loading incident history…
What does this page monitor?

Checks run from Cloudflare once a minute. The public API must return “pong”; the dashboard backend must report healthy data connections. Website checks verify an HTTP 200 HTML response. A slow response beyond eight seconds counts as a failed check.

Two consecutive failed checks open an incident; two successful checks close it. The first failure is already reflected in the service status and daily percentage. Results older than three minutes are marked unknown. Daily bars show UTC calendar days; striped bars indicate incomplete coverage.

The monitoring history starts when this service is enabled. Earlier days are left empty. Sign-in checks do not verify authentication, and API checks do not test downloads, uploads, billing or webhooks. A single Cloudflare probe location cannot establish global availability.

This page and its history are hosted independently of TornadoAPI’s servers on Cloudflare. A Cloudflare-wide incident may also affect this page.

DAILY OBSERVATIONS

All times in UTC. Unobserved minutes are not counted as successful checks.