DNS response history for ns2.chicagopools4d.com

ns2.chicagopools4d.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-31. For this date, NameServerHistory found 32 DNS check records, 31 successful responses, 1 failed responses, and 171 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.chicagopools4d.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

171 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 10:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.135.94.65

Most recently resolved hosting IP on selected date

Successful Responses

31

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.chicagopools4d.com

Showing DNS history for 2026-08-31 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-31 10:37 639237690759595513
48 ms 5.135.94.65
31 2026-08-31 10:19 639237680122296836
44 ms 5.135.94.65
30 2026-08-31 09:26 639237647999458954
20 ms 5.135.94.65
29 2026-08-31 09:09 639237637680951774
6 ms 5.135.94.65
28 2026-08-31 08:51 639237627437728712
41 ms 5.135.94.65
27 2026-08-31 08:34 639237617127808241
41 ms 5.135.94.65
26 2026-08-31 08:17 639237606990101394
32 ms 5.135.94.65
25 2026-08-31 08:00 639237596595480036
7 ms 5.135.94.65
24 2026-08-31 07:43 639237586261012001
2023 ms 5.135.94.65
23 2026-08-31 07:26 639237576047657695
21 ms 5.135.94.65
22 2026-08-31 07:09 639237565832936443
38 ms 5.135.94.65
21 2026-08-31 06:51 639237555466329546
51 ms 5.135.94.65
20 2026-08-31 06:34 639237545032411072
81 ms 5.135.94.65
19 2026-08-31 06:16 639237534469438634
64 ms 5.135.94.65
18 2026-08-31 05:23 639237502279296801
30 ms 5.135.94.65
17 2026-08-31 05:06 639237492362730124
95 ms 5.135.94.65
16 2026-08-31 04:49 639237482311584319
2 ms 5.135.94.65
15 2026-08-31 04:33 639237472150685594
48 ms 5.135.94.65
14 2026-08-31 04:16 639237462055295430
-
13 2026-08-31 03:59 639237452089913890
7 ms 5.135.94.65
12 2026-08-31 03:42 639237441972654103
16 ms 5.135.94.65
11 2026-08-31 03:26 639237432052396478
10 ms 5.135.94.65
10 2026-08-31 03:09 639237422012990851
68 ms 5.135.94.65
9 2026-08-31 02:52 639237411889602012
112 ms 5.135.94.65
8 2026-08-31 02:35 639237401637354221
39 ms 5.135.94.65
7 2026-08-31 02:18 639237391412690360
50 ms 5.135.94.65
6 2026-08-31 01:25 639237359972957132
38 ms 5.135.94.65
5 2026-08-31 01:09 639237350032183979
47 ms 5.135.94.65
4 2026-08-31 00:52 639237340111452066
2022 ms 5.135.94.65
3 2026-08-31 00:36 639237329967272514
32 ms 5.135.94.65
2 2026-08-31 00:19 639237319916508151
59 ms 5.135.94.65
1 2026-08-31 00:02 639237309944877243
113 ms 5.135.94.65