DNS response history for ns2.vismtech.com

ns2.vismtech.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 285 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.vismtech.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

285 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.214.130.228

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.vismtech.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:39 639233370841350248
165 ms 162.214.130.228
32 2026-08-26 10:22 639233360361507238
172 ms 162.214.130.228
31 2026-08-26 10:05 639233350067824371
292 ms 162.214.130.228
30 2026-08-26 09:48 639233339545274518
296 ms 162.214.130.228
29 2026-08-26 09:30 639233329214918079
32 ms 162.214.130.228
28 2026-08-26 09:13 639233318749762337
163 ms 162.214.130.228
27 2026-08-26 08:56 639233308387917838
320 ms 162.214.130.228
26 2026-08-26 08:38 639233297961740122
322 ms 162.214.130.228
25 2026-08-26 08:21 639233287487159094
333 ms 162.214.130.228
24 2026-08-26 08:03 639233276995531707
314 ms 162.214.130.228
23 2026-08-26 07:46 639233266521568229
258 ms 162.214.130.228
22 2026-08-26 07:28 639233256081047431
178 ms 162.214.130.228
21 2026-08-26 06:34 639233223620132921
291 ms 162.214.130.228
20 2026-08-26 06:17 639233213287814244
2022 ms 162.214.130.228
19 2026-08-26 06:00 639233202925983161
289 ms 162.214.130.228
18 2026-08-26 05:42 639233192644780696
10 ms 162.214.130.228
17 2026-08-26 05:25 639233182401183833
4 ms 162.214.130.228
16 2026-08-26 05:08 639233172074181051
4 ms 162.214.130.228
15 2026-08-26 04:51 639233161808421455
290 ms 162.214.130.228
14 2026-08-26 04:34 639233151357344052
304 ms 162.214.130.228
13 2026-08-26 04:17 639233141034116946
289 ms 162.214.130.228
12 2026-08-26 03:59 639233130828334142
291 ms 162.214.130.228
11 2026-08-26 03:42 639233120373450007
12 ms 162.214.130.228
10 2026-08-26 03:25 639233110066216193
147 ms 162.214.130.228
9 2026-08-26 02:32 639233078065410564
288 ms 162.214.130.228
8 2026-08-26 02:14 639233067787457832
289 ms 162.214.130.228
7 2026-08-26 01:57 639233057501801162
391 ms 162.214.130.228
6 2026-08-26 01:40 639233047089431703
290 ms 162.214.130.228
5 2026-08-26 01:23 639233036754790688
301 ms 162.214.130.228
4 2026-08-26 01:06 639233026412602472
292 ms 162.214.130.228
3 2026-08-26 00:48 639233016064066127
293 ms 162.214.130.228
2 2026-08-26 00:31 639233005922655772
290 ms 162.214.130.228
1 2026-08-26 00:14 639232995672256907
167 ms 162.214.130.228