A live readout, rendered at the moment you loaded this page. The same figures
as JSON are at /healthz, which is what an uptime monitor
should poll.
All systems nominal
Requests since the last deploy, counted by crawler family from the user agent alone. No paths, no addresses, nothing stored.
Every request to a paid route, by the stage it reached. "Issued" is a 402 answered to a request without payment; "refused" is a request rejected before payment; "attempts" carried a payment header; "settled" is money that landed.
| route | 402 issued | refused | paid attempts | settled |
|---|---|---|---|---|
| POST /v1/email | 10 | 0 | 0 | 0 |
| POST /v1/webhook | 6 | 0 | 0 | 0 |
| route | refused with | count |
|---|---|---|
| none in the last 7 days | ||
Loop lag is the seconds since the delivery loop last completed a pass. Under about 60 seconds
is healthy; beyond that /healthz returns 503. Queued deliveries briefly above zero is
normal: those are messages in flight or on the retry ladder.