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.
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.
Service
Read at 2026-11-19 21:00 UTC
What we hold ourselves to
Last 30 days · /api/slo
| Objective | Target | Measured | Budget left | p95 |
|---|---|---|---|---|
| Resolve answers without a server error | 99.9% | 99.9% of 16200 | 25.9% | 713 ms |
| Resolve answers for a measured domain within 300 ms on the server | 95% | 74.2% of 16200 | 0% | 713 ms |
| Preflight decisions without a server error | 99.9% | 100% of 4644 | 78.5% | 659 ms |
| Preflight decisions within 300 ms on the server | 95% | 60.9% of 4644 | 0% | 659 ms |
| A first answer for a never-measured domain within 2 seconds on the server | 95% | 95.7% of 786 | 13.5% | 1949 ms |
Open incidents
None open.
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.
