DNS response history for ns2.veerotech.net

ns2.veerotech.net 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 36 DNS check records, 36 successful responses, 0 failed responses, and 190 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.veerotech.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

190 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.69.112.200

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.veerotech.net

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
36 2026-08-26 12:03 639233424567558554
10 ms 158.69.112.200
35 2026-08-26 11:46 639233414056832719
29 ms 158.69.112.200
34 2026-08-26 11:28 639233403515141099
6 ms 158.69.112.200
33 2026-08-26 10:34 639233370841350248
7 ms 158.69.112.200
32 2026-08-26 10:16 639233360361507238
33 ms 158.69.112.200
31 2026-08-26 09:59 639233350067824371
19 ms 158.69.112.200
30 2026-08-26 09:42 639233339545274518
21 ms 158.69.112.200
29 2026-08-26 09:24 639233329214918079
35 ms 158.69.112.200
28 2026-08-26 09:07 639233318749762337
18 ms 158.69.112.200
27 2026-08-26 08:50 639233308387917838
7 ms 158.69.112.200
26 2026-08-26 08:32 639233297961740122
7 ms 158.69.112.200
25 2026-08-26 08:15 639233287487159094
23 ms 158.69.112.200
24 2026-08-26 07:57 639233276995531707
8 ms 158.69.112.200
23 2026-08-26 07:40 639233266521568229
40 ms 158.69.112.200
22 2026-08-26 07:23 639233256081047431
58 ms 158.69.112.200
21 2026-08-26 06:28 639233223620132921
42 ms 158.69.112.200
20 2026-08-26 06:11 639233213287814244
7 ms 158.69.112.200
19 2026-08-26 05:54 639233202925983161
2019 ms 158.69.112.200
18 2026-08-26 05:37 639233192644780696
2026 ms 158.69.112.200
17 2026-08-26 05:20 639233182401183833
18 ms 158.69.112.200
16 2026-08-26 05:03 639233172074181051
19 ms 158.69.112.200
15 2026-08-26 04:45 639233161808421455
15 ms 158.69.112.200
14 2026-08-26 04:28 639233151357344052
2044 ms 158.69.112.200
13 2026-08-26 04:11 639233141034116946
5 ms 158.69.112.200
12 2026-08-26 03:54 639233130828334142
32 ms 158.69.112.200
11 2026-08-26 03:36 639233120373450007
16 ms 158.69.112.200
10 2026-08-26 03:19 639233110066216193
59 ms 158.69.112.200
9 2026-08-26 02:26 639233078065410564
34 ms 158.69.112.200
8 2026-08-26 02:09 639233067787457832
8 ms 158.69.112.200
7 2026-08-26 01:52 639233057501801162
18 ms 158.69.112.200
6 2026-08-26 01:34 639233047089431703
30 ms 158.69.112.200
5 2026-08-26 01:17 639233036754790688
6 ms 158.69.112.200
4 2026-08-26 01:00 639233026412602472
21 ms 158.69.112.200
3 2026-08-26 00:42 639233016064066127
22 ms 158.69.112.200
2 2026-08-26 00:26 639233005922655772
55 ms 158.69.112.200
1 2026-08-26 00:09 639232995672256907
20 ms 158.69.112.200