DNS response history for ns2.apexwebmarketing.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

247 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

131.153.102.225

Most recently resolved hosting IP on selected date

Successful Responses

28

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.apexwebmarketing.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
28 2026-08-25 09:42 639232471861770303
189 ms 131.153.102.225
27 2026-08-25 09:25 639232461630217327
180 ms 131.153.102.225
26 2026-08-25 09:08 639232451282965990
91 ms 131.153.102.225
25 2026-08-25 08:50 639232440814614938
98 ms 131.153.102.225
24 2026-08-25 08:33 639232430410720425
181 ms 131.153.102.225
23 2026-08-25 08:16 639232420003096185
733 ms 131.153.102.225
22 2026-08-25 07:58 639232409467287444
180 ms 131.153.102.225
21 2026-08-25 07:41 639232399077195997
33 ms 131.153.102.225
20 2026-08-25 07:24 639232388731528337
207 ms 131.153.102.225
19 2026-08-25 07:06 639232378288598612
190 ms 131.153.102.225
18 2026-08-25 06:13 639232346196373643
117 ms 131.153.102.225
17 2026-08-25 05:56 639232336112370741
189 ms 131.153.102.225
16 2026-08-25 05:39 639232326146508970
112 ms 131.153.102.225
15 2026-08-25 05:23 639232316189381720
181 ms 131.153.102.225
14 2026-08-25 05:06 639232306217998913
110 ms 131.153.102.225
13 2026-08-25 04:49 639232296255744174
228 ms 131.153.102.225
12 2026-08-25 04:33 639232286095760789
176 ms 131.153.102.225
11 2026-08-25 04:16 639232276086186273
199 ms 131.153.102.225
10 2026-08-25 03:59 639232265900986425
89 ms 131.153.102.225
9 2026-08-25 03:42 639232255723518075
91 ms 131.153.102.225
8 2026-08-25 03:25 639232245484452890
179 ms 131.153.102.225
7 2026-08-25 03:08 639232235157175331
110 ms 131.153.102.225
6 2026-08-25 02:14 639232203197189095
2226 ms 131.153.102.225
5 2026-08-25 01:57 639232192844564298
177 ms 131.153.102.225
4 2026-08-25 01:40 639232182496008942
88 ms 131.153.102.225
3 2026-08-25 01:23 639232172197053132
221 ms 131.153.102.225
2 2026-08-25 00:29 639232140250307418
134 ms 131.153.102.225
1 2026-08-25 00:12 639232129927860324
194 ms 131.153.102.225