Plain definitions for every number on the status page, what we cannot measure, and how to check us.
Every timed figure on the status page is the difference between two of three timestamps attached to an alert.
Catch time = caught − happened. Delivery time = delivered − happened. When an alert is sent by more than one product, the delivery time shown in the ticker and in the catch tables is the earliest delivery; the delivery tables count every delivery separately.
Every 60 seconds the service checks each product's components: whether the product is running, whether it has recently reported itself alive, and a health check where one exists. A failing core component marks the product down for that minute; a failing secondary component marks it degraded, which still counts as available. Uptime is available minutes divided by checked minutes over the window shown, and each percentage carries the number of checks behind it. Days are rolled up at midnight UTC and kept indefinitely.
An incident opens automatically after a few consecutive down minutes and resolves automatically after a few consecutive available minutes; the duration is the time between those two points. Incidents can also be opened, updated and resolved by the operator. Updates are time-stamped and never edited; the incident list shows the last 30 days.
Incidents are published with a delay to protect customers. A public, real-time "degraded" or "down" would tell other players exactly when our customers are without alerts, and a real-time list of caught alerts would let a player test whether they are being watched. Therefore:
Daily archive. Shortly after midnight UTC the completed day is written to /status/archive/ as one JSON file: counts, medians and 95th percentiles per alert type and product, delivery figures, uptime per product and the day's incidents. Archive files are never edited or rewritten. Each file contains the SHA-256 hash of the previous day's file and its own hash, forming a chain published at chain.json.
sha256 field, serialise the rest as canonical JSON (keys sorted, no whitespace, UTF-8) and hash it with SHA-256; it must equal the file's sha256 and the entry in chain.json, and sha256_prev must equal the previous day's sha256.1.8 seconds passed between the moment the game's own server recorded the event ("happened") and the moment the Sinister Bots service recognised it ("caught"). Delivery time is measured the same way, ending at the Discord message timestamp.
The game records many event times in whole seconds. A difference below one second, including zero or a slightly negative value caused by that rounding, is shown as "under 1 s" and counted as 0.5 seconds in medians and percentiles. We never show a fractional time we cannot support.
Alerts without a usable reference time from the game, and types that only record that something took place (attack cancelled, node alerts, realm transfers), are counted but never timed.
Every 60 seconds the service checks each product's components. A failing core component marks the product down for that minute; a failing secondary component marks it degraded, which still counts as available. Uptime is available minutes divided by checked minutes, and every figure shows how many checks it is based on.
To protect customers. A public, real-time "degraded" or "down" would tell other players exactly when our customers are without alerts, and a real-time list of caught alerts would let a player test whether they are being watched. Incidents, any state other than operational, alert counts and timings are therefore published with a delay of about 60 minutes, or once the incident has ended. Customers are informed in real time in their private channels. Nothing is hidden from the record: uptime figures include every outage.
Live figures are recomputed from the raw records and change only as new records arrive. The daily archive is written once per day and never rewritten; each file includes the SHA-256 hash of the previous day's file, so any later change to any day would break the chain published at /status/archive/chain.json.
Fetch https://sinisterbots.com/status.json at any time and compare it with the page; download a day from /status/archive/, recompute its sha256 field over the canonical JSON and compare it with chain.json; and keep your own copies — if a later copy of the same day differs from yours, the chain is broken.
The Sinister Bots status service measures its own products; there is no third-party audit. The data is published under CC BY 4.0: you may republish it with attribution to Sinister Bots and a link to the status page.
Data measured by the Sinister Bots status service itself and published under CC BY 4.0 — republish with attribution and a link to sinisterbots.com/status. Times are UTC.