System status
Stampwright's own endpoints
| Independent checks | Public endpoints responding, no open findings |
|---|---|
| Last completed sweep | 2m ago |
| Open findings | 0 |
A monitor outside Cloudflare requests the landing page, the sample report, the artwork preflight, the status data behind this page, the privacy notice, the terms, and a resolver path every five minutes, and records a completed run in the database each time. A sweep that finds a failing endpoint twice in a row opens a finding. Those sweeps are not retained as history, so this page reports when the last one completed and what it found, and does not convert them into an uptime percentage.
Customer destinations
| Destinations behind resolver links | No destinations configured yet |
|---|---|
| Checks run (24h) | 0 |
| Failed checks (24h) | 0 |
| Open resolver and destination incidents | 0 |
| Last destination sweep | None yet |
How to read this page. The two sections measure different things. Destination uptime is the share of checks in which a page behind a resolver link returned a successful response, so it describes the brand's own URLs rather than Stampwright. Every figure comes from Stampwright's monitoring tables. Neither section is an independent measure of Cloudflare edge availability. Open findings are outage findings on public endpoints that a person has not yet closed, including an outage that has recovered but is still under review. Resolver and destination incidents cover customer destinations that keep failing and resolver links whose stored record cannot be served. Internal alerts, such as a failed scheduled job or a backup check, go to the operator and are not counted here.
Machine-readable: /status.json | Security contact: security.txt