Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
97.4% avgResponse time
p50 404ms · p95 512msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/29/2026, 11:00:00 PM | 100% | 1 | 418ms |
| 9/30/2026, 2:00:00 AM | 0% | 1 | — |
| 9/30/2026, 4:00:00 AM | 100% | 1 | 505ms |
| 9/30/2026, 6:00:00 AM | 100% | 1 | 510ms |
| 9/30/2026, 8:00:00 AM | 100% | 1 | 500ms |
| 9/30/2026, 10:00:00 AM | 100% | 1 | 416ms |
| 9/30/2026, 12:00:00 PM | 100% | 1 | 449ms |
| 9/30/2026, 2:00:00 PM | 100% | 1 | 516ms |
| 9/30/2026, 4:00:00 PM | 100% | 1 | 521ms |
| 9/30/2026, 6:00:00 PM | 100% | 1 | 420ms |
| 9/30/2026, 8:00:00 PM | 100% | 1 | 418ms |
| 9/30/2026, 10:00:00 PM | 100% | 1 | 368ms |
| 10/1/2026, 12:00:00 AM | 100% | 1 | 410ms |
| 10/1/2026, 2:00:00 AM | 0% | 1 | — |
| 10/1/2026, 4:00:00 AM | 100% | 1 | 421ms |
| 10/1/2026, 6:00:00 AM | 100% | 1 | 402ms |
| 10/1/2026, 8:00:00 AM | 100% | 1 | 482ms |
| 10/1/2026, 10:00:00 AM | 100% | 1 | 427ms |
| 10/1/2026, 12:00:00 PM | 100% | 1 | 394ms |
| 10/1/2026, 2:00:00 PM | 100% | 1 | 522ms |
| 10/1/2026, 4:00:00 PM | 100% | 1 | 500ms |
| 10/1/2026, 6:00:00 PM | 100% | 1 | 389ms |
| 10/1/2026, 8:00:00 PM | 100% | 1 | 499ms |
| 10/1/2026, 10:00:00 PM | 100% | 1 | 384ms |
| 10/2/2026, 12:00:00 AM | 100% | 1 | 371ms |
| 10/2/2026, 2:00:00 AM | 100% | 1 | 397ms |
| 10/2/2026, 4:00:00 AM | 100% | 1 | 518ms |
| 10/2/2026, 6:00:00 AM | 100% | 1 | 401ms |
| 10/2/2026, 8:00:00 AM | 100% | 1 | 402ms |
| 10/2/2026, 10:00:00 AM | 100% | 1 | 387ms |
| 10/2/2026, 12:00:00 PM | 100% | 1 | 469ms |
| 10/2/2026, 2:00:00 PM | 100% | 1 | 385ms |
| 10/2/2026, 4:00:00 PM | 100% | 1 | 499ms |
| 10/2/2026, 6:00:00 PM | 100% | 1 | 387ms |
| 10/2/2026, 8:00:00 PM | 100% | 1 | 398ms |
| 10/2/2026, 11:00:00 PM | 100% | 1 | 474ms |
| 10/3/2026, 12:00:00 AM | 100% | 1 | 415ms |
| 10/3/2026, 2:00:00 AM | 100% | 1 | 373ms |
| 10/3/2026, 4:00:00 AM | 100% | 1 | 392ms |
| 10/3/2026, 6:00:00 AM | 100% | 1 | 489ms |
| 10/3/2026, 8:00:00 AM | 100% | 1 | 405ms |
| 10/3/2026, 10:00:00 AM | 100% | 1 | 399ms |
| 10/3/2026, 12:00:00 PM | 100% | 1 | 366ms |
| 10/3/2026, 2:00:00 PM | 100% | 1 | 509ms |
| 10/3/2026, 4:00:00 PM | 100% | 1 | 401ms |
| 10/3/2026, 6:00:00 PM | 100% | 1 | 504ms |
| 10/3/2026, 8:00:00 PM | 100% | 1 | 479ms |
| 10/3/2026, 11:00:00 PM | 100% | 1 | 395ms |
| 10/4/2026, 1:00:00 AM | 100% | 1 | 493ms |
| 10/4/2026, 2:00:00 AM | 100% | 1 | 123ms |
| 10/4/2026, 3:00:00 AM | 100% | 1 | 476ms |
| 10/4/2026, 5:00:00 AM | 100% | 1 | 387ms |
| 10/4/2026, 7:00:00 AM | 100% | 1 | 366ms |
| 10/4/2026, 9:00:00 AM | 100% | 1 | 359ms |
| 10/4/2026, 1:00:00 PM | 100% | 1 | 461ms |
| 10/4/2026, 3:00:00 PM | 100% | 1 | 490ms |
| 10/4/2026, 5:00:00 PM | 100% | 1 | 388ms |
| 10/4/2026, 7:00:00 PM | 100% | 1 | 407ms |
| 10/4/2026, 9:00:00 PM | 100% | 1 | 496ms |
| 10/5/2026, 2:00:00 AM | 100% | 1 | 379ms |
| 10/5/2026, 8:00:00 AM | 100% | 1 | 390ms |
| 10/5/2026, 9:00:00 AM | 100% | 1 | 403ms |
| 10/5/2026, 11:00:00 AM | 100% | 1 | 465ms |
| 10/5/2026, 1:00:00 PM | 100% | 1 | 395ms |
| 10/5/2026, 2:00:00 PM | 100% | 1 | 445ms |
| 10/5/2026, 4:00:00 PM | 100% | 1 | 381ms |
| 10/5/2026, 6:00:00 PM | 100% | 1 | 376ms |
| 10/5/2026, 8:00:00 PM | 100% | 1 | 395ms |
| 10/5/2026, 10:00:00 PM | 100% | 1 | 383ms |
| 10/6/2026, 1:00:00 AM | 100% | 1 | 472ms |
| 10/6/2026, 2:00:00 AM | 100% | 1 | 393ms |
| 10/6/2026, 5:00:00 AM | 100% | 1 | 479ms |
| 10/6/2026, 11:00:00 AM | 100% | 1 | 405ms |
| 10/6/2026, 1:00:00 PM | 100% | 1 | 386ms |
| 10/6/2026, 3:00:00 PM | 100% | 1 | 388ms |
| 10/6/2026, 5:00:00 PM | 100% | 1 | 395ms |
| 10/6/2026, 7:00:00 PM | 100% | 1 | 388ms |
- Availability
- 99
- Latency
- 96
- Security
- 97
- Transparency
- 30
- Activity
- 5
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
- CLOUD-NBG1
- Hosting country
- DE
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/23/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 9/15/2026 | 1 | 0.05 | 1 |
| 9/20/2026 | 2 | 0.1 | 1 |
| 9/21/2026 | 1 | 0.05 | 1 |
| 9/23/2026 | 1 | 0.04 | 1 |
Only payments settled on chains and facilitators we index.