DNS response history for ns.chicago-lane.com

ns.chicago-lane.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-24. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 94 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 ns.chicago-lane.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

94 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

92.205.109.180

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 ns.chicago-lane.com

Showing DNS history for 2026-08-24 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-24 13:27 639231745628278877
33 ms 92.205.109.180
31 2026-08-24 13:10 639231735407682062
30 ms 92.205.109.180
30 2026-08-24 12:17 639231703815441688
27 ms 92.205.109.180
29 2026-08-24 12:01 639231693747052549
42 ms 92.205.109.180
28 2026-08-24 11:44 639231683712487276
7 ms 92.205.109.180
27 2026-08-24 11:27 639231673513573868
4 ms 92.205.109.180
26 2026-08-24 10:34 639231641791249939
51 ms 92.205.109.180
25 2026-08-24 10:17 639231631866211033
19 ms 92.205.109.180
24 2026-08-24 10:01 639231621644955316
20 ms 92.205.109.180
23 2026-08-24 09:43 639231611478799259
21 ms 92.205.109.180
22 2026-08-24 08:51 639231579923718211
50 ms 92.205.109.180
21 2026-08-24 08:34 639231569810702936
28 ms 92.205.109.180
20 2026-08-24 08:17 639231559762411619
26 ms 92.205.109.180
19 2026-08-24 08:00 639231549663595407
28 ms 92.205.109.180
18 2026-08-24 07:08 639231518076817246
20 ms 92.205.109.180
17 2026-08-24 06:51 639231508078650885
74 ms 92.205.109.180
16 2026-08-24 06:35 639231498210697093
2030 ms 92.205.109.180
15 2026-08-24 06:18 639231488109699360
44 ms 92.205.109.180
14 2026-08-24 05:26 639231456772510692
7 ms 92.205.109.180
13 2026-08-24 05:10 639231447084631185
42 ms 92.205.109.180
12 2026-08-24 04:53 639231437208519473
41 ms 92.205.109.180
11 2026-08-24 04:36 639231427209627490
18 ms 92.205.109.180
10 2026-08-24 03:44 639231395791246644
35 ms 92.205.109.180
9 2026-08-24 03:28 639231386075551458
30 ms 92.205.109.180
8 2026-08-24 03:11 639231376208713791
35 ms 92.205.109.180
7 2026-08-24 02:55 639231366170589276
46 ms 92.205.109.180
6 2026-08-24 02:02 639231334732159368
41 ms 92.205.109.180
5 2026-08-24 01:46 639231325035670078
64 ms 92.205.109.180
4 2026-08-24 01:30 639231315132253837
39 ms 92.205.109.180
3 2026-08-24 01:13 639231305014280808
20 ms 92.205.109.180
2 2026-08-24 00:21 639231273779380675
37 ms 92.205.109.180
1 2026-08-24 00:05 639231264180839154
9 ms 92.205.109.180