DNS response history for ns2.nestorakey.com

ns2.nestorakey.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 294 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.nestorakey.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

294 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.121.72.86

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.nestorakey.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:11 639234253963286387
112 ms 129.121.72.86
34 2026-08-27 10:54 639234243654907465
196 ms 129.121.72.86
33 2026-08-27 10:36 639234233269654413
199 ms 129.121.72.86
32 2026-08-27 10:19 639234222943951923
203 ms 129.121.72.86
31 2026-08-27 10:02 639234212558002823
200 ms 129.121.72.86
30 2026-08-27 09:44 639234202117531850
204 ms 129.121.72.86
29 2026-08-27 09:27 639234191649612722
197 ms 129.121.72.86
28 2026-08-27 09:09 639234181105879568
203 ms 129.121.72.86
27 2026-08-27 08:52 639234170713214496
195 ms 129.121.72.86
26 2026-08-27 08:35 639234160341037652
200 ms 129.121.72.86
25 2026-08-27 08:17 639234149799404224
204 ms 129.121.72.86
24 2026-08-27 08:00 639234139553286469
218 ms 129.121.72.86
23 2026-08-27 07:06 639234107183588293
201 ms 129.121.72.86
22 2026-08-27 06:49 639234096905435724
198 ms 129.121.72.86
21 2026-08-27 06:32 639234086579410775
12 ms 129.121.72.86
20 2026-08-27 06:15 639234076291157956
199 ms 129.121.72.86
19 2026-08-27 05:58 639234065981939454
205 ms 129.121.72.86
18 2026-08-27 05:40 639234055548642997
204 ms 129.121.72.86
17 2026-08-27 05:23 639234045267979603
102 ms 129.121.72.86
16 2026-08-27 05:06 639234034999717463
201 ms 129.121.72.86
15 2026-08-27 04:49 639234024739225358
2148 ms 129.121.72.86
14 2026-08-27 04:32 639234014311170162
134 ms 129.121.72.86
13 2026-08-27 04:14 639234003806017640
199 ms 129.121.72.86
12 2026-08-27 03:56 639233993356203030
208 ms 129.121.72.86
11 2026-08-27 03:03 639233961301716608
2218 ms 129.121.72.86
10 2026-08-27 02:46 639233950834200647
198 ms 129.121.72.86
9 2026-08-27 02:28 639233940431849026
204 ms 129.121.72.86
8 2026-08-27 02:11 639233930110596398
198 ms 129.121.72.86
7 2026-08-27 01:54 639233919705434540
121 ms 129.121.72.86
6 2026-08-27 01:37 639233909452807845
199 ms 129.121.72.86
5 2026-08-27 01:20 639233899096420820
195 ms 129.121.72.86
4 2026-08-27 01:02 639233888707824939
211 ms 129.121.72.86
3 2026-08-27 00:45 639233878461203802
7 ms 129.121.72.86
2 2026-08-27 00:28 639233868060868209
193 ms 129.121.72.86
1 2026-08-27 00:10 639233857450922991
202 ms 129.121.72.86