DNS response history for second.ary.jp

second.ary.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-28. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 539 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 second.ary.jp.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

539 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 16:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

133.125.53.22

Most recently resolved hosting IP on selected date

Successful Responses

38

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 second.ary.jp

Showing DNS history for 2026-08-28 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
38 2026-08-28 16:24 639235301738139314
545 ms 133.125.53.22
37 2026-08-28 16:06 639235291168160936
534 ms 133.125.53.22
36 2026-08-28 15:12 639235258803654519
532 ms 133.125.53.22
35 2026-08-28 14:55 639235248596087996
539 ms 133.125.53.22
34 2026-08-28 14:37 639235238225955920
562 ms 133.125.53.22
33 2026-08-28 14:20 639235227727862105
554 ms 133.125.53.22
32 2026-08-28 13:26 639235195230848570
529 ms 133.125.53.22
31 2026-08-28 13:09 639235184840503274
540 ms 133.125.53.22
30 2026-08-28 12:51 639235174453894956
544 ms 133.125.53.22
29 2026-08-28 12:34 639235163898672622
545 ms 133.125.53.22
28 2026-08-28 11:41 639235132147470568
540 ms 133.125.53.22
27 2026-08-28 11:24 639235121907744088
544 ms 133.125.53.22
26 2026-08-28 11:06 639235111428014262
795 ms 133.125.53.22
25 2026-08-28 10:49 639235100921813626
545 ms 133.125.53.22
24 2026-08-28 09:55 639235068670703481
544 ms 133.125.53.22
23 2026-08-28 09:38 639235058337459445
541 ms 133.125.53.22
22 2026-08-28 09:20 639235047825109146
530 ms 133.125.53.22
21 2026-08-28 09:03 639235037383229033
548 ms 133.125.53.22
20 2026-08-28 08:10 639235005619242711
548 ms 133.125.53.22
19 2026-08-28 07:53 639234995310346584
536 ms 133.125.53.22
18 2026-08-28 07:35 639234984946548933
548 ms 133.125.53.22
17 2026-08-28 07:18 639234974608077290
786 ms 133.125.53.22
16 2026-08-28 06:25 639234942529845595
543 ms 133.125.53.22
15 2026-08-28 06:08 639234932259126627
541 ms 133.125.53.22
14 2026-08-28 05:50 639234921916735988
538 ms 133.125.53.22
13 2026-08-28 05:33 639234911470038027
542 ms 133.125.53.22
12 2026-08-28 04:40 639234879588411654
528 ms 133.125.53.22
11 2026-08-28 04:23 639234869341589104
4 ms 133.125.53.22
10 2026-08-28 04:05 639234859012216675
534 ms 133.125.53.22
9 2026-08-28 03:48 639234848695364934
541 ms 133.125.53.22
8 2026-08-28 02:55 639234816952458162
526 ms 133.125.53.22
7 2026-08-28 02:38 639234806773081598
547 ms 133.125.53.22
6 2026-08-28 02:21 639234796382955255
526 ms 133.125.53.22
5 2026-08-28 02:04 639234786015782563
527 ms 133.125.53.22
4 2026-08-28 01:10 639234753811917646
531 ms 133.125.53.22
3 2026-08-28 00:53 639234743739767811
541 ms 133.125.53.22
2 2026-08-28 00:36 639234733372362811
540 ms 133.125.53.22
1 2026-08-28 00:19 639234723048550337
548 ms 133.125.53.22