DNS response history for ns2.nmadvertiser.com

ns2.nmadvertiser.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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 212 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.nmadvertiser.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

212 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.116.205.193

Most recently resolved hosting IP on selected date

Successful Responses

34

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.nmadvertiser.com

Showing DNS history for 2026-08-24 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
34 2026-08-24 14:09 639231765923559455
246 ms 66.116.205.193
33 2026-08-24 13:52 639231755868832964
6 ms 66.116.205.193
32 2026-08-24 13:35 639231745628278877
149 ms 66.116.205.193
31 2026-08-24 13:18 639231735407682062
4 ms 66.116.205.193
30 2026-08-24 12:25 639231703815441688
3 ms 66.116.205.193
29 2026-08-24 12:09 639231693747052549
274 ms 66.116.205.193
28 2026-08-24 11:52 639231683712487276
7 ms 66.116.205.193
27 2026-08-24 11:35 639231673513573868
264 ms 66.116.205.193
26 2026-08-24 10:42 639231641791249939
251 ms 66.116.205.193
25 2026-08-24 10:25 639231631866211033
246 ms 66.116.205.193
24 2026-08-24 10:09 639231621644955316
257 ms 66.116.205.193
23 2026-08-24 09:52 639231611478799259
4 ms 66.116.205.193
22 2026-08-24 08:59 639231579923718211
5 ms 66.116.205.193
21 2026-08-24 08:42 639231569810702936
263 ms 66.116.205.193
20 2026-08-24 08:25 639231559762411619
263 ms 66.116.205.193
19 2026-08-24 08:08 639231549663595407
258 ms 66.116.205.193
18 2026-08-24 07:16 639231518076817246
270 ms 66.116.205.193
17 2026-08-24 06:59 639231508078650885
263 ms 66.116.205.193
16 2026-08-24 06:43 639231498210697093
2 ms 66.116.205.193
15 2026-08-24 06:26 639231488109699360
4 ms 66.116.205.193
14 2026-08-24 05:34 639231456772510692
153 ms 66.116.205.193
13 2026-08-24 05:17 639231447084631185
3 ms 66.116.205.193
12 2026-08-24 05:01 639231437208519473
249 ms 66.116.205.193
11 2026-08-24 04:44 639231427209627490
249 ms 66.116.205.193
10 2026-08-24 03:52 639231395791246644
3 ms 66.116.205.193
9 2026-08-24 03:36 639231386075551458
2 ms 66.116.205.193
8 2026-08-24 03:19 639231376208713791
2 ms 66.116.205.193
7 2026-08-24 03:03 639231366170589276
2382 ms 66.116.205.193
6 2026-08-24 02:10 639231334732159368
254 ms 66.116.205.193
5 2026-08-24 01:54 639231325035670078
237 ms 66.116.205.193
4 2026-08-24 01:38 639231315132253837
126 ms 66.116.205.193
3 2026-08-24 01:21 639231305014280808
126 ms 66.116.205.193
2 2026-08-24 00:28 639231273779380675
130 ms 66.116.205.193
1 2026-08-24 00:13 639231264180839154
250 ms 66.116.205.193