Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 232ms · p95 976msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/28/2026, 10:00:00 PM | 100% | 1 | 845ms |
| 9/29/2026, 12:00:00 AM | 100% | 1 | 846ms |
| 9/29/2026, 2:00:00 AM | 100% | 1 | 260ms |
| 9/29/2026, 3:00:00 AM | 100% | 1 | 1004ms |
| 9/29/2026, 5:00:00 AM | 100% | 1 | 1198ms |
| 9/29/2026, 7:00:00 AM | 100% | 1 | 983ms |
| 9/29/2026, 9:00:00 AM | 100% | 1 | 853ms |
| 9/29/2026, 11:00:00 AM | 100% | 1 | 963ms |
| 9/29/2026, 1:00:00 PM | 100% | 1 | 230ms |
| 9/29/2026, 3:00:00 PM | 100% | 1 | 199ms |
| 9/29/2026, 6:00:00 PM | 100% | 1 | 346ms |
| 9/29/2026, 8:00:00 PM | 100% | 1 | 174ms |
| 9/29/2026, 9:00:00 PM | 100% | 1 | 293ms |
| 9/30/2026, 12:00:00 AM | 100% | 1 | 227ms |
| 9/30/2026, 2:00:00 AM | 100% | 1 | 233ms |
| 9/30/2026, 4:00:00 AM | 100% | 1 | 151ms |
| 9/30/2026, 6:00:00 AM | 100% | 1 | 165ms |
| 9/30/2026, 8:00:00 AM | 100% | 1 | 193ms |
| 9/30/2026, 10:00:00 AM | 100% | 1 | 147ms |
| 9/30/2026, 12:00:00 PM | 100% | 1 | 190ms |
| 9/30/2026, 2:00:00 PM | 100% | 1 | 183ms |
| 9/30/2026, 4:00:00 PM | 100% | 1 | 251ms |
| 9/30/2026, 6:00:00 PM | 100% | 1 | 196ms |
| 9/30/2026, 8:00:00 PM | 100% | 1 | 212ms |
| 9/30/2026, 10:00:00 PM | 100% | 1 | 213ms |
| 10/1/2026, 12:00:00 AM | 100% | 1 | 207ms |
| 10/1/2026, 2:00:00 AM | 100% | 1 | 182ms |
| 10/1/2026, 4:00:00 AM | 100% | 1 | 167ms |
| 10/1/2026, 6:00:00 AM | 100% | 1 | 251ms |
| 10/1/2026, 8:00:00 AM | 100% | 1 | 173ms |
| 10/1/2026, 10:00:00 AM | 100% | 1 | 217ms |
| 10/1/2026, 12:00:00 PM | 100% | 1 | 900ms |
| 10/1/2026, 2:00:00 PM | 100% | 1 | 249ms |
| 10/1/2026, 4:00:00 PM | 100% | 1 | 947ms |
| 10/1/2026, 6:00:00 PM | 100% | 1 | 938ms |
| 10/1/2026, 8:00:00 PM | 100% | 1 | 932ms |
| 10/1/2026, 10:00:00 PM | 100% | 1 | 827ms |
| 10/2/2026, 12:00:00 AM | 100% | 1 | 970ms |
| 10/2/2026, 2:00:00 AM | 100% | 1 | 823ms |
| 10/2/2026, 4:00:00 AM | 100% | 1 | 211ms |
| 10/2/2026, 6:00:00 AM | 100% | 1 | 147ms |
| 10/2/2026, 8:00:00 AM | 100% | 1 | 194ms |
| 10/2/2026, 10:00:00 AM | 100% | 1 | 210ms |
| 10/2/2026, 12:00:00 PM | 100% | 1 | 164ms |
| 10/2/2026, 2:00:00 PM | 100% | 1 | 916ms |
| 10/2/2026, 4:00:00 PM | 100% | 1 | 999ms |
| 10/2/2026, 6:00:00 PM | 100% | 1 | 211ms |
| 10/2/2026, 8:00:00 PM | 100% | 1 | 218ms |
| 10/2/2026, 11:00:00 PM | 100% | 1 | 181ms |
| 10/3/2026, 12:00:00 AM | 100% | 1 | 136ms |
| 10/3/2026, 2:00:00 AM | 100% | 1 | 168ms |
| 10/3/2026, 4:00:00 AM | 100% | 1 | 941ms |
| 10/3/2026, 6:00:00 AM | 100% | 1 | 194ms |
| 10/3/2026, 8:00:00 AM | 100% | 1 | 210ms |
| 10/3/2026, 10:00:00 AM | 100% | 1 | 895ms |
| 10/3/2026, 12:00:00 PM | 100% | 1 | 976ms |
| 10/3/2026, 2:00:00 PM | 100% | 1 | 147ms |
| 10/3/2026, 4:00:00 PM | 100% | 1 | 887ms |
| 10/3/2026, 6:00:00 PM | 100% | 1 | 873ms |
| 10/3/2026, 8:00:00 PM | 100% | 1 | 136ms |
| 10/3/2026, 11:00:00 PM | 100% | 1 | 776ms |
| 10/4/2026, 1:00:00 AM | 100% | 1 | 211ms |
| 10/4/2026, 3:00:00 AM | 100% | 1 | 227ms |
| 10/4/2026, 5:00:00 AM | 100% | 1 | 908ms |
| 10/4/2026, 7:00:00 AM | 100% | 1 | 310ms |
| 10/4/2026, 9:00:00 AM | 100% | 1 | 286ms |
| 10/4/2026, 1:00:00 PM | 100% | 1 | 282ms |
| 10/4/2026, 3:00:00 PM | 100% | 1 | 172ms |
| 10/4/2026, 5:00:00 PM | 100% | 1 | 270ms |
| 10/4/2026, 7:00:00 PM | 100% | 1 | 256ms |
| 10/4/2026, 9:00:00 PM | 100% | 1 | 166ms |
| 10/5/2026, 2:00:00 AM | 100% | 1 | 170ms |
| 10/5/2026, 7:00:00 AM | 100% | 1 | 970ms |
| 10/5/2026, 9:00:00 AM | 100% | 1 | 203ms |
| 10/5/2026, 11:00:00 AM | 100% | 1 | 476ms |
| 10/5/2026, 1:00:00 PM | 100% | 1 | 424ms |
| 10/5/2026, 2:00:00 PM | 100% | 1 | 218ms |
| 10/5/2026, 4:00:00 PM | 100% | 1 | 302ms |
| 10/5/2026, 6:00:00 PM | 100% | 1 | 470ms |
| 10/5/2026, 8:00:00 PM | 100% | 1 | 229ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 49
- Activity
- 7
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
- USDC
- Networks
- base
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- GoDaddy.com, LLC
- Domain registered
- 2025-07-04
- Hosting network
- VERCEL-12
- 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.
On-chain activity (base)
Payments per day
last payment 9/28/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 9/14/2026 | 1 | 0.01 | 1 |
| 9/28/2026 | 1 | 0.01 | 1 |
Only payments settled on chains and facilitators we index.
Response schema
{
"input": {
"discoverable": true,
"method": "GET",
"type": "http"
},
"output": {
"network": {
"type": "string"
},
"product": {
"type": "string"
},
"report": {
"properties": {
"proofRecord": {
"type": "string"
},
"proofRegistry": {
"type": "string"
},
"repository": {
"type": "string"
},
"summary": {
"type": "string"
}
},
"type": "object"
}
}
}