QuintaDB
https://quintadb.ru/mcpNo-code databases, forms, portals and AI sites. Manage records and automation via natural language.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 884ms · p95 985msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/9/2026, 12:00:00 AM | 100% | 1 | 961ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 973ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 964ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 962ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 965ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 961ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 858ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 965ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 997ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 960ms |
| 8/19/2026, 12:00:00 AM | 100% | 21 | 959ms |
| 8/20/2026, 12:00:00 AM | 100% | 20 | 966ms |
| 8/21/2026, 12:00:00 AM | 100% | 22 | 958ms |
| 8/22/2026, 12:00:00 AM | 100% | 23 | 982ms |
| 8/23/2026, 12:00:00 AM | 100% | 20 | 962ms |
| 8/24/2026, 12:00:00 AM | 100% | 21 | 965ms |
| 8/25/2026, 12:00:00 AM | 100% | 15 | 957ms |
| 8/26/2026, 12:00:00 AM | 100% | 9 | 862ms |
| 8/27/2026, 12:00:00 AM | 100% | 14 | 858ms |
| 8/28/2026, 12:00:00 AM | 100% | 20 | 860ms |
| 8/29/2026, 12:00:00 AM | 100% | 21 | 874ms |
| 8/30/2026, 12:00:00 AM | 100% | 21 | 888ms |
| 8/31/2026, 12:00:00 AM | 100% | 21 | 876ms |
| 9/1/2026, 12:00:00 AM | 100% | 20 | 920ms |
| 9/2/2026, 12:00:00 AM | 100% | 21 | 875ms |
| 9/3/2026, 12:00:00 AM | 100% | 21 | 953ms |
| 9/4/2026, 12:00:00 AM | 100% | 20 | 878ms |
| 9/5/2026, 12:00:00 AM | 100% | 21 | 953ms |
| 9/6/2026, 12:00:00 AM | 100% | 17 | 950ms |
| 9/7/2026, 12:00:00 AM | 100% | 4 | 918ms |
- Availability
- 100
- Latency
- 79
- Security
- 100
- Transparency
- 12
- 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
- —
- Networks
- —
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- CLOUD-SIN
- Hosting country
- SG
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.