Sporthotel IDEAL Hochgurgl
https://booking.sporthotelideal.at/mcpLive-Verfügbarkeit, Preise und Buchungslinks direkt beim Sporthotel IDEAL Hochgurgl in Tirol.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 1268ms · p95 1677msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/5/2026, 9:00:00 AM | 100% | 1 | 1204ms |
| 9/5/2026, 10:00:00 AM | 100% | 1 | 1189ms |
| 9/5/2026, 11:00:00 AM | 100% | 1 | 1213ms |
| 9/5/2026, 12:00:00 PM | 100% | 1 | 1312ms |
| 9/5/2026, 1:00:00 PM | 100% | 1 | 1032ms |
| 9/5/2026, 2:00:00 PM | 100% | 1 | 881ms |
| 9/5/2026, 4:00:00 PM | 100% | 1 | 1260ms |
| 9/5/2026, 5:00:00 PM | 100% | 1 | 1052ms |
| 9/5/2026, 6:00:00 PM | 100% | 1 | 1281ms |
| 9/5/2026, 7:00:00 PM | 100% | 1 | 984ms |
| 9/5/2026, 8:00:00 PM | 100% | 1 | 1268ms |
| 9/5/2026, 9:00:00 PM | 100% | 1 | 1088ms |
| 9/5/2026, 11:00:00 PM | 100% | 1 | 1979ms |
| 9/6/2026, 12:00:00 AM | 100% | 1 | 1373ms |
| 9/6/2026, 1:00:00 AM | 100% | 1 | 1331ms |
| 9/6/2026, 2:00:00 AM | 100% | 1 | 1008ms |
| 9/6/2026, 3:00:00 AM | 100% | 1 | 884ms |
| 9/6/2026, 4:00:00 AM | 100% | 1 | 1182ms |
| 9/6/2026, 6:00:00 AM | 100% | 1 | 1435ms |
| 9/6/2026, 7:00:00 AM | 100% | 1 | 1343ms |
| 9/6/2026, 8:00:00 AM | 100% | 1 | 1299ms |
| 9/6/2026, 9:00:00 AM | 100% | 1 | 1379ms |
| 9/6/2026, 10:00:00 AM | 100% | 1 | 1469ms |
| 9/6/2026, 11:00:00 AM | 100% | 1 | 1475ms |
| 9/6/2026, 1:00:00 PM | 100% | 1 | 1367ms |
| 9/6/2026, 2:00:00 PM | 100% | 1 | 1007ms |
| 9/6/2026, 4:00:00 PM | 100% | 1 | 1410ms |
| 9/6/2026, 6:00:00 PM | 100% | 1 | 1250ms |
| 9/6/2026, 8:00:00 PM | 100% | 1 | 1446ms |
| 9/6/2026, 10:00:00 PM | 100% | 1 | 1011ms |
| 9/7/2026, 12:00:00 AM | 100% | 1 | 798ms |
| 9/7/2026, 2:00:00 AM | 100% | 1 | 3024ms |
| 9/7/2026, 4:00:00 AM | 100% | 1 | 1466ms |
- Availability
- 100
- Latency
- 64
- Security
- 100
- Transparency
- 42
- 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 66% — 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
- Futureweb-GmbH
- Hosting country
- AT
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.