Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 522ms · p95 887msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/6/2026, 12:00:00 AM | 100% | 17 | 520ms |
| 9/7/2026, 12:00:00 AM | 100% | 15 | 515ms |
| 9/8/2026, 12:00:00 AM | 100% | 20 | 526ms |
| 9/9/2026, 12:00:00 AM | 100% | 21 | 510ms |
| 9/10/2026, 12:00:00 AM | 100% | 14 | 526ms |
| 9/11/2026, 12:00:00 AM | 100% | 10 | 566ms |
| 9/12/2026, 12:00:00 AM | 100% | 9 | 536ms |
| 9/13/2026, 12:00:00 AM | 100% | 16 | 520ms |
| 9/14/2026, 12:00:00 AM | 100% | 15 | 553ms |
| 9/15/2026, 12:00:00 AM | 100% | 16 | 500ms |
| 9/16/2026, 12:00:00 AM | 100% | 16 | 506ms |
| 9/17/2026, 12:00:00 AM | 100% | 15 | 496ms |
| 9/18/2026, 12:00:00 AM | 100% | 13 | 512ms |
| 9/19/2026, 12:00:00 AM | 100% | 13 | 503ms |
| 9/20/2026, 12:00:00 AM | 100% | 12 | 505ms |
| 9/21/2026, 12:00:00 AM | 100% | 12 | 516ms |
| 9/22/2026, 12:00:00 AM | 100% | 12 | 502ms |
| 9/23/2026, 12:00:00 AM | 100% | 12 | 524ms |
| 9/24/2026, 12:00:00 AM | 100% | 13 | 502ms |
| 9/25/2026, 12:00:00 AM | 100% | 14 | 488ms |
| 9/26/2026, 12:00:00 AM | 100% | 13 | 507ms |
| 9/27/2026, 12:00:00 AM | 100% | 14 | 512ms |
| 9/28/2026, 12:00:00 AM | 100% | 12 | 548ms |
| 9/29/2026, 12:00:00 AM | 100% | 12 | 539ms |
| 9/30/2026, 12:00:00 AM | 100% | 12 | 537ms |
| 10/1/2026, 12:00:00 AM | 100% | 12 | 578ms |
| 10/2/2026, 12:00:00 AM | 100% | 12 | 518ms |
| 10/3/2026, 12:00:00 AM | 100% | 12 | 544ms |
| 10/4/2026, 12:00:00 AM | 100% | 10 | 509ms |
| 10/5/2026, 12:00:00 AM | 100% | 6 | 630ms |
- Availability
- 100
- Latency
- 91
- Security
- 100
- Transparency
- 49
- Activity
- 70
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
- Cloudflare, Inc
- Domain registered
- 2026-01-31
- Hosting network
- CLOUDFLARENET
- 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)
Payout address changed 20 times, last on 10/5/2026
- 0x04Cd…4EaD → 0x0000…0001 (base) · 10/5/2026
- 0x0000…0001 → 0x04Cd…4EaD (base) · 10/5/2026
- 0x04Cd…4EaD → 0x0000…0001 (base) · 10/5/2026
- 0x0000…0001 → 0x04Cd…4EaD (base) · 10/5/2026
- 0x04Cd…4EaD → 0x0000…0001 (base) · 10/4/2026
- 0x0000…0001 → 0x04Cd…4EaD (base) · 10/4/2026
- 0x04Cd…4EaD → 0x0000…0001 (base) · 10/4/2026
- 0x0000…0001 → 0x04Cd…4EaD (base) · 10/4/2026
- 0x04Cd…4EaD → 0x0000…0001 (base) · 10/4/2026
- 0x0000…0001 → 0x04Cd…4EaD (base) · 10/4/2026
- 0x04Cd…4EaD → 0x0000…0001 (base) · 10/4/2026
- 0x0000…0001 → 0x04Cd…4EaD (base) · 10/4/2026
- 0x04Cd…4EaD → 0x0000…0001 (base) · 10/3/2026
- 0x0000…0001 → 0x04Cd…4EaD (base) · 10/3/2026
- 0x04Cd…4EaD → 0x0000…0001 (base) · 10/3/2026
- 0x0000…0001 → 0x04Cd…4EaD (base) · 10/3/2026
- 0x04Cd…4EaD → 0x0000…0001 (base) · 10/3/2026
- 0x0000…0001 → 0x04Cd…4EaD (base) · 10/3/2026
- 0x04Cd…4EaD → 0x0000…0001 (base) · 10/3/2026
- 0x0000…0001 → 0x04Cd…4EaD (base) · 10/3/2026
A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.
Only payments settled on chains and facilitators we index.
Response schema
{
"input": {
"discoverable": true,
"method": "GET",
"type": "http"
}
}