DNS response history for ns2.yxlm5.com

ns2.yxlm5.com 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 36 DNS check records, 36 successful responses, 0 failed responses, and 402 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 ns2.yxlm5.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

402 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 19:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.237.129.242

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns2.yxlm5.com

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
36 2026-08-24 19:24 639231952257842845
459 ms 172.237.129.242
35 2026-08-24 19:24 639231952257842845
459 ms 172.237.129.236
34 2026-08-24 19:24 639231952257842845
459 ms 172.237.129.108
33 2026-08-24 17:41 639231890488117536
309 ms 172.237.129.242
32 2026-08-24 17:41 639231890488117536
309 ms 172.237.129.236
31 2026-08-24 17:41 639231890488117536
309 ms 172.237.129.108
30 2026-08-24 15:57 639231828211839931
464 ms 172.237.129.242
29 2026-08-24 15:57 639231828211839931
464 ms 172.237.129.108
28 2026-08-24 15:57 639231828211839931
464 ms 172.237.129.236
27 2026-08-24 14:14 639231765923559455
317 ms 172.237.129.236
26 2026-08-24 14:14 639231765923559455
317 ms 172.237.129.242
25 2026-08-24 14:14 639231765923559455
317 ms 172.237.129.108
24 2026-08-24 12:30 639231703815441688
476 ms 172.237.129.236
23 2026-08-24 12:30 639231703815441688
476 ms 172.237.129.242
22 2026-08-24 12:30 639231703815441688
476 ms 172.237.129.108
21 2026-08-24 10:46 639231641791249939
328 ms 172.237.129.236
20 2026-08-24 10:46 639231641791249939
328 ms 172.237.129.108
19 2026-08-24 10:46 639231641791249939
328 ms 172.237.129.242
18 2026-08-24 09:04 639231579923718211
464 ms 172.237.129.236
17 2026-08-24 09:04 639231579923718211
464 ms 172.237.129.242
16 2026-08-24 09:04 639231579923718211
464 ms 172.237.129.108
15 2026-08-24 07:20 639231518076817246
478 ms 172.237.129.236
14 2026-08-24 07:20 639231518076817246
478 ms 172.237.129.242
13 2026-08-24 07:20 639231518076817246
478 ms 172.237.129.108
12 2026-08-24 05:38 639231456772510692
299 ms 172.237.129.242
11 2026-08-24 05:38 639231456772510692
299 ms 172.237.129.236
10 2026-08-24 05:38 639231456772510692
299 ms 172.237.129.108
9 2026-08-24 03:56 639231395791246644
468 ms 172.237.129.242
8 2026-08-24 03:56 639231395791246644
468 ms 172.237.129.108
7 2026-08-24 03:56 639231395791246644
468 ms 172.237.129.236
6 2026-08-24 02:15 639231334732159368
304 ms 172.237.129.108
5 2026-08-24 02:15 639231334732159368
304 ms 172.237.129.236
4 2026-08-24 02:15 639231334732159368
304 ms 172.237.129.242
3 2026-08-24 00:33 639231273779380675
456 ms 172.237.129.236
2 2026-08-24 00:33 639231273779380675
456 ms 172.237.129.108
1 2026-08-24 00:33 639231273779380675
456 ms 172.237.129.242