DNS response history for dns2.lamersfam.com

dns2.lamersfam.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 38 DNS check records, 38 successful responses, 0 failed responses, and 375 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 dns2.lamersfam.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

375 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

47.49.255.2

Most recently resolved hosting IP on selected date

Successful Responses

38

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 dns2.lamersfam.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
38 2026-08-26 12:31 639233434974187439
134 ms 47.49.255.2
37 2026-08-26 12:13 639233424567558554
199 ms 47.49.255.2
36 2026-08-26 11:56 639233414056832719
273 ms 47.49.255.2
35 2026-08-26 11:38 639233403515141099
263 ms 47.49.255.2
34 2026-08-26 10:43 639233370841350248
167 ms 47.49.255.2
33 2026-08-26 10:26 639233360361507238
132 ms 47.49.255.2
32 2026-08-26 10:09 639233350067824371
268 ms 47.49.255.2
31 2026-08-26 09:52 639233339545274518
4 ms 47.49.255.2
30 2026-08-26 09:34 639233329214918079
4 ms 47.49.255.2
29 2026-08-26 09:17 639233318749762337
591 ms 47.49.255.2
28 2026-08-26 08:59 639233308387917838
268 ms 47.49.255.2
27 2026-08-26 08:42 639233297961740122
278 ms 47.49.255.2
26 2026-08-26 08:25 639233287487159094
271 ms 47.49.255.2
25 2026-08-26 08:07 639233276995531707
285 ms 47.49.255.2
24 2026-08-26 07:50 639233266521568229
272 ms 47.49.255.2
23 2026-08-26 07:32 639233256081047431
268 ms 47.49.255.2
22 2026-08-26 06:38 639233223620132921
299 ms 47.49.255.2
21 2026-08-26 06:21 639233213287814244
520 ms 47.49.255.2
20 2026-08-26 06:04 639233202925983161
268 ms 47.49.255.2
19 2026-08-26 05:47 639233192644780696
282 ms 47.49.255.2
18 2026-08-26 05:29 639233182401183833
265 ms 47.49.255.2
17 2026-08-26 05:12 639233172074181051
270 ms 47.49.255.2
16 2026-08-26 04:55 639233161808421455
271 ms 47.49.255.2
15 2026-08-26 04:38 639233151357344052
4 ms 47.49.255.2
14 2026-08-26 04:20 639233141034116946
144 ms 47.49.255.2
13 2026-08-26 04:03 639233130828334142
263 ms 47.49.255.2
12 2026-08-26 03:46 639233120373450007
265 ms 47.49.255.2
11 2026-08-26 03:29 639233110066216193
2780 ms 47.49.255.2
10 2026-08-26 02:36 639233078065410564
132 ms 47.49.255.2
9 2026-08-26 02:19 639233067787457832
306 ms 47.49.255.2
8 2026-08-26 02:01 639233057501801162
265 ms 47.49.255.2
7 2026-08-26 01:44 639233047089431703
2763 ms 47.49.255.2
6 2026-08-26 01:27 639233036754790688
264 ms 47.49.255.2
5 2026-08-26 01:10 639233026412602472
135 ms 47.49.255.2
4 2026-08-26 00:52 639233016064066127
277 ms 47.49.255.2
3 2026-08-26 00:35 639233005922655772
268 ms 47.49.255.2
2 2026-08-26 00:18 639232995672256907
272 ms 47.49.255.2
1 2026-08-26 00:01 639232985300872416
273 ms 47.49.255.2