Status

1. Loading…

An incident is one target failing in consecutive 5-minute runs. It ends at the next run where the target passed.

Every row is a payment that verified and was forwarded to the merchant's API. Not charged: the API failed, so nothing settled (pay on success). Settle rate counts settled tolls among those whose API answered 2xx.

• Tried in order: Elsa first, then Ultravioleta DAO.
• Down → next. No answer, a timeout, 5xx, 429, 401, 404 or an unreadable answer moves the payment to the next facilitator. Two failures in a row bench a facilitator for 3 minutes; it is tried last while benched.
• Refusal is final. A facilitator that answers and rejects the payment is not overruled by asking another one.
• Verify and settle never split. The facilitator that verified a payment is the one that settles it.

• TOLLA publishes these measurements as they are. Nothing is smoothed or removed.
• No contractual SLA is offered during beta. There are no credits or guaranteed uptime yet.
• Measurement started on the day this page was deployed (…), so early numbers are thin. Uptime shows "not enough data" until a target has an hour of checks. Rows older than 8 days are deleted.
• Checks run from Cloudflare's network once every 5 minutes. A short outage between two runs is not seen.
• The same data is public at GET /api/status (JSON, cached 60 s).