DNS response history for ns2.horigome.jp

ns2.horigome.jp 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 33 DNS check records, 33 successful responses, 0 failed responses, and 421 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.horigome.jp.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

421 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

221.240.201.100

Most recently resolved hosting IP on selected date

Successful Responses

33

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.horigome.jp

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
33 2026-08-25 11:33 639232535349285207
254 ms 221.240.201.100
32 2026-08-25 11:16 639232524938080723
260 ms 221.240.201.100
31 2026-08-25 10:22 639232492740373468
240 ms 221.240.201.100
30 2026-08-25 10:05 639232482235303141
1109 ms 221.240.201.100
29 2026-08-25 09:47 639232471861770303
249 ms 221.240.201.100
28 2026-08-25 09:30 639232461630217327
1112 ms 221.240.201.100
27 2026-08-25 09:13 639232451282965990
502 ms 221.240.201.100
26 2026-08-25 08:56 639232440814614938
489 ms 221.240.201.100
25 2026-08-25 08:38 639232430410720425
492 ms 221.240.201.100
24 2026-08-25 08:21 639232420003096185
251 ms 221.240.201.100
23 2026-08-25 08:03 639232409467287444
241 ms 221.240.201.100
22 2026-08-25 07:46 639232399077195997
238 ms 221.240.201.100
21 2026-08-25 07:29 639232388731528337
237 ms 221.240.201.100
20 2026-08-25 07:11 639232378288598612
963 ms 221.240.201.100
19 2026-08-25 06:17 639232346196373643
242 ms 221.240.201.100
18 2026-08-25 06:01 639232336112370741
515 ms 221.240.201.100
17 2026-08-25 05:44 639232326146508970
245 ms 221.240.201.100
16 2026-08-25 05:27 639232316189381720
238 ms 221.240.201.100
15 2026-08-25 05:11 639232306217998913
2 ms 221.240.201.100
14 2026-08-25 04:54 639232296255744174
2 ms 221.240.201.100
13 2026-08-25 04:37 639232286095760789
2 ms 221.240.201.100
12 2026-08-25 04:20 639232276086186273
483 ms 221.240.201.100
11 2026-08-25 04:04 639232265900986425
508 ms 221.240.201.100
10 2026-08-25 03:47 639232255723518075
3 ms 221.240.201.100
9 2026-08-25 03:30 639232245484452890
1101 ms 221.240.201.100
8 2026-08-25 03:13 639232235157175331
245 ms 221.240.201.100
7 2026-08-25 02:19 639232203197189095
854 ms 221.240.201.100
6 2026-08-25 02:02 639232192844564298
482 ms 221.240.201.100
5 2026-08-25 01:45 639232182496008942
1094 ms 221.240.201.100
4 2026-08-25 01:28 639232172197053132
252 ms 221.240.201.100
3 2026-08-25 00:34 639232140250307418
242 ms 221.240.201.100
2 2026-08-25 00:17 639232129927860324
252 ms 221.240.201.100
1 2026-08-25 00:00 639232119551972438
482 ms 221.240.201.100