DNS response history for ns2.icomputerdenver.com

ns2.icomputerdenver.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 35 DNS check records, 35 successful responses, 0 failed responses, and 159 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.icomputerdenver.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

159 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

178.32.106.127

Most recently resolved hosting IP on selected date

Successful Responses

35

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.icomputerdenver.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
35 2026-08-26 11:47 639233414056832719
35 ms 178.32.106.127
34 2026-08-26 11:30 639233403515141099
89 ms 178.32.106.127
33 2026-08-26 10:35 639233370841350248
26 ms 178.32.106.127
32 2026-08-26 10:18 639233360361507238
37 ms 178.32.106.127
31 2026-08-26 10:00 639233350067824371
34 ms 178.32.106.127
30 2026-08-26 09:43 639233339545274518
34 ms 178.32.106.127
29 2026-08-26 09:26 639233329214918079
76 ms 178.32.106.127
28 2026-08-26 09:08 639233318749762337
69 ms 178.32.106.127
27 2026-08-26 08:51 639233308387917838
69 ms 178.32.106.127
26 2026-08-26 08:34 639233297961740122
40 ms 178.32.106.127
25 2026-08-26 08:16 639233287487159094
2055 ms 178.32.106.127
24 2026-08-26 07:59 639233276995531707
68 ms 178.32.106.127
23 2026-08-26 07:41 639233266521568229
24 ms 178.32.106.127
22 2026-08-26 07:24 639233256081047431
72 ms 178.32.106.127
21 2026-08-26 06:30 639233223620132921
18 ms 178.32.106.127
20 2026-08-26 06:13 639233213287814244
8 ms 178.32.106.127
19 2026-08-26 05:55 639233202925983161
42 ms 178.32.106.127
18 2026-08-26 05:38 639233192644780696
19 ms 178.32.106.127
17 2026-08-26 05:21 639233182401183833
40 ms 178.32.106.127
16 2026-08-26 05:04 639233172074181051
63 ms 178.32.106.127
15 2026-08-26 04:47 639233161808421455
59 ms 178.32.106.127
14 2026-08-26 04:29 639233151357344052
2052 ms 178.32.106.127
13 2026-08-26 04:12 639233141034116946
44 ms 178.32.106.127
12 2026-08-26 03:55 639233130828334142
78 ms 178.32.106.127
11 2026-08-26 03:38 639233120373450007
33 ms 178.32.106.127
10 2026-08-26 03:20 639233110066216193
33 ms 178.32.106.127
9 2026-08-26 02:27 639233078065410564
8 ms 178.32.106.127
8 2026-08-26 02:10 639233067787457832
42 ms 178.32.106.127
7 2026-08-26 01:53 639233057501801162
47 ms 178.32.106.127
6 2026-08-26 01:36 639233047089431703
61 ms 178.32.106.127
5 2026-08-26 01:18 639233036754790688
35 ms 178.32.106.127
4 2026-08-26 01:01 639233026412602472
23 ms 178.32.106.127
3 2026-08-26 00:44 639233016064066127
35 ms 178.32.106.127
2 2026-08-26 00:27 639233005922655772
31 ms 178.32.106.127
1 2026-08-26 00:10 639232995672256907
72 ms 178.32.106.127