DNS response history for ns2.nestedkode.com

ns2.nestedkode.com 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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 286 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.nestedkode.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

286 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

166.117.220.151

Most recently resolved hosting IP on selected date

Successful Responses

35

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.nestedkode.com

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:05 639234253963286387
2037 ms 166.117.220.151
34 2026-08-27 10:47 639234243654907465
197 ms 166.117.220.151
33 2026-08-27 10:30 639234233269654413
110 ms 166.117.220.151
32 2026-08-27 10:13 639234222943951923
107 ms 166.117.220.151
31 2026-08-27 09:56 639234212558002823
46 ms 166.117.220.151
30 2026-08-27 09:38 639234202117531850
53 ms 166.117.220.151
29 2026-08-27 09:21 639234191649612722
31 ms 166.117.220.151
28 2026-08-27 09:03 639234181105879568
2013 ms 166.117.220.151
27 2026-08-27 08:46 639234170713214496
47 ms 166.117.220.151
26 2026-08-27 08:29 639234160341037652
29 ms 166.117.220.151
25 2026-08-27 08:11 639234149799404224
44 ms 166.117.220.151
24 2026-08-27 07:54 639234139553286469
289 ms 166.117.220.151
23 2026-08-27 07:00 639234107183588293
55 ms 166.117.220.151
22 2026-08-27 06:43 639234096905435724
52 ms 166.117.220.151
21 2026-08-27 06:26 639234086579410775
44 ms 166.117.220.151
20 2026-08-27 06:09 639234076291157956
43 ms 166.117.220.151
19 2026-08-27 05:51 639234065981939454
65 ms 166.117.220.151
18 2026-08-27 05:34 639234055548642997
48 ms 166.117.220.151
17 2026-08-27 05:17 639234045267979603
40 ms 166.117.220.151
16 2026-08-27 05:00 639234034999717463
53 ms 166.117.220.151
15 2026-08-27 04:43 639234024739225358
45 ms 166.117.220.151
14 2026-08-27 04:25 639234014311170162
48 ms 166.117.220.151
13 2026-08-27 04:08 639234003806017640
54 ms 166.117.220.151
12 2026-08-27 03:50 639233993356203030
25 ms 166.117.220.151
11 2026-08-27 02:57 639233961301716608
31 ms 166.117.220.151
10 2026-08-27 02:40 639233950834200647
2019 ms 166.117.220.151
9 2026-08-27 02:22 639233940431849026
2024 ms 166.117.220.151
8 2026-08-27 02:05 639233930110596398
56 ms 166.117.220.151
7 2026-08-27 01:48 639233919705434540
24 ms 166.117.220.151
6 2026-08-27 01:31 639233909452807845
17 ms 166.117.220.151
5 2026-08-27 01:13 639233899096420820
50 ms 166.117.220.151
4 2026-08-27 00:56 639233888707824939
92 ms 166.117.220.151
3 2026-08-27 00:39 639233878461203802
23 ms 166.117.220.151
2 2026-08-27 00:22 639233868060868209
34 ms 166.117.220.151
1 2026-08-27 00:04 639233857450922991
48 ms 166.117.220.151