DNS response history for ns1.shard.jp

ns1.shard.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-24. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 639 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.shard.jp.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

639 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.127.71.152

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 ns1.shard.jp

Showing DNS history for 2026-08-24 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-24 13:19 639231735407682062
558 ms 153.127.71.152
30 2026-08-24 12:26 639231703815441688
561 ms 153.127.71.152
29 2026-08-24 12:10 639231693747052549
538 ms 153.127.71.152
28 2026-08-24 11:53 639231683712487276
530 ms 153.127.71.152
27 2026-08-24 11:36 639231673513573868
540 ms 153.127.71.152
26 2026-08-24 10:43 639231641791249939
544 ms 153.127.71.152
25 2026-08-24 10:27 639231631866211033
553 ms 153.127.71.152
24 2026-08-24 10:10 639231621644955316
555 ms 153.127.71.152
23 2026-08-24 09:53 639231611478799259
556 ms 153.127.71.152
22 2026-08-24 09:00 639231579923718211
548 ms 153.127.71.152
21 2026-08-24 08:43 639231569810702936
527 ms 153.127.71.152
20 2026-08-24 08:26 639231559762411619
263 ms 153.127.71.152
19 2026-08-24 08:10 639231549663595407
527 ms 153.127.71.152
18 2026-08-24 07:17 639231518076817246
555 ms 153.127.71.152
17 2026-08-24 07:01 639231508078650885
538 ms 153.127.71.152
16 2026-08-24 06:44 639231498210697093
544 ms 153.127.71.152
15 2026-08-24 06:27 639231488109699360
537 ms 153.127.71.152
14 2026-08-24 05:35 639231456772510692
525 ms 153.127.71.152
13 2026-08-24 05:18 639231447084631185
2289 ms 153.127.71.152
12 2026-08-24 05:02 639231437208519473
305 ms 153.127.71.152
11 2026-08-24 04:46 639231427209627490
539 ms 153.127.71.152
10 2026-08-24 03:53 639231395791246644
562 ms 153.127.71.152
9 2026-08-24 03:37 639231386075551458
543 ms 153.127.71.152
8 2026-08-24 03:21 639231376208713791
531 ms 153.127.71.152
7 2026-08-24 03:04 639231366170589276
540 ms 153.127.71.152
6 2026-08-24 02:12 639231334732159368
530 ms 153.127.71.152
5 2026-08-24 01:55 639231325035670078
2295 ms 153.127.71.152
4 2026-08-24 01:39 639231315132253837
560 ms 153.127.71.152
3 2026-08-24 01:22 639231305014280808
552 ms 153.127.71.152
2 2026-08-24 00:30 639231273779380675
553 ms 153.127.71.152
1 2026-08-24 00:14 639231264180839154
518 ms 153.127.71.152