DNS response history for ns2.loyalhome.com

ns2.loyalhome.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-26. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 377 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.loyalhome.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

377 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.214.157.216

Most recently resolved hosting IP on selected date

Successful Responses

29

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.loyalhome.com

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
29 2026-08-26 09:33 639233329214918079
7 ms 162.214.157.216
28 2026-08-26 09:15 639233318749762337
2166 ms 162.214.157.216
27 2026-08-26 08:58 639233308387917838
349 ms 162.214.157.216
26 2026-08-26 08:41 639233297961740122
348 ms 162.214.157.216
25 2026-08-26 08:23 639233287487159094
344 ms 162.214.157.216
24 2026-08-26 08:06 639233276995531707
337 ms 162.214.157.216
23 2026-08-26 07:48 639233266521568229
327 ms 162.214.157.216
22 2026-08-26 07:31 639233256081047431
323 ms 162.214.157.216
21 2026-08-26 06:37 639233223620132921
157 ms 162.214.157.216
20 2026-08-26 06:19 639233213287814244
317 ms 162.214.157.216
19 2026-08-26 06:02 639233202925983161
320 ms 162.214.157.216
18 2026-08-26 05:45 639233192644780696
2157 ms 162.214.157.216
17 2026-08-26 05:28 639233182401183833
321 ms 162.214.157.216
16 2026-08-26 05:11 639233172074181051
318 ms 162.214.157.216
15 2026-08-26 04:54 639233161808421455
315 ms 162.214.157.216
14 2026-08-26 04:36 639233151357344052
330 ms 162.214.157.216
13 2026-08-26 04:19 639233141034116946
317 ms 162.214.157.216
12 2026-08-26 04:02 639233130828334142
7 ms 162.214.157.216
11 2026-08-26 03:45 639233120373450007
323 ms 162.214.157.216
10 2026-08-26 03:27 639233110066216193
7 ms 162.214.157.216
9 2026-08-26 02:34 639233078065410564
331 ms 162.214.157.216
8 2026-08-26 02:17 639233067787457832
3 ms 162.214.157.216
7 2026-08-26 02:00 639233057501801162
4 ms 162.214.157.216
6 2026-08-26 01:43 639233047089431703
318 ms 162.214.157.216
5 2026-08-26 01:25 639233036754790688
8 ms 162.214.157.216
4 2026-08-26 01:08 639233026412602472
317 ms 162.214.157.216
3 2026-08-26 00:51 639233016064066127
321 ms 162.214.157.216
2 2026-08-26 00:34 639233005922655772
208 ms 162.214.157.216
1 2026-08-26 00:17 639232995672256907
319 ms 162.214.157.216