close
CrawlCheck
Status

Part of CrawlCheck needs attention.

Each line is read from the running system when this page loads: the build serving now, scans, signing, the daily seal, the backup and its restore test, the hourly security self-test and the outside observers. Incidents are written to a signed, append-only log.

0%50%100%resolve availabilityresolve availability: 100%99.9%resolve latencyresolve latency: 74%74.2%preflight availabilitypreflight availability: 100%100%preflight latencypreflight latency: 61%60.9%jit latencyjit latency: 96%95.7%
Denominator: resolve availability 16,200 · resolve latency 16,200 · preflight availability 4,644 · preflight latency 4,644 · jit latency 786 samples · Scale: share of samples meeting the objective, 0–100% · Window: the last 30 days, rolling

Definition

Availability
The share of lookups answered without a server error.
Latency
The share answered within the stated time on the server, read from its own Server-Timing header; the network between the server and the caller is not included.
First answer
A lookup for a domain CrawlCheck has never measured: a live read within 2 seconds.
Met / missed
Settled at 95% confidence (Wilson interval); an objective whose interval still contains the target is reported as not settled.

What this does not prove

  • A 30-day window lags a fix: after a latency fix the line moves only as the slow days roll out of the window.
  • Probe calls from CrawlCheck's own monitors count as samples, alongside outside calls.
  • Server time is not what a caller waits: add their network round trip.
  • Green components say the systems answered when read, not that every answer was correct.

Check it yourself

The numbers on this page come from the signed JSON at /api/v1/instruments/status/now.json, rebuilt every few minutes; each copy carries its own sha256 and an Ed25519 signature by key 1hHmE3fo1rg5…. For a copy that never changes, cite a weekly edition. Verify either with no call to us:

node crawlcheck-verify.mjs --online status.json

The verifier: /crawlcheck-verify.mjs, zero dependencies.

Editions

One sealed edition per ISO week: the signed reading as first taken that week, never edited. Feed: Atom · all instruments: /api/v1/instruments.

Now

Service

Read at 2026-11-19 21:00 UTC

Website and APIServing now; this build went live 2026-11-19 18:38 UTC
Operational
Scans276 scans in the last 24 hours, 18 in the last hour; free scans open (8 of today's 1500)
Operational
Signed answers and receiptsSigning with key 1hHmE3fo1rg5…
Operational
Daily Bitcoin sealLatest sealed day 2026-11-18
Operational
Backup and restore testLast backup 2026-11-18 (4796776 keys); restore test passed
Operational
Security self-test101 of 101 checks passed, 43 minutes ago
Operational
Agent lookups (Resolve and preflight)Resolve answers: 99.9% over 30 days (target 99.9%); last 24 hours within target (burn 0, 1020 samples); Resolve answers for a measured domain within 300 ms on the server: 74.2% over 30 days (target 95%), counting 3178 samples with no latency reading as misses (92.4% of the measured ones); last 24 hours over target (burn 20, 1020 samples); Preflight decisions: 100% over 30 days (target 99.9%); last 24 hours within target (burn 0, 306 samples); Preflight decisions within 300 ms on the server: 60.9% over 30 days (target 95%), counting 1004 samples with no latency reading as misses (77.7% of the measured ones); last 24 hours over target (burn 20, 306 samples)
Degraded
Break-glass owner accesslast test passed 2026-10-08
Operational
Release provenanceserving build carries a release receipt
Operational
Outside observers5 of 5 active observers reported in the last 24 hours (2 quarantined or revoked, not counted)
Operational
Targets

What we hold ourselves to

Last 30 days · /api/slo

ObjectiveTargetMeasuredBudget leftp95
Resolve answers without a server error99.9%99.9% of 1620025.9%713 ms
Resolve answers for a measured domain within 300 ms on the server95%74.2% of 162000%713 ms
Preflight decisions without a server error99.9%100% of 464478.5%659 ms
Preflight decisions within 300 ms on the server95%60.9% of 46440%659 ms
A first answer for a never-measured domain within 2 seconds on the server95%95.7% of 78613.5%1949 ms
Incidents

Open incidents

What each severity means

None open.

History

Resolved in the last 90 days

None.

The incident log has 0 signed entries; chain intact. Verify it yourself: /api/status/log (each entry is signed with the key at /keys and names the digest of the entry before it). Machine-readable: /api/status.