DNS response history for ns2.vaaar.org

ns2.vaaar.org 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 330 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.vaaar.org.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

330 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.191.173.141

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.vaaar.org

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:47 639233414056832719
52 ms 91.191.173.141
34 2026-08-26 11:29 639233403515141099
128 ms 91.191.173.141
33 2026-08-26 10:35 639233370841350248
74 ms 91.191.173.141
32 2026-08-26 10:17 639233360361507238
235 ms 91.191.173.141
31 2026-08-26 10:00 639233350067824371
46 ms 91.191.173.141
30 2026-08-26 09:43 639233339545274518
2053 ms 91.191.173.141
29 2026-08-26 09:26 639233329214918079
75 ms 91.191.173.141
28 2026-08-26 09:08 639233318749762337
216 ms 91.191.173.141
27 2026-08-26 08:51 639233308387917838
50 ms 91.191.173.141
26 2026-08-26 08:33 639233297961740122
56 ms 91.191.173.141
25 2026-08-26 08:16 639233287487159094
93 ms 91.191.173.141
24 2026-08-26 07:59 639233276995531707
53 ms 91.191.173.141
23 2026-08-26 07:41 639233266521568229
63 ms 91.191.173.141
22 2026-08-26 07:24 639233256081047431
2720 ms 91.191.173.141
21 2026-08-26 06:30 639233223620132921
422 ms 91.191.173.141
20 2026-08-26 06:12 639233213287814244
122 ms 91.191.173.141
19 2026-08-26 05:55 639233202925983161
87 ms 91.191.173.141
18 2026-08-26 05:38 639233192644780696
210 ms 91.191.173.141
17 2026-08-26 05:21 639233182401183833
427 ms 91.191.173.141
16 2026-08-26 05:04 639233172074181051
70 ms 91.191.173.141
15 2026-08-26 04:47 639233161808421455
2072 ms 91.191.173.141
14 2026-08-26 04:29 639233151357344052
345 ms 91.191.173.141
13 2026-08-26 04:12 639233141034116946
274 ms 91.191.173.141
12 2026-08-26 03:55 639233130828334142
59 ms 91.191.173.141
11 2026-08-26 03:38 639233120373450007
98 ms 91.191.173.141
10 2026-08-26 03:20 639233110066216193
64 ms 91.191.173.141
9 2026-08-26 02:27 639233078065410564
112 ms 91.191.173.141
8 2026-08-26 02:10 639233067787457832
425 ms 91.191.173.141
7 2026-08-26 01:53 639233057501801162
67 ms 91.191.173.141
6 2026-08-26 01:35 639233047089431703
38 ms 91.191.173.141
5 2026-08-26 01:18 639233036754790688
68 ms 91.191.173.141
4 2026-08-26 01:01 639233026412602472
143 ms 91.191.173.141
3 2026-08-26 00:44 639233016064066127
341 ms 91.191.173.141
2 2026-08-26 00:27 639233005922655772
119 ms 91.191.173.141
1 2026-08-26 00:10 639232995672256907
75 ms 91.191.173.141