DNS response history for ns2.dayman.net

ns2.dayman.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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 356 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.dayman.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

356 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.10.160

Most recently resolved hosting IP on selected date

Successful Responses

30

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.dayman.net

Showing DNS history for 2026-08-25 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
30 2026-08-25 10:09 639232492740373468
15 ms 162.159.10.160
29 2026-08-25 09:52 639232482235303141
33 ms 162.159.10.160
28 2026-08-25 09:34 639232471861770303
2064 ms 162.159.10.160
27 2026-08-25 09:17 639232461630217327
59 ms 162.159.10.160
26 2026-08-25 09:00 639232451282965990
36 ms 162.159.10.160
25 2026-08-25 08:43 639232440814614938
2036 ms 162.159.10.160
24 2026-08-25 08:25 639232430410720425
33 ms 162.159.10.160
23 2026-08-25 08:08 639232420003096185
24 ms 162.159.10.160
22 2026-08-25 07:50 639232409467287444
2042 ms 162.159.10.160
21 2026-08-25 07:33 639232399077195997
10 ms 162.159.10.160
20 2026-08-25 07:16 639232388731528337
13 ms 162.159.10.160
19 2026-08-25 06:58 639232378288598612
18 ms 162.159.10.160
18 2026-08-25 06:05 639232346196373643
7 ms 162.159.10.160
17 2026-08-25 05:48 639232336112370741
46 ms 162.159.10.160
16 2026-08-25 05:31 639232326146508970
8 ms 162.159.10.160
15 2026-08-25 05:15 639232316189381720
2024 ms 162.159.10.160
14 2026-08-25 04:58 639232306217998913
49 ms 162.159.10.160
13 2026-08-25 04:42 639232296255744174
6 ms 162.159.10.160
12 2026-08-25 04:25 639232286095760789
8 ms 162.159.10.160
11 2026-08-25 04:08 639232276086186273
7 ms 162.159.10.160
10 2026-08-25 03:51 639232265900986425
2034 ms 162.159.10.160
9 2026-08-25 03:34 639232255723518075
8 ms 162.159.10.160
8 2026-08-25 03:17 639232245484452890
6 ms 162.159.10.160
7 2026-08-25 03:00 639232235157175331
32 ms 162.159.10.160
6 2026-08-25 02:06 639232203197189095
12 ms 162.159.10.160
5 2026-08-25 01:49 639232192844564298
25 ms 162.159.10.160
4 2026-08-25 01:32 639232182496008942
18 ms 162.159.10.160
3 2026-08-25 01:15 639232172197053132
5 ms 162.159.10.160
2 2026-08-25 00:21 639232140250307418
3 ms 162.159.10.160
1 2026-08-25 00:04 639232129927860324
7 ms 162.159.10.160