DNS response history for dns1.a5s.jp

dns1.a5s.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 547 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 dns1.a5s.jp.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

547 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.10.131.171

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 dns1.a5s.jp

Showing DNS history for 2026-08-27 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-27 11:17 639234253963286387
501 ms 211.10.131.171
34 2026-08-27 11:00 639234243654907465
532 ms 211.10.131.171
33 2026-08-27 10:43 639234233269654413
823 ms 211.10.131.171
32 2026-08-27 10:26 639234222943951923
795 ms 211.10.131.171
31 2026-08-27 10:08 639234212558002823
511 ms 211.10.131.171
30 2026-08-27 09:51 639234202117531850
788 ms 211.10.131.171
29 2026-08-27 09:34 639234191649612722
539 ms 211.10.131.171
28 2026-08-27 09:16 639234181105879568
514 ms 211.10.131.171
27 2026-08-27 08:59 639234170713214496
521 ms 211.10.131.171
26 2026-08-27 08:41 639234160341037652
523 ms 211.10.131.171
25 2026-08-27 08:24 639234149799404224
520 ms 211.10.131.171
24 2026-08-27 08:06 639234139553286469
822 ms 211.10.131.171
23 2026-08-27 07:13 639234107183588293
510 ms 211.10.131.171
22 2026-08-27 06:56 639234096905435724
517 ms 211.10.131.171
21 2026-08-27 06:38 639234086579410775
522 ms 211.10.131.171
20 2026-08-27 06:21 639234076291157956
510 ms 211.10.131.171
19 2026-08-27 06:04 639234065981939454
513 ms 211.10.131.171
18 2026-08-27 05:47 639234055548642997
518 ms 211.10.131.171
17 2026-08-27 05:29 639234045267979603
530 ms 211.10.131.171
16 2026-08-27 05:12 639234034999717463
508 ms 211.10.131.171
15 2026-08-27 04:55 639234024739225358
525 ms 211.10.131.171
14 2026-08-27 04:38 639234014311170162
518 ms 211.10.131.171
13 2026-08-27 04:21 639234003806017640
808 ms 211.10.131.171
12 2026-08-27 04:03 639233993356203030
284 ms 211.10.131.171
11 2026-08-27 03:10 639233961301716608
506 ms 211.10.131.171
10 2026-08-27 02:52 639233950834200647
519 ms 211.10.131.171
9 2026-08-27 02:35 639233940431849026
529 ms 211.10.131.171
8 2026-08-27 02:18 639233930110596398
519 ms 211.10.131.171
7 2026-08-27 02:00 639233919705434540
3 ms 211.10.131.171
6 2026-08-27 01:43 639233909452807845
534 ms 211.10.131.171
5 2026-08-27 01:26 639233899096420820
812 ms 211.10.131.171
4 2026-08-27 01:09 639233888707824939
511 ms 211.10.131.171
3 2026-08-27 00:51 639233878461203802
528 ms 211.10.131.171
2 2026-08-27 00:34 639233868060868209
524 ms 211.10.131.171
1 2026-08-27 00:17 639233857450922991
508 ms 211.10.131.171