DNS response history for ns2.harum.tv

ns2.harum.tv is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 24 DNS check records, 24 successful responses, 0 failed responses, and 504 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.harum.tv.
Records on Selected Date

24

Historical checks stored for this nameserver on selected date

Average Latency

504 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 07:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.136.127.98

Most recently resolved hosting IP on selected date

Successful Responses

24

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.harum.tv

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
24 2026-08-26 07:50 639233266521568229
360 ms 108.136.127.98
23 2026-08-26 07:32 639233256081047431
2328 ms 108.136.127.98
22 2026-08-26 06:38 639233223620132921
363 ms 108.136.127.98
21 2026-08-26 06:21 639233213287814244
355 ms 108.136.127.98
20 2026-08-26 06:04 639233202925983161
359 ms 108.136.127.98
19 2026-08-26 05:46 639233192644780696
194 ms 108.136.127.98
18 2026-08-26 05:29 639233182401183833
338 ms 108.136.127.98
17 2026-08-26 05:12 639233172074181051
357 ms 108.136.127.98
16 2026-08-26 04:55 639233161808421455
354 ms 108.136.127.98
15 2026-08-26 04:38 639233151357344052
367 ms 108.136.127.98
14 2026-08-26 04:20 639233141034116946
364 ms 108.136.127.98
13 2026-08-26 04:03 639233130828334142
358 ms 108.136.127.98
12 2026-08-26 03:46 639233120373450007
360 ms 108.136.127.98
11 2026-08-26 03:29 639233110066216193
379 ms 108.136.127.98
10 2026-08-26 02:35 639233078065410564
356 ms 108.136.127.98
9 2026-08-26 02:18 639233067787457832
362 ms 108.136.127.98
8 2026-08-26 02:01 639233057501801162
351 ms 108.136.127.98
7 2026-08-26 01:44 639233047089431703
371 ms 108.136.127.98
6 2026-08-26 01:27 639233036754790688
360 ms 108.136.127.98
5 2026-08-26 01:09 639233026412602472
355 ms 108.136.127.98
4 2026-08-26 00:52 639233016064066127
352 ms 108.136.127.98
3 2026-08-26 00:35 639233005922655772
2193 ms 108.136.127.98
2 2026-08-26 00:18 639232995672256907
193 ms 108.136.127.98
1 2026-08-26 00:01 639232985300872416
360 ms 108.136.127.98