DNS response history for ns2.av2m.com

ns2.av2m.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-31. For this date, NameServerHistory found 37 DNS check records, 37 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.av2m.com.
Records on Selected Date

37

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-31 12:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.54.126.51

Most recently resolved hosting IP on selected date

Successful Responses

37

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

Showing DNS history for 2026-08-31 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
37 2026-08-31 12:13 639237742927117371
322 ms 198.54.126.51
36 2026-08-31 11:56 639237732538256235
307 ms 198.54.126.51
35 2026-08-31 11:38 639237722025682013
342 ms 198.54.126.51
34 2026-08-31 11:21 639237711568720101
330 ms 198.54.126.51
33 2026-08-31 11:03 639237701119461876
312 ms 198.54.126.51
32 2026-08-31 10:46 639237690759595513
3 ms 198.54.126.51
31 2026-08-31 10:29 639237680122296836
315 ms 198.54.126.51
30 2026-08-31 09:35 639237647999458954
308 ms 198.54.126.51
29 2026-08-31 09:18 639237637680951774
348 ms 198.54.126.51
28 2026-08-31 09:00 639237627437728712
312 ms 198.54.126.51
27 2026-08-31 08:43 639237617127808241
4 ms 198.54.126.51
26 2026-08-31 08:26 639237606990101394
363 ms 198.54.126.51
25 2026-08-31 08:09 639237596595480036
313 ms 198.54.126.51
24 2026-08-31 07:52 639237586261012001
309 ms 198.54.126.51
23 2026-08-31 07:35 639237576047657695
3 ms 198.54.126.51
22 2026-08-31 07:18 639237565832936443
314 ms 198.54.126.51
21 2026-08-31 07:01 639237555466329546
302 ms 198.54.126.51
20 2026-08-31 06:43 639237545032411072
311 ms 198.54.126.51
19 2026-08-31 06:26 639237534469438634
300 ms 198.54.126.51
18 2026-08-31 05:32 639237502279296801
280 ms 198.54.126.51
17 2026-08-31 05:15 639237492362730124
2 ms 198.54.126.51
16 2026-08-31 04:58 639237482311584319
294 ms 198.54.126.51
15 2026-08-31 04:41 639237472150685594
322 ms 198.54.126.51
14 2026-08-31 04:24 639237462055295430
326 ms 198.54.126.51
13 2026-08-31 04:08 639237452089913890
318 ms 198.54.126.51
12 2026-08-31 03:51 639237441972654103
2 ms 198.54.126.51
11 2026-08-31 03:34 639237432052396478
308 ms 198.54.126.51
10 2026-08-31 03:18 639237422012990851
2 ms 198.54.126.51
9 2026-08-31 03:01 639237411889602012
327 ms 198.54.126.51
8 2026-08-31 02:44 639237401637354221
304 ms 198.54.126.51
7 2026-08-31 02:27 639237391412690360
325 ms 198.54.126.51
6 2026-08-31 01:34 639237359972957132
2 ms 198.54.126.51
5 2026-08-31 01:18 639237350032183979
296 ms 198.54.126.51
4 2026-08-31 01:01 639237340111452066
327 ms 198.54.126.51
3 2026-08-31 00:44 639237329967272514
14 ms 198.54.126.51
2 2026-08-31 00:28 639237319916508151
292 ms 198.54.126.51
1 2026-08-31 00:11 639237309944877243
296 ms 198.54.126.51