DNS response history for alabang.ytp.ne.jp

alabang.ytp.ne.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 34 DNS check records, 34 successful responses, 0 failed responses, and 601 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 alabang.ytp.ne.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

601 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

219.111.8.233

Most recently resolved hosting IP on selected date

Successful Responses

34

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 alabang.ytp.ne.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
34 2026-08-26 10:45 639233370841350248
856 ms 219.111.8.233
33 2026-08-26 10:28 639233360361507238
570 ms 219.111.8.233
32 2026-08-26 10:10 639233350067824371
581 ms 219.111.8.233
31 2026-08-26 09:53 639233339545274518
618 ms 219.111.8.233
30 2026-08-26 09:35 639233329214918079
588 ms 219.111.8.233
29 2026-08-26 09:18 639233318749762337
655 ms 219.111.8.233
28 2026-08-26 09:01 639233308387917838
897 ms 219.111.8.233
27 2026-08-26 08:44 639233297961740122
3 ms 219.111.8.233
26 2026-08-26 08:26 639233287487159094
596 ms 219.111.8.233
25 2026-08-26 08:09 639233276995531707
601 ms 219.111.8.233
24 2026-08-26 07:51 639233266521568229
585 ms 219.111.8.233
23 2026-08-26 07:34 639233256081047431
596 ms 219.111.8.233
22 2026-08-26 06:40 639233223620132921
581 ms 219.111.8.233
21 2026-08-26 06:22 639233213287814244
586 ms 219.111.8.233
20 2026-08-26 06:05 639233202925983161
577 ms 219.111.8.233
19 2026-08-26 05:48 639233192644780696
641 ms 219.111.8.233
18 2026-08-26 05:31 639233182401183833
643 ms 219.111.8.233
17 2026-08-26 05:14 639233172074181051
832 ms 219.111.8.233
16 2026-08-26 04:56 639233161808421455
619 ms 219.111.8.233
15 2026-08-26 04:39 639233151357344052
583 ms 219.111.8.233
14 2026-08-26 04:22 639233141034116946
597 ms 219.111.8.233
13 2026-08-26 04:05 639233130828334142
598 ms 219.111.8.233
12 2026-08-26 03:48 639233120373450007
615 ms 219.111.8.233
11 2026-08-26 03:30 639233110066216193
618 ms 219.111.8.233
10 2026-08-26 02:37 639233078065410564
590 ms 219.111.8.233
9 2026-08-26 02:20 639233067787457832
649 ms 219.111.8.233
8 2026-08-26 02:03 639233057501801162
585 ms 219.111.8.233
7 2026-08-26 01:46 639233047089431703
751 ms 219.111.8.233
6 2026-08-26 01:28 639233036754790688
563 ms 219.111.8.233
5 2026-08-26 01:11 639233026412602472
624 ms 219.111.8.233
4 2026-08-26 00:54 639233016064066127
603 ms 219.111.8.233
3 2026-08-26 00:37 639233005922655772
572 ms 219.111.8.233
2 2026-08-26 00:19 639232995672256907
284 ms 219.111.8.233
1 2026-08-26 00:02 639232985300872416
588 ms 219.111.8.233