DNS response history for ns2.neopeak.com

ns2.neopeak.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 32 DNS check records, 32 successful responses, 0 failed responses, and 432 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.neopeak.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

432 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.131.66.159

Most recently resolved hosting IP on selected date

Successful Responses

32

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.neopeak.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
32 2026-08-27 10:19 639234222943951923
99 ms 104.131.66.159
31 2026-08-27 10:02 639234212558002823
121 ms 104.131.66.159
30 2026-08-27 09:44 639234202117531850
3 ms 104.131.66.159
29 2026-08-27 09:27 639234191649612722
232 ms 104.131.66.159
28 2026-08-27 09:09 639234181105879568
234 ms 104.131.66.159
27 2026-08-27 08:52 639234170713214496
220 ms 104.131.66.159
26 2026-08-27 08:35 639234160341037652
230 ms 104.131.66.159
25 2026-08-27 08:17 639234149799404224
235 ms 104.131.66.159
24 2026-08-27 08:00 639234139553286469
258 ms 104.131.66.159
23 2026-08-27 07:06 639234107183588293
118 ms 104.131.66.159
22 2026-08-27 06:49 639234096905435724
229 ms 104.131.66.159
21 2026-08-27 06:32 639234086579410775
8 ms 104.131.66.159
20 2026-08-27 06:15 639234076291157956
319 ms 104.131.66.159
19 2026-08-27 05:58 639234065981939454
2227 ms 104.131.66.159
18 2026-08-27 05:40 639234055548642997
2135 ms 104.131.66.159
17 2026-08-27 05:23 639234045267979603
228 ms 104.131.66.159
16 2026-08-27 05:06 639234034999717463
223 ms 104.131.66.159
15 2026-08-27 04:49 639234024739225358
228 ms 104.131.66.159
14 2026-08-27 04:32 639234014311170162
111 ms 104.131.66.159
13 2026-08-27 04:14 639234003806017640
234 ms 104.131.66.159
12 2026-08-27 03:57 639233993356203030
2113 ms 104.131.66.159
11 2026-08-27 03:03 639233961301716608
2133 ms 104.131.66.159
10 2026-08-27 02:46 639233950834200647
220 ms 104.131.66.159
9 2026-08-27 02:28 639233940431849026
104 ms 104.131.66.159
8 2026-08-27 02:11 639233930110596398
233 ms 104.131.66.159
7 2026-08-27 01:54 639233919705434540
92 ms 104.131.66.159
6 2026-08-27 01:37 639233909452807845
216 ms 104.131.66.159
5 2026-08-27 01:20 639233899096420820
224 ms 104.131.66.159
4 2026-08-27 01:02 639233888707824939
233 ms 104.131.66.159
3 2026-08-27 00:45 639233878461203802
101 ms 104.131.66.159
2 2026-08-27 00:28 639233868060868209
227 ms 104.131.66.159
1 2026-08-27 00:10 639233857450922991
245 ms 104.131.66.159