DNS response history for ns2.srivignavellmatrimony.com

ns2.srivignavellmatrimony.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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 286 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.srivignavellmatrimony.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

286 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.38.87.139

Most recently resolved hosting IP on selected date

Successful Responses

34

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

Showing DNS history for 2026-08-24 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
34 2026-08-24 14:06 639231765923559455
145 ms 198.38.87.139
33 2026-08-24 13:49 639231755868832964
301 ms 198.38.87.139
32 2026-08-24 13:32 639231745628278877
2280 ms 198.38.87.139
31 2026-08-24 13:15 639231735407682062
286 ms 198.38.87.139
30 2026-08-24 12:22 639231703815441688
289 ms 198.38.87.139
29 2026-08-24 12:06 639231693747052549
293 ms 198.38.87.139
28 2026-08-24 11:49 639231683712487276
377 ms 198.38.87.139
27 2026-08-24 11:32 639231673513573868
3 ms 198.38.87.139
26 2026-08-24 10:39 639231641791249939
144 ms 198.38.87.139
25 2026-08-24 10:22 639231631866211033
283 ms 198.38.87.139
24 2026-08-24 10:06 639231621644955316
281 ms 198.38.87.139
23 2026-08-24 09:49 639231611478799259
3 ms 198.38.87.139
22 2026-08-24 08:56 639231579923718211
7 ms 198.38.87.139
21 2026-08-24 08:39 639231569810702936
320 ms 198.38.87.139
20 2026-08-24 08:22 639231559762411619
157 ms 198.38.87.139
19 2026-08-24 08:05 639231549663595407
6 ms 198.38.87.139
18 2026-08-24 07:13 639231518076817246
275 ms 198.38.87.139
17 2026-08-24 06:56 639231508078650885
128 ms 198.38.87.139
16 2026-08-24 06:40 639231498210697093
5 ms 198.38.87.139
15 2026-08-24 06:23 639231488109699360
3 ms 198.38.87.139
14 2026-08-24 05:31 639231456772510692
322 ms 198.38.87.139
13 2026-08-24 05:15 639231447084631185
7 ms 198.38.87.139
12 2026-08-24 04:58 639231437208519473
3 ms 198.38.87.139
11 2026-08-24 04:41 639231427209627490
4 ms 198.38.87.139
10 2026-08-24 03:49 639231395791246644
274 ms 198.38.87.139
9 2026-08-24 03:33 639231386075551458
274 ms 198.38.87.139
8 2026-08-24 03:17 639231376208713791
2184 ms 198.38.87.139
7 2026-08-24 03:00 639231366170589276
3 ms 198.38.87.139
6 2026-08-24 02:07 639231334732159368
271 ms 198.38.87.139
5 2026-08-24 01:51 639231325035670078
4 ms 198.38.87.139
4 2026-08-24 01:35 639231315132253837
218 ms 198.38.87.139
3 2026-08-24 01:18 639231305014280808
132 ms 198.38.87.139
2 2026-08-24 00:26 639231273779380675
263 ms 198.38.87.139
1 2026-08-24 00:10 639231264180839154
168 ms 198.38.87.139