DNS response history for hmt.shz.jp

hmt.shz.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 30 DNS check records, 30 successful responses, 0 failed responses, and 480 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 hmt.shz.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

480 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

61.206.38.247

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 hmt.shz.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
30 2026-08-25 10:20 639232492740373468
517 ms 61.206.38.247
29 2026-08-25 10:03 639232482235303141
2266 ms 61.206.38.247
28 2026-08-25 09:46 639232471861770303
522 ms 61.206.38.247
27 2026-08-25 09:29 639232461630217327
3 ms 61.206.38.247
26 2026-08-25 09:11 639232451282965990
2243 ms 61.206.38.247
25 2026-08-25 08:54 639232440814614938
507 ms 61.206.38.247
24 2026-08-25 08:37 639232430410720425
506 ms 61.206.38.247
23 2026-08-25 08:19 639232420003096185
503 ms 61.206.38.247
22 2026-08-25 08:02 639232409467287444
250 ms 61.206.38.247
21 2026-08-25 07:45 639232399077195997
507 ms 61.206.38.247
20 2026-08-25 07:27 639232388731528337
3 ms 61.206.38.247
19 2026-08-25 07:10 639232378288598612
526 ms 61.206.38.247
18 2026-08-25 06:16 639232346196373643
3 ms 61.206.38.247
17 2026-08-25 05:59 639232336112370741
501 ms 61.206.38.247
16 2026-08-25 05:43 639232326146508970
3 ms 61.206.38.247
15 2026-08-25 05:26 639232316189381720
508 ms 61.206.38.247
14 2026-08-25 05:09 639232306217998913
4 ms 61.206.38.247
13 2026-08-25 04:53 639232296255744174
517 ms 61.206.38.247
12 2026-08-25 04:36 639232286095760789
9 ms 61.206.38.247
11 2026-08-25 04:19 639232276086186273
521 ms 61.206.38.247
10 2026-08-25 04:02 639232265900986425
502 ms 61.206.38.247
9 2026-08-25 03:45 639232255723518075
281 ms 61.206.38.247
8 2026-08-25 03:28 639232245484452890
513 ms 61.206.38.247
7 2026-08-25 03:11 639232235157175331
827 ms 61.206.38.247
6 2026-08-25 02:18 639232203197189095
3 ms 61.206.38.247
5 2026-08-25 02:01 639232192844564298
523 ms 61.206.38.247
4 2026-08-25 01:43 639232182496008942
281 ms 61.206.38.247
3 2026-08-25 01:26 639232172197053132
534 ms 61.206.38.247
2 2026-08-25 00:33 639232140250307418
3 ms 61.206.38.247
1 2026-08-25 00:16 639232129927860324
509 ms 61.206.38.247