The audit engine, degraded right now.
This page is the engine's own record of the audits it ran, not an independent uptime monitor. It counts every run started in the last 30 days and how it ended. If a run of yours failed, it was not charged, and we would like to know about it.
59%
of audits finished
382 of 649 that ended
4 min 18 s
median time to a report
from the moment you paste the address
56%
reached the checkout
214 of 382 finished audits
0
running right now
with a heartbeat in the last five minutes
30 days agoGreen: at least 9 of 10 audits finished. Amber: 7 to 9. Red: fewer. Grey: no audits that day.Today
What an audit goes through
Four steps, and a run that stalls on any of them is failed and said so rather than left spinning. We do not record how long each step takes on its own, so no per-step timing is claimed here.
01QueueYour address is accepted and a run is opened. A run that stops sending a heartbeat is failed rather than left hanging.
02WalkA real browser opens the store, finds a product page, adds to the cart and goes as far into the checkout as it can. Screenshots at every step.
03JudgeThe rulebook is applied to what the walk saw. A check that cannot be made confidently returns not assessable and lowers coverage.
04ReportFindings, evidence and the score are written and the report becomes readable. A run that died after saving a partial report is salvaged rather than thrown away.
Rough days
2026-08-2529 of 48 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-08-269 of 22 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-08-2711 of 18 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-08-285 of 5 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-08-295 of 5 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-08-3119 of 45 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-0129 of 36 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-0212 of 21 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-0310 of 18 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-0613 of 32 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-0833 of 71 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-0916 of 34 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-109 of 17 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-129 of 13 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-168 of 15 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-191 of 1 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-215 of 5 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
2026-09-221 of 1 audits failed. A failed audit is never charged, and the reason is on the report it would have been.
Counts refresh at most once an hour. For what the audit actually checks, see how it works; for what a score is allowed to claim, see trust and data.