DNS response history for ns2.vivashri.in

ns2.vivashri.in 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 40 DNS check records, 40 successful responses, 0 failed responses, and 380 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.vivashri.in.
Records on Selected Date

40

Historical checks stored for this nameserver on selected date

Average Latency

380 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 13:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.50.99.129

Most recently resolved hosting IP on selected date

Successful Responses

40

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.vivashri.in

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
40 2026-08-26 13:05 639233455747096265
297 ms 49.50.99.129
39 2026-08-26 12:47 639233445367152284
147 ms 49.50.99.129
38 2026-08-26 12:30 639233434974187439
137 ms 49.50.99.129
37 2026-08-26 12:13 639233424567558554
3 ms 49.50.99.129
36 2026-08-26 11:55 639233414056832719
4297 ms 49.50.99.129
35 2026-08-26 11:38 639233403515141099
297 ms 49.50.99.129
34 2026-08-26 10:43 639233370841350248
288 ms 49.50.99.129
33 2026-08-26 10:26 639233360361507238
301 ms 49.50.99.129
32 2026-08-26 10:08 639233350067824371
288 ms 49.50.99.129
31 2026-08-26 09:51 639233339545274518
290 ms 49.50.99.129
30 2026-08-26 09:33 639233329214918079
150 ms 49.50.99.129
29 2026-08-26 09:16 639233318749762337
292 ms 49.50.99.129
28 2026-08-26 08:59 639233308387917838
294 ms 49.50.99.129
27 2026-08-26 08:42 639233297961740122
296 ms 49.50.99.129
26 2026-08-26 08:24 639233287487159094
148 ms 49.50.99.129
25 2026-08-26 08:07 639233276995531707
176 ms 49.50.99.129
24 2026-08-26 07:49 639233266521568229
287 ms 49.50.99.129
23 2026-08-26 07:32 639233256081047431
289 ms 49.50.99.129
22 2026-08-26 06:38 639233223620132921
292 ms 49.50.99.129
21 2026-08-26 06:20 639233213287814244
283 ms 49.50.99.129
20 2026-08-26 06:03 639233202925983161
155 ms 49.50.99.129
19 2026-08-26 05:46 639233192644780696
296 ms 49.50.99.129
18 2026-08-26 05:29 639233182401183833
277 ms 49.50.99.129
17 2026-08-26 05:12 639233172074181051
138 ms 49.50.99.129
16 2026-08-26 04:54 639233161808421455
10 ms 49.50.99.129
15 2026-08-26 04:37 639233151357344052
292 ms 49.50.99.129
14 2026-08-26 04:20 639233141034116946
287 ms 49.50.99.129
13 2026-08-26 04:03 639233130828334142
141 ms 49.50.99.129
12 2026-08-26 03:46 639233120373450007
289 ms 49.50.99.129
11 2026-08-26 03:28 639233110066216193
150 ms 49.50.99.129
10 2026-08-26 02:35 639233078065410564
149 ms 49.50.99.129
9 2026-08-26 02:18 639233067787457832
282 ms 49.50.99.129
8 2026-08-26 02:01 639233057501801162
278 ms 49.50.99.129
7 2026-08-26 01:44 639233047089431703
2165 ms 49.50.99.129
6 2026-08-26 01:26 639233036754790688
275 ms 49.50.99.129
5 2026-08-26 01:09 639233026412602472
291 ms 49.50.99.129
4 2026-08-26 00:52 639233016064066127
145 ms 49.50.99.129
3 2026-08-26 00:35 639233005922655772
136 ms 49.50.99.129
2 2026-08-26 00:18 639232995672256907
288 ms 49.50.99.129
1 2026-08-26 00:00 639232985300872416
290 ms 49.50.99.129