DNS response history for ns2.diyview.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

270 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.54.116.140

Most recently resolved hosting IP on selected date

Successful Responses

36

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.diyview.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
36 2026-08-24 15:21 639231807961539652
32 ms 198.54.116.140
35 2026-08-24 15:04 639231797631669865
304 ms 198.54.116.140
34 2026-08-24 14:11 639231765923559455
316 ms 198.54.116.140
33 2026-08-24 13:54 639231755868832964
339 ms 198.54.116.140
32 2026-08-24 13:37 639231745628278877
214 ms 198.54.116.140
31 2026-08-24 13:20 639231735407682062
307 ms 198.54.116.140
30 2026-08-24 12:27 639231703815441688
10 ms 198.54.116.140
29 2026-08-24 12:10 639231693747052549
298 ms 198.54.116.140
28 2026-08-24 11:54 639231683712487276
319 ms 198.54.116.140
27 2026-08-24 11:37 639231673513573868
302 ms 198.54.116.140
26 2026-08-24 10:43 639231641791249939
323 ms 198.54.116.140
25 2026-08-24 10:27 639231631866211033
11 ms 198.54.116.140
24 2026-08-24 10:10 639231621644955316
295 ms 198.54.116.140
23 2026-08-24 09:53 639231611478799259
165 ms 198.54.116.140
22 2026-08-24 09:01 639231579923718211
306 ms 198.54.116.140
21 2026-08-24 08:44 639231569810702936
367 ms 198.54.116.140
20 2026-08-24 08:27 639231559762411619
174 ms 198.54.116.140
19 2026-08-24 08:10 639231549663595407
308 ms 198.54.116.140
18 2026-08-24 07:17 639231518076817246
305 ms 198.54.116.140
17 2026-08-24 07:01 639231508078650885
319 ms 198.54.116.140
16 2026-08-24 06:44 639231498210697093
4 ms 198.54.116.140
15 2026-08-24 06:28 639231488109699360
4 ms 198.54.116.140
14 2026-08-24 05:35 639231456772510692
18 ms 198.54.116.140
13 2026-08-24 05:19 639231447084631185
305 ms 198.54.116.140
12 2026-08-24 05:03 639231437208519473
308 ms 198.54.116.140
11 2026-08-24 04:46 639231427209627490
317 ms 198.54.116.140
10 2026-08-24 03:53 639231395791246644
187 ms 198.54.116.140
9 2026-08-24 03:37 639231386075551458
311 ms 198.54.116.140
8 2026-08-24 03:21 639231376208713791
12 ms 198.54.116.140
7 2026-08-24 03:04 639231366170589276
159 ms 198.54.116.140
6 2026-08-24 02:12 639231334732159368
299 ms 198.54.116.140
5 2026-08-24 01:56 639231325035670078
4 ms 198.54.116.140
4 2026-08-24 01:39 639231315132253837
294 ms 198.54.116.140
3 2026-08-24 01:23 639231305014280808
294 ms 198.54.116.140
2 2026-08-24 00:30 639231273779380675
2 ms 198.54.116.140
1 2026-08-24 00:14 639231264180839154
2185 ms 198.54.116.140