DNS response history for ns2.apex-tek.com

ns2.apex-tek.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-25. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 211 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.apex-tek.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

211 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.24.60

Most recently resolved hosting IP on selected date

Successful Responses

26

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.apex-tek.com

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
26 2026-08-25 09:05 639232451282965990
47 ms 162.159.24.60
25 2026-08-25 08:48 639232440814614938
26 ms 162.159.24.60
24 2026-08-25 08:30 639232430410720425
57 ms 162.159.24.60
23 2026-08-25 08:13 639232420003096185
136 ms 162.159.24.60
22 2026-08-25 07:56 639232409467287444
158 ms 162.159.24.60
21 2026-08-25 07:38 639232399077195997
49 ms 162.159.24.60
20 2026-08-25 07:21 639232388731528337
2130 ms 162.159.24.60
19 2026-08-25 07:04 639232378288598612
62 ms 162.159.24.60
18 2026-08-25 06:10 639232346196373643
4 ms 162.159.24.60
17 2026-08-25 05:53 639232336112370741
8 ms 162.159.24.60
16 2026-08-25 05:37 639232326146508970
53 ms 162.159.24.60
15 2026-08-25 05:20 639232316189381720
33 ms 162.159.24.60
14 2026-08-25 05:04 639232306217998913
44 ms 162.159.24.60
13 2026-08-25 04:47 639232296255744174
53 ms 162.159.24.60
12 2026-08-25 04:30 639232286095760789
70 ms 162.159.24.60
11 2026-08-25 04:13 639232276086186273
26 ms 162.159.24.60
10 2026-08-25 03:56 639232265900986425
45 ms 162.159.24.60
9 2026-08-25 03:39 639232255723518075
34 ms 162.159.24.60
8 2026-08-25 03:22 639232245484452890
47 ms 162.159.24.60
7 2026-08-25 03:05 639232235157175331
44 ms 162.159.24.60
6 2026-08-25 02:12 639232203197189095
178 ms 162.159.24.60
5 2026-08-25 01:55 639232192844564298
2009 ms 162.159.24.60
4 2026-08-25 01:37 639232182496008942
59 ms 162.159.24.60
3 2026-08-25 01:20 639232172197053132
23 ms 162.159.24.60
2 2026-08-25 00:27 639232140250307418
50 ms 162.159.24.60
1 2026-08-25 00:10 639232129927860324
37 ms 162.159.24.60