DNS response history for hns2.htcn.ne.jp

hns2.htcn.ne.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 35 DNS check records, 35 successful responses, 0 failed responses, and 498 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 hns2.htcn.ne.jp.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

498 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.250.163.101

Most recently resolved hosting IP on selected date

Successful Responses

35

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 hns2.htcn.ne.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
35 2026-08-25 12:24 639232566381512620
434 ms 210.250.163.101
34 2026-08-25 12:06 639232556111768563
464 ms 210.250.163.101
33 2026-08-25 11:49 639232545839529039
827 ms 210.250.163.101
32 2026-08-25 11:32 639232535349285207
433 ms 210.250.163.101
31 2026-08-25 11:15 639232524938080723
572 ms 210.250.163.101
30 2026-08-25 10:21 639232492740373468
570 ms 210.250.163.101
29 2026-08-25 10:04 639232482235303141
543 ms 210.250.163.101
28 2026-08-25 09:46 639232471861770303
594 ms 210.250.163.101
27 2026-08-25 09:29 639232461630217327
549 ms 210.250.163.101
26 2026-08-25 09:12 639232451282965990
438 ms 210.250.163.101
25 2026-08-25 08:55 639232440814614938
289 ms 210.250.163.101
24 2026-08-25 08:37 639232430410720425
426 ms 210.250.163.101
23 2026-08-25 08:20 639232420003096185
285 ms 210.250.163.101
22 2026-08-25 08:02 639232409467287444
566 ms 210.250.163.101
21 2026-08-25 07:45 639232399077195997
425 ms 210.250.163.101
20 2026-08-25 07:28 639232388731528337
567 ms 210.250.163.101
19 2026-08-25 07:10 639232378288598612
570 ms 210.250.163.101
18 2026-08-25 06:16 639232346196373643
598 ms 210.250.163.101
17 2026-08-25 06:00 639232336112370741
558 ms 210.250.163.101
16 2026-08-25 05:43 639232326146508970
451 ms 210.250.163.101
15 2026-08-25 05:26 639232316189381720
281 ms 210.250.163.101
14 2026-08-25 05:10 639232306217998913
529 ms 210.250.163.101
13 2026-08-25 04:53 639232296255744174
557 ms 210.250.163.101
12 2026-08-25 04:36 639232286095760789
555 ms 210.250.163.101
11 2026-08-25 04:19 639232276086186273
526 ms 210.250.163.101
10 2026-08-25 04:03 639232265900986425
566 ms 210.250.163.101
9 2026-08-25 03:46 639232255723518075
569 ms 210.250.163.101
8 2026-08-25 03:29 639232245484452890
538 ms 210.250.163.101
7 2026-08-25 03:12 639232235157175331
583 ms 210.250.163.101
6 2026-08-25 02:18 639232203197189095
534 ms 210.250.163.101
5 2026-08-25 02:01 639232192844564298
10 ms 210.250.163.101
4 2026-08-25 01:44 639232182496008942
600 ms 210.250.163.101
3 2026-08-25 01:27 639232172197053132
547 ms 210.250.163.101
2 2026-08-25 00:33 639232140250307418
584 ms 210.250.163.101
1 2026-08-25 00:16 639232129927860324
289 ms 210.250.163.101