DNS response history for ns2.boyrikyu.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

697 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.79.177.24

Most recently resolved hosting IP on selected date

Successful Responses

31

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.boyrikyu.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
31 2026-08-25 10:22 639232492740373468
887 ms 51.79.177.24
30 2026-08-25 10:05 639232482235303141
887 ms 51.79.177.24
29 2026-08-25 09:47 639232471861770303
802 ms 51.79.177.24
28 2026-08-25 09:30 639232461630217327
410 ms 51.79.177.24
27 2026-08-25 09:13 639232451282965990
885 ms 51.79.177.24
26 2026-08-25 08:56 639232440814614938
883 ms 51.79.177.24
25 2026-08-25 08:38 639232430410720425
799 ms 51.79.177.24
24 2026-08-25 08:21 639232420003096185
918 ms 51.79.177.24
23 2026-08-25 08:04 639232409467287444
798 ms 51.79.177.24
22 2026-08-25 07:46 639232399077195997
325 ms 51.79.177.24
21 2026-08-25 07:29 639232388731528337
415 ms 51.79.177.24
20 2026-08-25 07:12 639232378288598612
411 ms 51.79.177.24
19 2026-08-25 06:18 639232346196373643
317 ms 51.79.177.24
18 2026-08-25 06:01 639232336112370741
326 ms 51.79.177.24
17 2026-08-25 05:44 639232326146508970
738 ms 51.79.177.24
16 2026-08-25 05:28 639232316189381720
801 ms 51.79.177.24
15 2026-08-25 05:11 639232306217998913
396 ms 51.79.177.24
14 2026-08-25 04:54 639232296255744174
326 ms 51.79.177.24
13 2026-08-25 04:38 639232286095760789
824 ms 51.79.177.24
12 2026-08-25 04:21 639232276086186273
788 ms 51.79.177.24
11 2026-08-25 04:04 639232265900986425
868 ms 51.79.177.24
10 2026-08-25 03:47 639232255723518075
788 ms 51.79.177.24
9 2026-08-25 03:30 639232245484452890
322 ms 51.79.177.24
8 2026-08-25 03:13 639232235157175331
791 ms 51.79.177.24
7 2026-08-25 02:20 639232203197189095
970 ms 51.79.177.24
6 2026-08-25 02:03 639232192844564298
801 ms 51.79.177.24
5 2026-08-25 01:45 639232182496008942
788 ms 51.79.177.24
4 2026-08-25 01:28 639232172197053132
784 ms 51.79.177.24
3 2026-08-25 00:34 639232140250307418
871 ms 51.79.177.24
2 2026-08-25 00:18 639232129927860324
791 ms 51.79.177.24
1 2026-08-25 00:00 639232119551972438
889 ms 51.79.177.24