Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 225ms · p95 306msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/29/2026, 12:00:00 AM | 100% | 1 | 233ms |
| 9/29/2026, 1:00:00 AM | 100% | 1 | 273ms |
| 9/29/2026, 3:00:00 AM | 100% | 1 | 248ms |
| 9/29/2026, 5:00:00 AM | 100% | 1 | 236ms |
| 9/29/2026, 7:00:00 AM | 100% | 1 | 226ms |
| 9/29/2026, 9:00:00 AM | 100% | 1 | 202ms |
| 9/29/2026, 11:00:00 AM | 100% | 1 | 243ms |
| 9/29/2026, 1:00:00 PM | 100% | 1 | 250ms |
| 9/29/2026, 3:00:00 PM | 100% | 1 | 226ms |
| 9/29/2026, 6:00:00 PM | 100% | 1 | 250ms |
| 9/29/2026, 7:00:00 PM | 100% | 1 | 289ms |
| 9/29/2026, 9:00:00 PM | 100% | 1 | 209ms |
| 9/30/2026, 12:00:00 AM | 100% | 1 | 251ms |
| 9/30/2026, 2:00:00 AM | 100% | 1 | 241ms |
| 9/30/2026, 4:00:00 AM | 100% | 1 | 239ms |
| 9/30/2026, 6:00:00 AM | 100% | 1 | 217ms |
| 9/30/2026, 8:00:00 AM | 100% | 1 | 190ms |
| 9/30/2026, 10:00:00 AM | 100% | 1 | 203ms |
| 9/30/2026, 12:00:00 PM | 100% | 1 | 262ms |
| 9/30/2026, 2:00:00 PM | 100% | 1 | 218ms |
| 9/30/2026, 4:00:00 PM | 100% | 1 | 245ms |
| 9/30/2026, 6:00:00 PM | 100% | 1 | 212ms |
| 9/30/2026, 8:00:00 PM | 100% | 1 | 213ms |
| 9/30/2026, 10:00:00 PM | 100% | 1 | 209ms |
| 10/1/2026, 12:00:00 AM | 100% | 1 | 217ms |
| 10/1/2026, 2:00:00 AM | 100% | 1 | 232ms |
| 10/1/2026, 4:00:00 AM | 100% | 1 | 190ms |
| 10/1/2026, 6:00:00 AM | 100% | 1 | 236ms |
| 10/1/2026, 8:00:00 AM | 100% | 1 | 309ms |
| 10/1/2026, 10:00:00 AM | 100% | 1 | 306ms |
| 10/1/2026, 12:00:00 PM | 100% | 1 | 224ms |
| 10/1/2026, 2:00:00 PM | 100% | 1 | 204ms |
| 10/1/2026, 4:00:00 PM | 100% | 1 | 203ms |
| 10/1/2026, 6:00:00 PM | 100% | 1 | 206ms |
| 10/1/2026, 8:00:00 PM | 100% | 1 | 226ms |
| 10/1/2026, 10:00:00 PM | 100% | 1 | 202ms |
| 10/2/2026, 12:00:00 AM | 100% | 1 | 225ms |
| 10/2/2026, 2:00:00 AM | 100% | 1 | 226ms |
| 10/2/2026, 4:00:00 AM | 100% | 1 | 1193ms |
| 10/2/2026, 6:00:00 AM | 100% | 1 | 218ms |
| 10/2/2026, 8:00:00 AM | 100% | 1 | 222ms |
| 10/2/2026, 10:00:00 AM | 100% | 1 | 242ms |
| 10/2/2026, 12:00:00 PM | 100% | 1 | 270ms |
| 10/2/2026, 2:00:00 PM | 100% | 1 | 482ms |
| 10/2/2026, 4:00:00 PM | 100% | 1 | 232ms |
| 10/2/2026, 6:00:00 PM | 100% | 1 | 210ms |
| 10/2/2026, 8:00:00 PM | 100% | 1 | 216ms |
| 10/2/2026, 11:00:00 PM | 100% | 1 | 226ms |
| 10/3/2026, 12:00:00 AM | 100% | 1 | 224ms |
| 10/3/2026, 2:00:00 AM | 100% | 1 | 192ms |
| 10/3/2026, 4:00:00 AM | 100% | 1 | 225ms |
| 10/3/2026, 6:00:00 AM | 100% | 1 | 210ms |
| 10/3/2026, 8:00:00 AM | 100% | 1 | 183ms |
| 10/3/2026, 10:00:00 AM | 100% | 1 | 284ms |
| 10/3/2026, 12:00:00 PM | 100% | 1 | 249ms |
| 10/3/2026, 2:00:00 PM | 100% | 1 | 251ms |
| 10/3/2026, 4:00:00 PM | 100% | 1 | 223ms |
| 10/3/2026, 6:00:00 PM | 100% | 1 | 224ms |
| 10/3/2026, 8:00:00 PM | 100% | 1 | 245ms |
| 10/3/2026, 11:00:00 PM | 100% | 1 | 247ms |
| 10/4/2026, 1:00:00 AM | 100% | 1 | 218ms |
| 10/4/2026, 3:00:00 AM | 100% | 1 | 204ms |
| 10/4/2026, 5:00:00 AM | 100% | 1 | 274ms |
| 10/4/2026, 7:00:00 AM | 100% | 1 | 233ms |
| 10/4/2026, 8:00:00 AM | 100% | 1 | 223ms |
| 10/4/2026, 1:00:00 PM | 100% | 1 | 306ms |
| 10/4/2026, 3:00:00 PM | 100% | 1 | 194ms |
| 10/4/2026, 5:00:00 PM | 100% | 1 | 217ms |
| 10/4/2026, 7:00:00 PM | 100% | 1 | 262ms |
| 10/4/2026, 9:00:00 PM | 100% | 1 | 272ms |
| 10/5/2026, 2:00:00 AM | 100% | 1 | 195ms |
| 10/5/2026, 7:00:00 AM | 100% | 1 | 225ms |
| 10/5/2026, 9:00:00 AM | 100% | 1 | 217ms |
| 10/5/2026, 11:00:00 AM | 100% | 1 | 220ms |
| 10/5/2026, 1:00:00 PM | 100% | 1 | 233ms |
| 10/5/2026, 2:00:00 PM | 100% | 1 | 214ms |
| 10/5/2026, 4:00:00 PM | 100% | 1 | 202ms |
| 10/5/2026, 6:00:00 PM | 100% | 1 | 214ms |
| 10/5/2026, 8:00:00 PM | 100% | 1 | 246ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 49
- Activity
- 9
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
- —
- Domain registered
- —
- Hosting network
- RUMBLE-CLOUD-NET1
- 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 10/4/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 9/25/2026 | 1 | 0.01 | 1 |
| 9/28/2026 | 1 | 0.01 | 1 |
| 10/4/2026 | 1 | 0.01 | 1 |
Only payments settled on chains and facilitators we index.
Response schema
{
"input": {
"discoverable": true,
"method": "GET",
"queryParams": {
"limit": "10",
"make": "BMW",
"model": "M3",
"year": "2029"
},
"type": "http"
},
"output": {
"count": 1,
"limit": 10,
"offset": 0,
"results": [
{
"horsepower": 503,
"id": "tpqep1eykfzk352",
"make": "BMW",
"model": "M3",
"year": 2029
}
]
}
}