DNS response history for ns2.loyalcom.net

ns2.loyalcom.net 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 170 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.loyalcom.net.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

170 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.43.12.122

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.loyalcom.net

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:31 639233329214918079
118 ms 67.43.12.122
28 2026-08-26 09:14 639233318749762337
225 ms 67.43.12.122
27 2026-08-26 08:57 639233308387917838
120 ms 67.43.12.122
26 2026-08-26 08:39 639233297961740122
116 ms 67.43.12.122
25 2026-08-26 08:22 639233287487159094
233 ms 67.43.12.122
24 2026-08-26 08:05 639233276995531707
125 ms 67.43.12.122
23 2026-08-26 07:47 639233266521568229
119 ms 67.43.12.122
22 2026-08-26 07:30 639233256081047431
128 ms 67.43.12.122
21 2026-08-26 06:36 639233223620132921
123 ms 67.43.12.122
20 2026-08-26 06:18 639233213287814244
228 ms 67.43.12.122
19 2026-08-26 06:01 639233202925983161
134 ms 67.43.12.122
18 2026-08-26 05:44 639233192644780696
225 ms 67.43.12.122
17 2026-08-26 05:27 639233182401183833
230 ms 67.43.12.122
16 2026-08-26 05:10 639233172074181051
226 ms 67.43.12.122
15 2026-08-26 04:52 639233161808421455
182 ms 67.43.12.122
14 2026-08-26 04:35 639233151357344052
112 ms 67.43.12.122
13 2026-08-26 04:18 639233141034116946
112 ms 67.43.12.122
12 2026-08-26 04:01 639233130828334142
231 ms 67.43.12.122
11 2026-08-26 03:44 639233120373450007
110 ms 67.43.12.122
10 2026-08-26 03:26 639233110066216193
121 ms 67.43.12.122
9 2026-08-26 02:33 639233078065410564
237 ms 67.43.12.122
8 2026-08-26 02:16 639233067787457832
228 ms 67.43.12.122
7 2026-08-26 01:59 639233057501801162
110 ms 67.43.12.122
6 2026-08-26 01:41 639233047089431703
225 ms 67.43.12.122
5 2026-08-26 01:24 639233036754790688
115 ms 67.43.12.122
4 2026-08-26 01:07 639233026412602472
227 ms 67.43.12.122
3 2026-08-26 00:50 639233016064066127
225 ms 67.43.12.122
2 2026-08-26 00:33 639233005922655772
224 ms 67.43.12.122
1 2026-08-26 00:15 639232995672256907
115 ms 67.43.12.122