DNS response history for ns1.agml.jp

ns1.agml.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-26. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 493 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.agml.jp.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

493 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.212.211.250

Most recently resolved hosting IP on selected date

Successful Responses

32

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.agml.jp

Showing DNS history for 2026-08-26 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
32 2026-08-26 10:10 639233350067824371
528 ms 49.212.211.250
31 2026-08-26 09:53 639233339545274518
546 ms 49.212.211.250
30 2026-08-26 09:35 639233329214918079
541 ms 49.212.211.250
29 2026-08-26 09:18 639233318749762337
560 ms 49.212.211.250
28 2026-08-26 09:00 639233308387917838
612 ms 49.212.211.250
27 2026-08-26 08:43 639233297961740122
536 ms 49.212.211.250
26 2026-08-26 08:26 639233287487159094
549 ms 49.212.211.250
25 2026-08-26 08:08 639233276995531707
543 ms 49.212.211.250
24 2026-08-26 07:51 639233266521568229
552 ms 49.212.211.250
23 2026-08-26 07:33 639233256081047431
561 ms 49.212.211.250
22 2026-08-26 06:39 639233223620132921
3 ms 49.212.211.250
21 2026-08-26 06:22 639233213287814244
555 ms 49.212.211.250
20 2026-08-26 06:05 639233202925983161
549 ms 49.212.211.250
19 2026-08-26 05:47 639233192644780696
536 ms 49.212.211.250
18 2026-08-26 05:30 639233182401183833
3 ms 49.212.211.250
17 2026-08-26 05:13 639233172074181051
536 ms 49.212.211.250
16 2026-08-26 04:56 639233161808421455
9 ms 49.212.211.250
15 2026-08-26 04:39 639233151357344052
3 ms 49.212.211.250
14 2026-08-26 04:21 639233141034116946
294 ms 49.212.211.250
13 2026-08-26 04:04 639233130828334142
543 ms 49.212.211.250
12 2026-08-26 03:47 639233120373450007
558 ms 49.212.211.250
11 2026-08-26 03:30 639233110066216193
539 ms 49.212.211.250
10 2026-08-26 02:37 639233078065410564
3 ms 49.212.211.250
9 2026-08-26 02:19 639233067787457832
538 ms 49.212.211.250
8 2026-08-26 02:02 639233057501801162
2 ms 49.212.211.250
7 2026-08-26 01:45 639233047089431703
557 ms 49.212.211.250
6 2026-08-26 01:28 639233036754790688
2296 ms 49.212.211.250
5 2026-08-26 01:11 639233026412602472
538 ms 49.212.211.250
4 2026-08-26 00:53 639233016064066127
548 ms 49.212.211.250
3 2026-08-26 00:36 639233005922655772
541 ms 49.212.211.250
2 2026-08-26 00:19 639232995672256907
538 ms 49.212.211.250
1 2026-08-26 00:02 639232985300872416
544 ms 49.212.211.250