DNS response history for ns1.boyslove.tokyo

ns1.boyslove.tokyo 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 30 DNS check records, 30 successful responses, 0 failed responses, and 348 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 ns1.boyslove.tokyo.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

348 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.101.76.7

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns1.boyslove.tokyo

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
30 2026-08-25 10:20 639232492740373468
531 ms 158.101.76.7
29 2026-08-25 10:03 639232482235303141
6 ms 158.101.76.7
28 2026-08-25 09:45 639232471861770303
514 ms 158.101.76.7
27 2026-08-25 09:28 639232461630217327
525 ms 158.101.76.7
26 2026-08-25 09:11 639232451282965990
39 ms 158.101.76.7
25 2026-08-25 08:54 639232440814614938
492 ms 158.101.76.7
24 2026-08-25 08:36 639232430410720425
507 ms 158.101.76.7
23 2026-08-25 08:19 639232420003096185
9 ms 158.101.76.7
22 2026-08-25 08:02 639232409467287444
7 ms 158.101.76.7
21 2026-08-25 07:44 639232399077195997
8 ms 158.101.76.7
20 2026-08-25 07:27 639232388731528337
248 ms 158.101.76.7
19 2026-08-25 07:09 639232378288598612
488 ms 158.101.76.7
18 2026-08-25 06:16 639232346196373643
518 ms 158.101.76.7
17 2026-08-25 05:59 639232336112370741
498 ms 158.101.76.7
16 2026-08-25 05:42 639232326146508970
250 ms 158.101.76.7
15 2026-08-25 05:26 639232316189381720
244 ms 158.101.76.7
14 2026-08-25 05:09 639232306217998913
503 ms 158.101.76.7
13 2026-08-25 04:52 639232296255744174
491 ms 158.101.76.7
12 2026-08-25 04:36 639232286095760789
6 ms 158.101.76.7
11 2026-08-25 04:19 639232276086186273
503 ms 158.101.76.7
10 2026-08-25 04:02 639232265900986425
22 ms 158.101.76.7
9 2026-08-25 03:45 639232255723518075
506 ms 158.101.76.7
8 2026-08-25 03:28 639232245484452890
494 ms 158.101.76.7
7 2026-08-25 03:11 639232235157175331
11 ms 158.101.76.7
6 2026-08-25 02:18 639232203197189095
489 ms 158.101.76.7
5 2026-08-25 02:01 639232192844564298
502 ms 158.101.76.7
4 2026-08-25 01:43 639232182496008942
527 ms 158.101.76.7
3 2026-08-25 01:26 639232172197053132
494 ms 158.101.76.7
2 2026-08-25 00:33 639232140250307418
512 ms 158.101.76.7
1 2026-08-25 00:16 639232129927860324
506 ms 158.101.76.7