DNS response history for ns.rodem.tv

ns.rodem.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 36 DNS check records, 36 successful responses, 0 failed responses, and 582 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 ns.rodem.tv.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

582 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.43.210.126

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns.rodem.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
36 2026-08-26 11:58 639233414056832719
578 ms 211.43.210.126
35 2026-08-26 11:40 639233403515141099
578 ms 211.43.210.126
34 2026-08-26 10:45 639233370841350248
575 ms 211.43.210.126
33 2026-08-26 10:28 639233360361507238
582 ms 211.43.210.126
32 2026-08-26 10:11 639233350067824371
557 ms 211.43.210.126
31 2026-08-26 09:54 639233339545274518
564 ms 211.43.210.126
30 2026-08-26 09:36 639233329214918079
568 ms 211.43.210.126
29 2026-08-26 09:19 639233318749762337
602 ms 211.43.210.126
28 2026-08-26 09:01 639233308387917838
598 ms 211.43.210.126
27 2026-08-26 08:44 639233297961740122
580 ms 211.43.210.126
26 2026-08-26 08:27 639233287487159094
610 ms 211.43.210.126
25 2026-08-26 08:09 639233276995531707
594 ms 211.43.210.126
24 2026-08-26 07:52 639233266521568229
585 ms 211.43.210.126
23 2026-08-26 07:34 639233256081047431
582 ms 211.43.210.126
22 2026-08-26 06:40 639233223620132921
572 ms 211.43.210.126
21 2026-08-26 06:23 639233213287814244
572 ms 211.43.210.126
20 2026-08-26 06:06 639233202925983161
572 ms 211.43.210.126
19 2026-08-26 05:48 639233192644780696
572 ms 211.43.210.126
18 2026-08-26 05:31 639233182401183833
570 ms 211.43.210.126
17 2026-08-26 05:14 639233172074181051
572 ms 211.43.210.126
16 2026-08-26 04:57 639233161808421455
589 ms 211.43.210.126
15 2026-08-26 04:40 639233151357344052
583 ms 211.43.210.126
14 2026-08-26 04:22 639233141034116946
581 ms 211.43.210.126
13 2026-08-26 04:05 639233130828334142
576 ms 211.43.210.126
12 2026-08-26 03:48 639233120373450007
590 ms 211.43.210.126
11 2026-08-26 03:31 639233110066216193
598 ms 211.43.210.126
10 2026-08-26 02:37 639233078065410564
607 ms 211.43.210.126
9 2026-08-26 02:20 639233067787457832
576 ms 211.43.210.126
8 2026-08-26 02:03 639233057501801162
575 ms 211.43.210.126
7 2026-08-26 01:46 639233047089431703
578 ms 211.43.210.126
6 2026-08-26 01:29 639233036754790688
557 ms 211.43.210.126
5 2026-08-26 01:11 639233026412602472
597 ms 211.43.210.126
4 2026-08-26 00:54 639233016064066127
573 ms 211.43.210.126
3 2026-08-26 00:37 639233005922655772
600 ms 211.43.210.126
2 2026-08-26 00:20 639232995672256907
590 ms 211.43.210.126
1 2026-08-26 00:03 639232985300872416
605 ms 211.43.210.126