DNS response history for ns3.avgmt.com

ns3.avgmt.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-26. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 375 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 ns3.avgmt.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

375 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

184.168.126.247

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns3.avgmt.com

Showing DNS history for 2026-08-26 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
29 2026-08-26 09:30 639233329214918079
335 ms 184.168.126.247
28 2026-08-26 09:12 639233318749762337
4 ms 184.168.126.247
27 2026-08-26 08:55 639233308387917838
7 ms 184.168.126.247
26 2026-08-26 08:38 639233297961740122
324 ms 184.168.126.247
25 2026-08-26 08:20 639233287487159094
326 ms 184.168.126.247
24 2026-08-26 08:03 639233276995531707
308 ms 184.168.126.247
23 2026-08-26 07:45 639233266521568229
336 ms 184.168.126.247
22 2026-08-26 07:28 639233256081047431
323 ms 184.168.126.247
21 2026-08-26 06:34 639233223620132921
4182 ms 184.168.126.247
20 2026-08-26 06:17 639233213287814244
325 ms 184.168.126.247
19 2026-08-26 05:59 639233202925983161
324 ms 184.168.126.247
18 2026-08-26 05:42 639233192644780696
13 ms 184.168.126.247
17 2026-08-26 05:25 639233182401183833
3 ms 184.168.126.247
16 2026-08-26 05:08 639233172074181051
2 ms 184.168.126.247
15 2026-08-26 04:51 639233161808421455
170 ms 184.168.126.247
14 2026-08-26 04:33 639233151357344052
3 ms 184.168.126.247
13 2026-08-26 04:16 639233141034116946
9 ms 184.168.126.247
12 2026-08-26 03:59 639233130828334142
11 ms 184.168.126.247
11 2026-08-26 03:42 639233120373450007
165 ms 184.168.126.247
10 2026-08-26 03:24 639233110066216193
26 ms 184.168.126.247
9 2026-08-26 02:31 639233078065410564
326 ms 184.168.126.247
8 2026-08-26 02:14 639233067787457832
9 ms 184.168.126.247
7 2026-08-26 01:57 639233057501801162
331 ms 184.168.126.247
6 2026-08-26 01:40 639233047089431703
5 ms 184.168.126.247
5 2026-08-26 01:22 639233036754790688
2322 ms 184.168.126.247
4 2026-08-26 01:05 639233026412602472
2 ms 184.168.126.247
3 2026-08-26 00:48 639233016064066127
9 ms 184.168.126.247
2 2026-08-26 00:31 639233005922655772
322 ms 184.168.126.247
1 2026-08-26 00:14 639232995672256907
339 ms 184.168.126.247