Usero
https://usero.io/mcpRead your Usero feedback inbox and clusters, file feedback, build forms, and open an AI PR.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 869ms · p95 1304msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/4/2026, 9:00:00 PM | 100% | 1 | 950ms |
| 9/4/2026, 10:00:00 PM | 100% | 1 | 909ms |
| 9/4/2026, 11:00:00 PM | 100% | 1 | 766ms |
| 9/5/2026, 12:00:00 AM | 100% | 1 | 940ms |
| 9/5/2026, 1:00:00 AM | 100% | 1 | 829ms |
| 9/5/2026, 3:00:00 AM | 100% | 1 | 38ms |
| 9/5/2026, 4:00:00 AM | 100% | 1 | 869ms |
| 9/5/2026, 5:00:00 AM | 100% | 1 | 840ms |
| 9/5/2026, 6:00:00 AM | 100% | 1 | 813ms |
| 9/5/2026, 7:00:00 AM | 100% | 1 | 795ms |
| 9/5/2026, 8:00:00 AM | 100% | 1 | 804ms |
| 9/5/2026, 10:00:00 AM | 100% | 1 | 857ms |
| 9/5/2026, 11:00:00 AM | 100% | 1 | 883ms |
| 9/5/2026, 12:00:00 PM | 100% | 1 | 866ms |
| 9/5/2026, 1:00:00 PM | 100% | 1 | 868ms |
| 9/5/2026, 2:00:00 PM | 100% | 1 | 818ms |
| 9/5/2026, 3:00:00 PM | 100% | 1 | 945ms |
| 9/5/2026, 5:00:00 PM | 100% | 1 | 956ms |
| 9/5/2026, 6:00:00 PM | 100% | 1 | 924ms |
| 9/5/2026, 7:00:00 PM | 100% | 1 | 1267ms |
| 9/5/2026, 8:00:00 PM | 100% | 1 | 1449ms |
| 9/5/2026, 9:00:00 PM | 100% | 1 | 965ms |
| 9/5/2026, 10:00:00 PM | 100% | 1 | 95ms |
| 9/6/2026, 12:00:00 AM | 100% | 1 | 77ms |
| 9/6/2026, 1:00:00 AM | 100% | 1 | 915ms |
| 9/6/2026, 2:00:00 AM | 100% | 1 | 1308ms |
| 9/6/2026, 3:00:00 AM | 100% | 1 | 1259ms |
| 9/6/2026, 4:00:00 AM | 100% | 1 | 918ms |
| 9/6/2026, 5:00:00 AM | 100% | 1 | 949ms |
| 9/6/2026, 7:00:00 AM | 100% | 1 | 791ms |
| 9/6/2026, 8:00:00 AM | 100% | 1 | 798ms |
| 9/6/2026, 9:00:00 AM | 100% | 1 | 859ms |
| 9/6/2026, 10:00:00 AM | 100% | 1 | 804ms |
| 9/6/2026, 11:00:00 AM | 100% | 1 | 957ms |
| 9/6/2026, 12:00:00 PM | 100% | 1 | 834ms |
| 9/6/2026, 2:00:00 PM | 100% | 1 | 902ms |
| 9/6/2026, 4:00:00 PM | 100% | 1 | 1349ms |
| 9/6/2026, 6:00:00 PM | 100% | 1 | 1208ms |
| 9/6/2026, 8:00:00 PM | 100% | 1 | 804ms |
| 9/6/2026, 10:00:00 PM | 100% | 1 | 888ms |
| 9/7/2026, 12:00:00 AM | 100% | 1 | 889ms |
| 9/7/2026, 2:00:00 AM | 100% | 1 | 355ms |
| 9/7/2026, 4:00:00 AM | 100% | 1 | 76ms |
- Availability
- 100
- Latency
- 79
- Security
- 100
- Transparency
- 30
- 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 86% — 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
- —
- Networks
- —
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- —
- 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.