DNS response history for ns2.lrcomm.org

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

32

Historical checks stored for this nameserver on selected date

Average Latency

282 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.216.132.3

Most recently resolved hosting IP on selected date

Successful Responses

32

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.org

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
32 2026-08-26 10:23 639233360361507238
253 ms 162.216.132.3
31 2026-08-26 10:06 639233350067824371
118 ms 162.216.132.3
30 2026-08-26 09:49 639233339545274518
193 ms 162.216.132.3
29 2026-08-26 09:31 639233329214918079
153 ms 162.216.132.3
28 2026-08-26 09:14 639233318749762337
500 ms 162.216.132.3
27 2026-08-26 08:56 639233308387917838
117 ms 162.216.132.3
26 2026-08-26 08:39 639233297961740122
368 ms 162.216.132.3
25 2026-08-26 08:22 639233287487159094
251 ms 162.216.132.3
24 2026-08-26 08:04 639233276995531707
144 ms 162.216.132.3
23 2026-08-26 07:47 639233266521568229
124 ms 162.216.132.3
22 2026-08-26 07:29 639233256081047431
241 ms 162.216.132.3
21 2026-08-26 06:35 639233223620132921
118 ms 162.216.132.3
20 2026-08-26 06:18 639233213287814244
601 ms 162.216.132.3
19 2026-08-26 06:01 639233202925983161
358 ms 162.216.132.3
18 2026-08-26 05:43 639233192644780696
234 ms 162.216.132.3
17 2026-08-26 05:26 639233182401183833
118 ms 162.216.132.3
16 2026-08-26 05:09 639233172074181051
387 ms 162.216.132.3
15 2026-08-26 04:52 639233161808421455
134 ms 162.216.132.3
14 2026-08-26 04:35 639233151357344052
247 ms 162.216.132.3
13 2026-08-26 04:17 639233141034116946
238 ms 162.216.132.3
12 2026-08-26 04:00 639233130828334142
244 ms 162.216.132.3
11 2026-08-26 03:43 639233120373450007
2122 ms 162.216.132.3
10 2026-08-26 03:26 639233110066216193
129 ms 162.216.132.3
9 2026-08-26 02:33 639233078065410564
383 ms 162.216.132.3
8 2026-08-26 02:15 639233067787457832
119 ms 162.216.132.3
7 2026-08-26 01:58 639233057501801162
117 ms 162.216.132.3
6 2026-08-26 01:41 639233047089431703
9 ms 162.216.132.3
5 2026-08-26 01:24 639233036754790688
134 ms 162.216.132.3
4 2026-08-26 01:07 639233026412602472
114 ms 162.216.132.3
3 2026-08-26 00:49 639233016064066127
497 ms 162.216.132.3
2 2026-08-26 00:32 639233005922655772
33 ms 162.216.132.3
1 2026-08-26 00:15 639232995672256907
240 ms 162.216.132.3