DNS response history for ns2.secureparkme.com

ns2.secureparkme.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 172 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.secureparkme.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

172 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.25.129

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.secureparkme.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:09 639234253963286387
83 ms 162.159.25.129
34 2026-08-27 10:52 639234243654907465
53 ms 162.159.25.129
33 2026-08-27 10:35 639234233269654413
339 ms 162.159.25.129
32 2026-08-27 10:17 639234222943951923
30 ms 162.159.25.129
31 2026-08-27 10:00 639234212558002823
76 ms 162.159.25.129
30 2026-08-27 09:43 639234202117531850
40 ms 162.159.25.129
29 2026-08-27 09:25 639234191649612722
10 ms 162.159.25.129
28 2026-08-27 09:08 639234181105879568
40 ms 162.159.25.129
27 2026-08-27 08:50 639234170713214496
184 ms 162.159.25.129
26 2026-08-27 08:33 639234160341037652
36 ms 162.159.25.129
25 2026-08-27 08:16 639234149799404224
22 ms 162.159.25.129
24 2026-08-27 07:58 639234139553286469
75 ms 162.159.25.129
23 2026-08-27 07:05 639234107183588293
189 ms 162.159.25.129
22 2026-08-27 06:47 639234096905435724
33 ms 162.159.25.129
21 2026-08-27 06:30 639234086579410775
16 ms 162.159.25.129
20 2026-08-27 06:13 639234076291157956
55 ms 162.159.25.129
19 2026-08-27 05:56 639234065981939454
69 ms 162.159.25.129
18 2026-08-27 05:39 639234055548642997
23 ms 162.159.25.129
17 2026-08-27 05:21 639234045267979603
23 ms 162.159.25.129
16 2026-08-27 05:04 639234034999717463
2018 ms 162.159.25.129
15 2026-08-27 04:47 639234024739225358
110 ms 162.159.25.129
14 2026-08-27 04:30 639234014311170162
12 ms 162.159.25.129
13 2026-08-27 04:12 639234003806017640
29 ms 162.159.25.129
12 2026-08-27 03:55 639233993356203030
26 ms 162.159.25.129
11 2026-08-27 03:02 639233961301716608
20 ms 162.159.25.129
10 2026-08-27 02:44 639233950834200647
38 ms 162.159.25.129
9 2026-08-27 02:27 639233940431849026
27 ms 162.159.25.129
8 2026-08-27 02:09 639233930110596398
34 ms 162.159.25.129
7 2026-08-27 01:52 639233919705434540
20 ms 162.159.25.129
6 2026-08-27 01:35 639233909452807845
157 ms 162.159.25.129
5 2026-08-27 01:18 639233899096420820
19 ms 162.159.25.129
4 2026-08-27 01:00 639233888707824939
27 ms 162.159.25.129
3 2026-08-27 00:43 639233878461203802
27 ms 162.159.25.129
2 2026-08-27 00:26 639233868060868209
45 ms 162.159.25.129
1 2026-08-27 00:08 639233857450922991
2009 ms 162.159.25.129