DNS response history for dns2.3lanhost.com

dns2.3lanhost.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-27. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 532 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.3lanhost.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

532 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

217.112.140.112

Most recently resolved hosting IP on selected date

Successful Responses

34

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.3lanhost.com

Showing DNS history for 2026-08-27 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
34 2026-08-27 10:52 639234243654907465
48 ms 217.112.140.112
33 2026-08-27 10:35 639234233269654413
4035 ms 217.112.140.112
32 2026-08-27 10:18 639234222943951923
2037 ms 217.112.140.112
31 2026-08-27 10:00 639234212558002823
53 ms 217.112.140.112
30 2026-08-27 09:43 639234202117531850
63 ms 217.112.140.112
29 2026-08-27 09:25 639234191649612722
55 ms 217.112.140.112
28 2026-08-27 09:08 639234181105879568
2047 ms 217.112.140.112
27 2026-08-27 08:50 639234170713214496
48 ms 217.112.140.112
26 2026-08-27 08:33 639234160341037652
45 ms 217.112.140.112
25 2026-08-27 08:16 639234149799404224
53 ms 217.112.140.112
24 2026-08-27 07:59 639234139553286469
2032 ms 217.112.140.112
23 2026-08-27 07:05 639234107183588293
2095 ms 217.112.140.112
22 2026-08-27 06:47 639234096905435724
40 ms 217.112.140.112
21 2026-08-27 06:30 639234086579410775
50 ms 217.112.140.112
20 2026-08-27 06:13 639234076291157956
52 ms 217.112.140.112
19 2026-08-27 05:56 639234065981939454
69 ms 217.112.140.112
18 2026-08-27 05:39 639234055548642997
46 ms 217.112.140.112
17 2026-08-27 05:21 639234045267979603
30 ms 217.112.140.112
16 2026-08-27 05:04 639234034999717463
58 ms 217.112.140.112
15 2026-08-27 04:47 639234024739225358
20 ms 217.112.140.112
14 2026-08-27 04:30 639234014311170162
21 ms 217.112.140.112
13 2026-08-27 04:12 639234003806017640
13 ms 217.112.140.112
12 2026-08-27 03:55 639233993356203030
43 ms 217.112.140.112
11 2026-08-27 03:02 639233961301716608
2067 ms 217.112.140.112
10 2026-08-27 02:44 639233950834200647
48 ms 217.112.140.112
9 2026-08-27 02:27 639233940431849026
34 ms 217.112.140.112
8 2026-08-27 02:10 639233930110596398
53 ms 217.112.140.112
7 2026-08-27 01:52 639233919705434540
2299 ms 217.112.140.112
6 2026-08-27 01:35 639233909452807845
51 ms 217.112.140.112
5 2026-08-27 01:18 639233899096420820
43 ms 217.112.140.112
4 2026-08-27 01:01 639233888707824939
63 ms 217.112.140.112
3 2026-08-27 00:43 639233878461203802
40 ms 217.112.140.112
2 2026-08-27 00:26 639233868060868209
47 ms 217.112.140.112
1 2026-08-27 00:09 639233857450922991
291 ms 217.112.140.112