All services operational
Last reviewed 31 Jul 202699.9%
target uptime
cached checks, rolling 90 days
~20s
a new check
typical, end to end
instant
a cached check
served from our own store
0
open incidents
Services
What a check touches
Each of these can be available or not independently. A check never fails as a whole — it comes back with whatever it could measure and a named gap for whatever it couldn't.
Cached checks
operational
Any post already scored, served from our own store. Unaffected by anything upstream.
New checks
operational
Scoring a post we haven't seen before, end to end.
Market data
operational
Price, volume and liquidity for the token, plus the peer benchmark.
Social data
operational
Post metrics and reply content for the audience score.
Track records
operational
Per-account history and the aggregate view across it.
Corpus comparison
operational
Percentiles, the profile quadrant, and everything else that needs the full distribution.
Reports & export
operational
Stored reports, campaign views, CSV and PDF.
Checkout
operational
Payment confirmation and plan activation.
This page is reviewed rather than polled. Automated monitoring ships alongside the API — until then we would rather date the page than show you a green dot we haven't earned.
Degradation
What you get when something is missing
The rule throughout is the same: a withheld number is honest, an estimated one is a fabrication with a decimal point.
Market data unavailable
You get the audience score and the intent classification. Performance and impact are withheld rather than approximated, and the check is marked incomplete so it can be re-run rather than quietly filed as final.
Social data unavailable
You get the chart side in full. The audience score is withheld — we will not infer whether replies were real from anything other than the replies.
Thin market for the token
Some pairs never produce a reliable first-hour figure. Those checks return without a profile quadrant instead of guessing at one, and say so on the report.
Ambiguous ticker
The check stops and asks for the contract address. Resolving to the most likely match is fine for exploration and unacceptable on a report with somebody's name on it.
Under load
Cached checks are unaffected — they don't depend on anything outside our own store, which is why they stay unlimited on every plan. New checks queue, and the queue position is visible while you wait.
Anything else
Scores already in your account stay readable and exportable regardless. Nothing you have paid for becomes unavailable because something upstream is having a bad day.
Questions