DNS response history for ns2.lrcomm.net

ns2.lrcomm.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 31 DNS check records, 31 successful responses, 0 failed responses, and 455 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.lrcomm.net.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

455 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.216.132.170

Most recently resolved hosting IP on selected date

Successful Responses

31

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.lrcomm.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
31 2026-08-26 10:06 639233350067824371
2170 ms 162.216.132.170
30 2026-08-26 09:48 639233339545274518
137 ms 162.216.132.170
29 2026-08-26 09:31 639233329214918079
8 ms 162.216.132.170
28 2026-08-26 09:13 639233318749762337
243 ms 162.216.132.170
27 2026-08-26 08:56 639233308387917838
245 ms 162.216.132.170
26 2026-08-26 08:39 639233297961740122
243 ms 162.216.132.170
25 2026-08-26 08:21 639233287487159094
131 ms 162.216.132.170
24 2026-08-26 08:04 639233276995531707
132 ms 162.216.132.170
23 2026-08-26 07:46 639233266521568229
240 ms 162.216.132.170
22 2026-08-26 07:29 639233256081047431
249 ms 162.216.132.170
21 2026-08-26 06:35 639233223620132921
238 ms 162.216.132.170
20 2026-08-26 06:18 639233213287814244
237 ms 162.216.132.170
19 2026-08-26 06:00 639233202925983161
131 ms 162.216.132.170
18 2026-08-26 05:43 639233192644780696
248 ms 162.216.132.170
17 2026-08-26 05:26 639233182401183833
554 ms 162.216.132.170
16 2026-08-26 05:09 639233172074181051
140 ms 162.216.132.170
15 2026-08-26 04:52 639233161808421455
2170 ms 162.216.132.170
14 2026-08-26 04:34 639233151357344052
9 ms 162.216.132.170
13 2026-08-26 04:17 639233141034116946
245 ms 162.216.132.170
12 2026-08-26 04:00 639233130828334142
244 ms 162.216.132.170
11 2026-08-26 03:43 639233120373450007
156 ms 162.216.132.170
10 2026-08-26 03:25 639233110066216193
240 ms 162.216.132.170
9 2026-08-26 02:32 639233078065410564
259 ms 162.216.132.170
8 2026-08-26 02:15 639233067787457832
248 ms 162.216.132.170
7 2026-08-26 01:58 639233057501801162
243 ms 162.216.132.170
6 2026-08-26 01:41 639233047089431703
242 ms 162.216.132.170
5 2026-08-26 01:23 639233036754790688
241 ms 162.216.132.170
4 2026-08-26 01:06 639233026412602472
236 ms 162.216.132.170
3 2026-08-26 00:49 639233016064066127
252 ms 162.216.132.170
2 2026-08-26 00:32 639233005922655772
3750 ms 162.216.132.170
1 2026-08-26 00:15 639232995672256907
235 ms 162.216.132.170