DNS response history for ns2.valse-dns.net

ns2.valse-dns.net 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 193 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.valse-dns.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

193 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

124.217.247.101

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.valse-dns.net

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 12:04 639233424567558554
17 ms 124.217.247.101
35 2026-08-26 11:46 639233414056832719
2018 ms 124.217.247.101
34 2026-08-26 11:29 639233403515141099
40 ms 124.217.247.101
33 2026-08-26 10:34 639233370841350248
21 ms 124.217.247.101
32 2026-08-26 10:17 639233360361507238
23 ms 124.217.247.101
31 2026-08-26 10:00 639233350067824371
8 ms 124.217.247.101
30 2026-08-26 09:42 639233339545274518
26 ms 124.217.247.101
29 2026-08-26 09:25 639233329214918079
2032 ms 124.217.247.101
28 2026-08-26 09:08 639233318749762337
2019 ms 124.217.247.101
27 2026-08-26 08:50 639233308387917838
69 ms 124.217.247.101
26 2026-08-26 08:33 639233297961740122
46 ms 124.217.247.101
25 2026-08-26 08:15 639233287487159094
38 ms 124.217.247.101
24 2026-08-26 07:58 639233276995531707
40 ms 124.217.247.101
23 2026-08-26 07:40 639233266521568229
9 ms 124.217.247.101
22 2026-08-26 07:23 639233256081047431
41 ms 124.217.247.101
21 2026-08-26 06:29 639233223620132921
6 ms 124.217.247.101
20 2026-08-26 06:12 639233213287814244
21 ms 124.217.247.101
19 2026-08-26 05:54 639233202925983161
13 ms 124.217.247.101
18 2026-08-26 05:37 639233192644780696
16 ms 124.217.247.101
17 2026-08-26 05:20 639233182401183833
10 ms 124.217.247.101
16 2026-08-26 05:03 639233172074181051
14 ms 124.217.247.101
15 2026-08-26 04:46 639233161808421455
37 ms 124.217.247.101
14 2026-08-26 04:28 639233151357344052
36 ms 124.217.247.101
13 2026-08-26 04:11 639233141034116946
8 ms 124.217.247.101
12 2026-08-26 03:54 639233130828334142
30 ms 124.217.247.101
11 2026-08-26 03:37 639233120373450007
7 ms 124.217.247.101
10 2026-08-26 03:20 639233110066216193
112 ms 124.217.247.101
9 2026-08-26 02:26 639233078065410564
11 ms 124.217.247.101
8 2026-08-26 02:09 639233067787457832
8 ms 124.217.247.101
7 2026-08-26 01:52 639233057501801162
17 ms 124.217.247.101
6 2026-08-26 01:35 639233047089431703
34 ms 124.217.247.101
5 2026-08-26 01:17 639233036754790688
33 ms 124.217.247.101
4 2026-08-26 01:00 639233026412602472
19 ms 124.217.247.101
3 2026-08-26 00:43 639233016064066127
10 ms 124.217.247.101
2 2026-08-26 00:26 639233005922655772
36 ms 124.217.247.101
1 2026-08-26 00:09 639232995672256907
30 ms 124.217.247.101