DNS response history for ns2.must-visits.be

ns2.must-visits.be 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 415 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.must-visits.be.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

415 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

149.210.235.13

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 ns2.must-visits.be

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:55 639233414056832719
2037 ms 149.210.235.13
35 2026-08-26 11:37 639233403515141099
56 ms 149.210.235.13
34 2026-08-26 10:42 639233370841350248
27 ms 149.210.235.13
33 2026-08-26 10:25 639233360361507238
712 ms 149.210.235.13
32 2026-08-26 10:08 639233350067824371
4040 ms 149.210.235.13
31 2026-08-26 09:50 639233339545274518
30 ms 149.210.235.13
30 2026-08-26 09:33 639233329214918079
22 ms 149.210.235.13
29 2026-08-26 09:16 639233318749762337
25 ms 149.210.235.13
28 2026-08-26 08:58 639233308387917838
26 ms 149.210.235.13
27 2026-08-26 08:41 639233297961740122
51 ms 149.210.235.13
26 2026-08-26 08:23 639233287487159094
55 ms 149.210.235.13
25 2026-08-26 08:06 639233276995531707
48 ms 149.210.235.13
24 2026-08-26 07:49 639233266521568229
3622 ms 149.210.235.13
23 2026-08-26 07:31 639233256081047431
53 ms 149.210.235.13
22 2026-08-26 06:37 639233223620132921
46 ms 149.210.235.13
21 2026-08-26 06:20 639233213287814244
52 ms 149.210.235.13
20 2026-08-26 06:02 639233202925983161
59 ms 149.210.235.13
19 2026-08-26 05:45 639233192644780696
2039 ms 149.210.235.13
18 2026-08-26 05:28 639233182401183833
56 ms 149.210.235.13
17 2026-08-26 05:11 639233172074181051
21 ms 149.210.235.13
16 2026-08-26 04:54 639233161808421455
36 ms 149.210.235.13
15 2026-08-26 04:37 639233151357344052
52 ms 149.210.235.13
14 2026-08-26 04:19 639233141034116946
52 ms 149.210.235.13
13 2026-08-26 04:02 639233130828334142
1095 ms 149.210.235.13
12 2026-08-26 03:45 639233120373450007
45 ms 149.210.235.13
11 2026-08-26 03:28 639233110066216193
53 ms 149.210.235.13
10 2026-08-26 02:34 639233078065410564
58 ms 149.210.235.13
9 2026-08-26 02:17 639233067787457832
50 ms 149.210.235.13
8 2026-08-26 02:00 639233057501801162
50 ms 149.210.235.13
7 2026-08-26 01:43 639233047089431703
63 ms 149.210.235.13
6 2026-08-26 01:26 639233036754790688
52 ms 149.210.235.13
5 2026-08-26 01:08 639233026412602472
21 ms 149.210.235.13
4 2026-08-26 00:51 639233016064066127
54 ms 149.210.235.13
3 2026-08-26 00:34 639233005922655772
62 ms 149.210.235.13
2 2026-08-26 00:17 639232995672256907
50 ms 149.210.235.13
1 2026-08-26 00:00 639232985300872416
55 ms 149.210.235.13