DNS response history for ns2.veernxt.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

396 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.120.176.233

Most recently resolved hosting IP on selected date

Successful Responses

35

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.veernxt.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
35 2026-08-26 11:54 639233414056832719
280 ms 103.120.176.233
34 2026-08-26 11:36 639233403515141099
277 ms 103.120.176.233
33 2026-08-26 10:41 639233370841350248
146 ms 103.120.176.233
32 2026-08-26 10:24 639233360361507238
268 ms 103.120.176.233
31 2026-08-26 10:07 639233350067824371
261 ms 103.120.176.233
30 2026-08-26 09:50 639233339545274518
261 ms 103.120.176.233
29 2026-08-26 09:32 639233329214918079
280 ms 103.120.176.233
28 2026-08-26 09:15 639233318749762337
265 ms 103.120.176.233
27 2026-08-26 08:57 639233308387917838
143 ms 103.120.176.233
26 2026-08-26 08:40 639233297961740122
275 ms 103.120.176.233
25 2026-08-26 08:23 639233287487159094
286 ms 103.120.176.233
24 2026-08-26 08:05 639233276995531707
145 ms 103.120.176.233
23 2026-08-26 07:48 639233266521568229
261 ms 103.120.176.233
22 2026-08-26 07:30 639233256081047431
282 ms 103.120.176.233
21 2026-08-26 06:36 639233223620132921
133 ms 103.120.176.233
20 2026-08-26 06:19 639233213287814244
286 ms 103.120.176.233
19 2026-08-26 06:02 639233202925983161
132 ms 103.120.176.233
18 2026-08-26 05:44 639233192644780696
277 ms 103.120.176.233
17 2026-08-26 05:27 639233182401183833
283 ms 103.120.176.233
16 2026-08-26 05:10 639233172074181051
172 ms 103.120.176.233
15 2026-08-26 04:53 639233161808421455
135 ms 103.120.176.233
14 2026-08-26 04:36 639233151357344052
142 ms 103.120.176.233
13 2026-08-26 04:18 639233141034116946
152 ms 103.120.176.233
12 2026-08-26 04:01 639233130828334142
2135 ms 103.120.176.233
11 2026-08-26 03:44 639233120373450007
269 ms 103.120.176.233
10 2026-08-26 03:27 639233110066216193
2143 ms 103.120.176.233
9 2026-08-26 02:34 639233078065410564
271 ms 103.120.176.233
8 2026-08-26 02:16 639233067787457832
265 ms 103.120.176.233
7 2026-08-26 01:59 639233057501801162
275 ms 103.120.176.233
6 2026-08-26 01:42 639233047089431703
262 ms 103.120.176.233
5 2026-08-26 01:25 639233036754790688
276 ms 103.120.176.233
4 2026-08-26 01:08 639233026412602472
128 ms 103.120.176.233
3 2026-08-26 00:50 639233016064066127
2233 ms 103.120.176.233
2 2026-08-26 00:33 639233005922655772
169 ms 103.120.176.233
1 2026-08-26 00:16 639232995672256907
279 ms 103.120.176.233