DNS response history for ns2.visamtech.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

439 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.96.180.127

Most recently resolved hosting IP on selected date

Successful Responses

33

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.visamtech.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
33 2026-08-26 10:27 639233360361507238
335 ms 172.96.180.127
32 2026-08-26 10:10 639233350067824371
330 ms 172.96.180.127
31 2026-08-26 09:53 639233339545274518
323 ms 172.96.180.127
30 2026-08-26 09:35 639233329214918079
167 ms 172.96.180.127
29 2026-08-26 09:18 639233318749762337
163 ms 172.96.180.127
28 2026-08-26 09:01 639233308387917838
287 ms 172.96.180.127
27 2026-08-26 08:43 639233297961740122
166 ms 172.96.180.127
26 2026-08-26 08:26 639233287487159094
329 ms 172.96.180.127
25 2026-08-26 08:09 639233276995531707
346 ms 172.96.180.127
24 2026-08-26 07:51 639233266521568229
163 ms 172.96.180.127
23 2026-08-26 07:33 639233256081047431
332 ms 172.96.180.127
22 2026-08-26 06:39 639233223620132921
338 ms 172.96.180.127
21 2026-08-26 06:22 639233213287814244
331 ms 172.96.180.127
20 2026-08-26 06:05 639233202925983161
3669 ms 172.96.180.127
19 2026-08-26 05:48 639233192644780696
2158 ms 172.96.180.127
18 2026-08-26 05:30 639233182401183833
321 ms 172.96.180.127
17 2026-08-26 05:13 639233172074181051
328 ms 172.96.180.127
16 2026-08-26 04:56 639233161808421455
164 ms 172.96.180.127
15 2026-08-26 04:39 639233151357344052
329 ms 172.96.180.127
14 2026-08-26 04:22 639233141034116946
172 ms 172.96.180.127
13 2026-08-26 04:04 639233130828334142
328 ms 172.96.180.127
12 2026-08-26 03:47 639233120373450007
162 ms 172.96.180.127
11 2026-08-26 03:30 639233110066216193
327 ms 172.96.180.127
10 2026-08-26 02:37 639233078065410564
340 ms 172.96.180.127
9 2026-08-26 02:20 639233067787457832
327 ms 172.96.180.127
8 2026-08-26 02:02 639233057501801162
327 ms 172.96.180.127
7 2026-08-26 01:45 639233047089431703
277 ms 172.96.180.127
6 2026-08-26 01:28 639233036754790688
328 ms 172.96.180.127
5 2026-08-26 01:11 639233026412602472
322 ms 172.96.180.127
4 2026-08-26 00:53 639233016064066127
325 ms 172.96.180.127
3 2026-08-26 00:36 639233005922655772
163 ms 172.96.180.127
2 2026-08-26 00:19 639232995672256907
167 ms 172.96.180.127
1 2026-08-26 00:02 639232985300872416
329 ms 172.96.180.127