Status
What the gateway is doing right now
Read live from the deployment itself, on every load. These are the same readings that page an operator — the number that turns a row amber here is the number that wakes somebody up.
Checking…
Reading the deployment now.
What we measure, and what we aim for
Each target is the threshold the gateway's own checks apply. A target no check enforces is marketing; a threshold no page states is a secret.
- How far behind the chain head a payment can be detected
- within 200 blocks
- Past this, your customer has paid and the payment still reads as unpaid. It is the only failure on this page that a customer sees before you do.
- How long between completed scans of each chain
- under 5 minutes
- A chain nobody is scanning looks exactly like a chain with no payments on it — nothing errors, nothing 500s, and money quietly stops being seen.
- Deliveries that exhaust every retry, per hour
- at most 20
- A delivery is retried 18 times over just under two days before it is declared dead. Deaths above this rate mean endpoints are being given up on, not merely retried.
- How stale an operator key’s reported gas balance may be
- under 20 minutes
- The keys that sign payouts, refunds and subscription charges pay their own gas. A key that stops reporting is read as unreadable rather than as healthy.
What each state means
Four, not three. The fourth is the one a status page is tempted to leave out.
- Operational
- The check ran and found nothing wrong.
- Degraded
- Working, but outside the objective above. Money is late rather than lost.
- Down
- Not doing its job at all.
- Unknown
- The check could not be performed. It is shown rather than hidden, and it never counts as healthy — a green tick drawn from a query that failed is a false one.
What this page is not
It is a measurement, not an undertaking. The difference is the part worth reading twice.
Reading this from your own systems
The page is a rendering of one public endpoint. Point anything you like at it.
GET https://app.paygatehq.com/v1/status needs no API key and is readable from any origin. It always answers 200, even when everything is down — the state is in the body, because a 503 would make every cache between here and you treat the status document itself as unavailable. It is described in the API reference.