402Signal
https://402signal.com/mcpFail-closed live-endpoint x402 router. POST /route, $0.01 USDC on Base, Solana, Algorand.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 116ms · p95 258msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/30/2026, 4:00:00 PM | 100% | 1 | 112ms |
| 8/30/2026, 5:00:00 PM | 100% | 1 | 163ms |
| 8/30/2026, 6:00:00 PM | 100% | 1 | 158ms |
| 8/30/2026, 7:00:00 PM | 100% | 1 | 167ms |
| 8/30/2026, 8:00:00 PM | 100% | 1 | 151ms |
| 8/30/2026, 9:00:00 PM | 100% | 1 | 135ms |
| 8/30/2026, 11:00:00 PM | 100% | 1 | 2161ms |
| 8/31/2026, 12:00:00 AM | 100% | 1 | 110ms |
| 8/31/2026, 1:00:00 AM | 100% | 1 | 101ms |
| 8/31/2026, 2:00:00 AM | 100% | 1 | 106ms |
| 8/31/2026, 3:00:00 AM | 100% | 1 | 123ms |
| 8/31/2026, 4:00:00 AM | 100% | 1 | 100ms |
| 8/31/2026, 6:00:00 AM | 100% | 1 | 110ms |
| 8/31/2026, 7:00:00 AM | 100% | 1 | 96ms |
| 8/31/2026, 8:00:00 AM | 100% | 1 | 104ms |
| 8/31/2026, 9:00:00 AM | 100% | 1 | 100ms |
| 8/31/2026, 10:00:00 AM | 100% | 1 | 99ms |
| 8/31/2026, 11:00:00 AM | 100% | 1 | 103ms |
| 8/31/2026, 1:00:00 PM | 100% | 1 | 112ms |
| 8/31/2026, 2:00:00 PM | 100% | 1 | 101ms |
| 8/31/2026, 3:00:00 PM | 100% | 1 | 171ms |
| 8/31/2026, 4:00:00 PM | 100% | 1 | 119ms |
| 8/31/2026, 5:00:00 PM | 100% | 1 | 227ms |
| 8/31/2026, 6:00:00 PM | 100% | 1 | 183ms |
| 8/31/2026, 7:00:00 PM | 100% | 1 | 327ms |
| 8/31/2026, 9:00:00 PM | 100% | 1 | 251ms |
| 8/31/2026, 10:00:00 PM | 100% | 1 | 264ms |
| 8/31/2026, 11:00:00 PM | 100% | 1 | 255ms |
| 9/1/2026, 12:00:00 AM | 100% | 1 | 115ms |
| 9/1/2026, 1:00:00 AM | 100% | 1 | 260ms |
| 9/1/2026, 2:00:00 AM | 100% | 1 | 256ms |
| 9/1/2026, 4:00:00 AM | 100% | 1 | 170ms |
| 9/1/2026, 5:00:00 AM | 100% | 1 | 135ms |
| 9/1/2026, 6:00:00 AM | 100% | 1 | 240ms |
| 9/1/2026, 7:00:00 AM | 100% | 1 | 176ms |
| 9/1/2026, 8:00:00 AM | 100% | 1 | 234ms |
| 9/1/2026, 9:00:00 AM | 100% | 1 | 156ms |
| 9/1/2026, 11:00:00 AM | 100% | 1 | 133ms |
| 9/1/2026, 12:00:00 PM | 100% | 1 | 126ms |
| 9/1/2026, 1:00:00 PM | 100% | 1 | 104ms |
| 9/1/2026, 2:00:00 PM | 100% | 1 | 226ms |
| 9/1/2026, 3:00:00 PM | 100% | 1 | 73ms |
| 9/1/2026, 4:00:00 PM | 100% | 1 | 103ms |
| 9/1/2026, 5:00:00 PM | 100% | 1 | 130ms |
| 9/1/2026, 7:00:00 PM | 100% | 1 | 107ms |
| 9/1/2026, 8:00:00 PM | 100% | 1 | 123ms |
| 9/1/2026, 9:00:00 PM | 100% | 1 | 106ms |
| 9/1/2026, 10:00:00 PM | 100% | 1 | 114ms |
| 9/1/2026, 11:00:00 PM | 100% | 1 | 111ms |
| 9/2/2026, 1:00:00 AM | 100% | 1 | 101ms |
| 9/2/2026, 2:00:00 AM | 100% | 1 | 109ms |
| 9/2/2026, 3:00:00 AM | 100% | 1 | 109ms |
| 9/2/2026, 4:00:00 AM | 100% | 1 | 102ms |
| 9/2/2026, 5:00:00 AM | 100% | 1 | 161ms |
| 9/2/2026, 6:00:00 AM | 100% | 1 | 117ms |
| 9/2/2026, 7:00:00 AM | 100% | 1 | 119ms |
| 9/2/2026, 9:00:00 AM | 100% | 1 | 100ms |
| 9/2/2026, 10:00:00 AM | 100% | 1 | 98ms |
| 9/2/2026, 11:00:00 AM | 100% | 1 | 102ms |
| 9/2/2026, 12:00:00 PM | 100% | 1 | 95ms |
| 9/2/2026, 1:00:00 PM | 100% | 1 | 85ms |
| 9/2/2026, 2:00:00 PM | 100% | 1 | 107ms |
| 9/2/2026, 3:00:00 PM | 100% | 1 | 133ms |
| 9/2/2026, 5:00:00 PM | 100% | 1 | 105ms |
| 9/2/2026, 6:00:00 PM | 100% | 1 | 96ms |
| 9/2/2026, 7:00:00 PM | 100% | 1 | 128ms |
| 9/2/2026, 8:00:00 PM | 100% | 1 | 128ms |
| 9/2/2026, 9:00:00 PM | 100% | 1 | 102ms |
| 9/2/2026, 10:00:00 PM | 100% | 1 | 99ms |
| 9/2/2026, 11:00:00 PM | 100% | 1 | 124ms |
| 9/3/2026, 1:00:00 AM | 100% | 1 | 126ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 36
- Activity
- not yet measured
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- —
- Networks
- —
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- NameCheap, Inc.
- Domain registered
- 2026-08-30
- Hosting network
- FLYIO
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.