NTHFS RTK - Status History

Dashboard Admin Login
NTHFS RTK
http://140.78.138.15:8080
7 days 14 days 30 days 60 days 90 days

Status Changes (Last 30 days)

UP 224 checks
Period: 2026-01-06 13:04:56 CET → 2026-01-07 07:46:10 CET
Average response time: 0.05s
✓ 224 successful
Duration: 18.7 hours
DOWN 1 check
Period: 2026-01-06 12:59:53 CET → 2026-01-06 13:04:56 CET
✗ 1 failed
Last Error:
HTTPConnectionPool(host='140.78.138.15', port=8080): Read timed out. (read timeout=30)
UP 2375 checks
Period: 2025-12-29 06:36:24 CET → 2026-01-06 12:59:53 CET
Average response time: 0.04s
✓ 2375 successful
Duration: 8.3 days
DOWN 2 checks
Period: 2025-12-29 06:25:51 CET → 2025-12-29 06:36:24 CET
✗ 2 failed
Duration: 11 minutes
Last Error:
HTTPConnectionPool(host='140.78.138.15', port=8080): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xef1ce4c88690>, 'Connection to 140.78.138.15 timed out. (connect timeout=30)'))
UP 1792 checks
Period: 2025-12-23 00:28:05 CET → 2025-12-29 06:25:51 CET
Average response time: 0.04s
✓ 1792 successful
Duration: 6.2 days
DOWN 1 check
Period: 2025-12-23 00:23:03 CET → 2025-12-23 00:28:05 CET
✗ 1 failed
Last Error:
HTTPConnectionPool(host='140.78.138.15', port=8080): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0xef1ce4994750>, 'Connection to 140.78.138.15 timed out. (connect timeout=30)'))
UP 1006 checks
Period: 2025-12-19 12:16:28 CET → 2025-12-23 00:23:03 CET
Average response time: 0.04s
✓ 1006 successful
Duration: 3.5 days
DOWN 1 check
Period: 2025-12-19 12:11:25 CET → 2025-12-19 12:16:28 CET
✗ 1 failed
Last Error:
HTTPConnectionPool(host='140.78.138.15', port=8080): Read timed out. (read timeout=30)
UP 3213 checks
Period: 2025-12-08 07:50:36 CET → 2025-12-19 12:11:25 CET
Average response time: 0.04s
✓ 3213 successful
Duration: 11.2 days
Back to Dashboard