Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 296ms · p95 449msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/29/2026, 8:00:00 AM | 100% | 1 | 296ms |
| 9/29/2026, 10:00:00 AM | 100% | 1 | 223ms |
| 9/29/2026, 12:00:00 PM | 100% | 1 | 228ms |
| 9/29/2026, 2:00:00 PM | 100% | 1 | 289ms |
| 9/29/2026, 4:00:00 PM | 100% | 1 | 143ms |
| 9/29/2026, 6:00:00 PM | 100% | 1 | 303ms |
| 9/29/2026, 8:00:00 PM | 100% | 1 | 331ms |
| 9/29/2026, 10:00:00 PM | 100% | 1 | 355ms |
| 9/30/2026, 1:00:00 AM | 100% | 1 | 320ms |
| 9/30/2026, 3:00:00 AM | 100% | 1 | 212ms |
| 9/30/2026, 5:00:00 AM | 100% | 1 | 300ms |
| 9/30/2026, 7:00:00 AM | 100% | 1 | 410ms |
| 9/30/2026, 9:00:00 AM | 100% | 1 | 384ms |
| 9/30/2026, 11:00:00 AM | 100% | 1 | 335ms |
| 9/30/2026, 1:00:00 PM | 100% | 1 | 517ms |
| 9/30/2026, 3:00:00 PM | 100% | 1 | 1275ms |
| 9/30/2026, 5:00:00 PM | 100% | 1 | 209ms |
| 9/30/2026, 7:00:00 PM | 100% | 1 | 311ms |
| 9/30/2026, 9:00:00 PM | 100% | 1 | 432ms |
| 9/30/2026, 11:00:00 PM | 100% | 1 | 328ms |
| 10/1/2026, 1:00:00 AM | 100% | 1 | 331ms |
| 10/1/2026, 3:00:00 AM | 100% | 1 | 383ms |
| 10/1/2026, 5:00:00 AM | 100% | 1 | 219ms |
| 10/1/2026, 7:00:00 AM | 100% | 1 | 349ms |
| 10/1/2026, 9:00:00 AM | 100% | 1 | 284ms |
| 10/1/2026, 11:00:00 AM | 100% | 1 | 280ms |
| 10/1/2026, 1:00:00 PM | 100% | 1 | 419ms |
| 10/1/2026, 3:00:00 PM | 100% | 1 | 326ms |
| 10/1/2026, 5:00:00 PM | 100% | 1 | 186ms |
| 10/1/2026, 7:00:00 PM | 100% | 1 | 447ms |
| 10/1/2026, 9:00:00 PM | 100% | 1 | 433ms |
| 10/1/2026, 11:00:00 PM | 100% | 1 | 360ms |
| 10/2/2026, 1:00:00 AM | 100% | 1 | 402ms |
| 10/2/2026, 3:00:00 AM | 100% | 1 | 205ms |
| 10/2/2026, 5:00:00 AM | 100% | 1 | 304ms |
| 10/2/2026, 7:00:00 AM | 100% | 1 | 363ms |
| 10/2/2026, 9:00:00 AM | 100% | 1 | 291ms |
| 10/2/2026, 11:00:00 AM | 100% | 1 | 258ms |
| 10/2/2026, 1:00:00 PM | 100% | 1 | 297ms |
| 10/2/2026, 3:00:00 PM | 100% | 1 | 375ms |
| 10/2/2026, 5:00:00 PM | 100% | 1 | 426ms |
| 10/2/2026, 7:00:00 PM | 100% | 1 | 487ms |
| 10/2/2026, 9:00:00 PM | 100% | 1 | 219ms |
| 10/2/2026, 11:00:00 PM | 100% | 1 | 314ms |
| 10/3/2026, 12:00:00 AM | 100% | 1 | 185ms |
| 10/3/2026, 2:00:00 AM | 100% | 1 | 283ms |
| 10/3/2026, 4:00:00 AM | 100% | 1 | 310ms |
| 10/3/2026, 6:00:00 AM | 100% | 1 | 208ms |
| 10/3/2026, 8:00:00 AM | 100% | 1 | 293ms |
| 10/3/2026, 10:00:00 AM | 100% | 1 | 306ms |
| 10/3/2026, 12:00:00 PM | 100% | 1 | 202ms |
| 10/3/2026, 2:00:00 PM | 100% | 1 | 264ms |
| 10/3/2026, 4:00:00 PM | 100% | 1 | 261ms |
| 10/3/2026, 6:00:00 PM | 100% | 1 | 229ms |
| 10/3/2026, 7:00:00 PM | 100% | 1 | 245ms |
| 10/3/2026, 9:00:00 PM | 100% | 1 | 181ms |
| 10/3/2026, 11:00:00 PM | 100% | 1 | 302ms |
| 10/4/2026, 1:00:00 AM | 100% | 1 | 329ms |
| 10/4/2026, 3:00:00 AM | 100% | 1 | 182ms |
| 10/4/2026, 5:00:00 AM | 100% | 1 | 198ms |
| 10/4/2026, 7:00:00 AM | 100% | 1 | 305ms |
| 10/4/2026, 9:00:00 AM | 100% | 1 | 293ms |
| 10/4/2026, 1:00:00 PM | 100% | 1 | 245ms |
| 10/4/2026, 3:00:00 PM | 100% | 1 | 272ms |
| 10/4/2026, 5:00:00 PM | 100% | 1 | 249ms |
| 10/4/2026, 7:00:00 PM | 100% | 1 | 206ms |
| 10/4/2026, 8:00:00 PM | 100% | 1 | 445ms |
| 10/5/2026, 2:00:00 AM | 100% | 1 | 378ms |
| 10/5/2026, 7:00:00 AM | 100% | 1 | 181ms |
| 10/5/2026, 9:00:00 AM | 100% | 1 | 287ms |
| 10/5/2026, 11:00:00 AM | 100% | 1 | 293ms |
| 10/5/2026, 1:00:00 PM | 100% | 1 | 344ms |
| 10/5/2026, 2:00:00 PM | 100% | 1 | 292ms |
| 10/5/2026, 4:00:00 PM | 100% | 1 | 219ms |
| 10/5/2026, 6:00:00 PM | 100% | 1 | 193ms |
| 10/5/2026, 8:00:00 PM | 100% | 1 | 210ms |
| 10/5/2026, 10:00:00 PM | 100% | 1 | 403ms |
| 10/6/2026, 1:00:00 AM | 100% | 1 | 493ms |
| 10/6/2026, 2:00:00 AM | 100% | 1 | 323ms |
| 10/6/2026, 5:00:00 AM | 100% | 1 | 220ms |
- Availability
- 99
- Latency
- 100
- Security
- 100
- Transparency
- 49
- 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
- USD
- Networks
- tempo
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- NAMECHEAP
- Domain registered
- 2024-12-25
- Hosting network
- AMAZON-CF
- 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.
Response schema
{
"$ref": "#/components/schemas/type_inboxes:ListInboxesResponse"
}