DNS response history for ns2.triayurveda.com

ns2.triayurveda.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-25. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 460 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.triayurveda.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

460 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

164.52.195.96

Most recently resolved hosting IP on selected date

Successful Responses

29

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.triayurveda.com

Showing DNS history for 2026-08-25 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
29 2026-08-25 10:03 639232482235303141
308 ms 164.52.195.96
28 2026-08-25 09:45 639232471861770303
307 ms 164.52.195.96
27 2026-08-25 09:28 639232461630217327
313 ms 164.52.195.96
26 2026-08-25 09:11 639232451282965990
304 ms 164.52.195.96
25 2026-08-25 08:53 639232440814614938
154 ms 164.52.195.96
24 2026-08-25 08:36 639232430410720425
150 ms 164.52.195.96
23 2026-08-25 08:19 639232420003096185
2386 ms 164.52.195.96
22 2026-08-25 08:01 639232409467287444
157 ms 164.52.195.96
21 2026-08-25 07:44 639232399077195997
303 ms 164.52.195.96
20 2026-08-25 07:27 639232388731528337
154 ms 164.52.195.96
19 2026-08-25 07:09 639232378288598612
317 ms 164.52.195.96
18 2026-08-25 06:16 639232346196373643
304 ms 164.52.195.96
17 2026-08-25 05:59 639232336112370741
2219 ms 164.52.195.96
16 2026-08-25 05:42 639232326146508970
301 ms 164.52.195.96
15 2026-08-25 05:25 639232316189381720
153 ms 164.52.195.96
14 2026-08-25 05:09 639232306217998913
303 ms 164.52.195.96
13 2026-08-25 04:52 639232296255744174
151 ms 164.52.195.96
12 2026-08-25 04:35 639232286095760789
2161 ms 164.52.195.96
11 2026-08-25 04:18 639232276086186273
306 ms 164.52.195.96
10 2026-08-25 04:02 639232265900986425
313 ms 164.52.195.96
9 2026-08-25 03:45 639232255723518075
305 ms 164.52.195.96
8 2026-08-25 03:28 639232245484452890
305 ms 164.52.195.96
7 2026-08-25 03:11 639232235157175331
303 ms 164.52.195.96
6 2026-08-25 02:17 639232203197189095
151 ms 164.52.195.96
5 2026-08-25 02:00 639232192844564298
304 ms 164.52.195.96
4 2026-08-25 01:43 639232182496008942
150 ms 164.52.195.96
3 2026-08-25 01:26 639232172197053132
309 ms 164.52.195.96
2 2026-08-25 00:32 639232140250307418
146 ms 164.52.195.96
1 2026-08-25 00:15 639232129927860324
300 ms 164.52.195.96