DNS response history for ns2.vrtech-hk.com

ns2.vrtech-hk.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 36 DNS check records, 36 successful responses, 0 failed responses, and 316 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.vrtech-hk.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

316 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.64.97.6

Most recently resolved hosting IP on selected date

Successful Responses

36

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.vrtech-hk.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
36 2026-08-24 15:20 639231807961539652
378 ms 202.64.97.6
35 2026-08-24 15:03 639231797631669865
3 ms 202.64.97.6
34 2026-08-24 14:10 639231765923559455
375 ms 202.64.97.6
33 2026-08-24 13:53 639231755868832964
374 ms 202.64.97.6
32 2026-08-24 13:36 639231745628278877
378 ms 202.64.97.6
31 2026-08-24 13:19 639231735407682062
375 ms 202.64.97.6
30 2026-08-24 12:26 639231703815441688
3 ms 202.64.97.6
29 2026-08-24 12:10 639231693747052549
387 ms 202.64.97.6
28 2026-08-24 11:53 639231683712487276
381 ms 202.64.97.6
27 2026-08-24 11:36 639231673513573868
4 ms 202.64.97.6
26 2026-08-24 10:43 639231641791249939
382 ms 202.64.97.6
25 2026-08-24 10:26 639231631866211033
189 ms 202.64.97.6
24 2026-08-24 10:09 639231621644955316
388 ms 202.64.97.6
23 2026-08-24 09:52 639231611478799259
3 ms 202.64.97.6
22 2026-08-24 09:00 639231579923718211
402 ms 202.64.97.6
21 2026-08-24 08:43 639231569810702936
191 ms 202.64.97.6
20 2026-08-24 08:26 639231559762411619
190 ms 202.64.97.6
19 2026-08-24 08:09 639231549663595407
378 ms 202.64.97.6
18 2026-08-24 07:16 639231518076817246
388 ms 202.64.97.6
17 2026-08-24 07:00 639231508078650885
381 ms 202.64.97.6
16 2026-08-24 06:43 639231498210697093
3 ms 202.64.97.6
15 2026-08-24 06:27 639231488109699360
381 ms 202.64.97.6
14 2026-08-24 05:35 639231456772510692
387 ms 202.64.97.6
13 2026-08-24 05:18 639231447084631185
381 ms 202.64.97.6
12 2026-08-24 05:02 639231437208519473
375 ms 202.64.97.6
11 2026-08-24 04:45 639231427209627490
2 ms 202.64.97.6
10 2026-08-24 03:52 639231395791246644
222 ms 202.64.97.6
9 2026-08-24 03:37 639231386075551458
382 ms 202.64.97.6
8 2026-08-24 03:20 639231376208713791
963 ms 202.64.97.6
7 2026-08-24 03:04 639231366170589276
2 ms 202.64.97.6
6 2026-08-24 02:11 639231334732159368
407 ms 202.64.97.6
5 2026-08-24 01:55 639231325035670078
2 ms 202.64.97.6
4 2026-08-24 01:38 639231315132253837
200 ms 202.64.97.6
3 2026-08-24 01:22 639231305014280808
957 ms 202.64.97.6
2 2026-08-24 00:29 639231273779380675
771 ms 202.64.97.6
1 2026-08-24 00:13 639231264180839154
387 ms 202.64.97.6