DNS response history for ns1.capcomputer2.com

ns1.capcomputer2.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 36 DNS check records, 36 successful responses, 0 failed responses, and 475 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 ns1.capcomputer2.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

475 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.241.78.166

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns1.capcomputer2.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
36 2026-08-27 12:10 639234286253196126
302 ms 162.241.78.166
35 2026-08-27 11:16 639234253963286387
308 ms 162.241.78.166
34 2026-08-27 10:59 639234243654907465
308 ms 162.241.78.166
33 2026-08-27 10:42 639234233269654413
795 ms 162.241.78.166
32 2026-08-27 10:24 639234222943951923
816 ms 162.241.78.166
31 2026-08-27 10:07 639234212558002823
802 ms 162.241.78.166
30 2026-08-27 09:50 639234202117531850
307 ms 162.241.78.166
29 2026-08-27 09:33 639234191649612722
812 ms 162.241.78.166
28 2026-08-27 09:15 639234181105879568
301 ms 162.241.78.166
27 2026-08-27 08:57 639234170713214496
310 ms 162.241.78.166
26 2026-08-27 08:40 639234160341037652
303 ms 162.241.78.166
25 2026-08-27 08:23 639234149799404224
292 ms 162.241.78.166
24 2026-08-27 08:05 639234139553286469
2130 ms 162.241.78.166
23 2026-08-27 07:12 639234107183588293
4 ms 162.241.78.166
22 2026-08-27 06:54 639234096905435724
277 ms 162.241.78.166
21 2026-08-27 06:37 639234086579410775
293 ms 162.241.78.166
20 2026-08-27 06:20 639234076291157956
798 ms 162.241.78.166
19 2026-08-27 06:03 639234065981939454
776 ms 162.241.78.166
18 2026-08-27 05:46 639234055548642997
235 ms 162.241.78.166
17 2026-08-27 05:28 639234045267979603
270 ms 162.241.78.166
16 2026-08-27 05:11 639234034999717463
787 ms 162.241.78.166
15 2026-08-27 04:54 639234024739225358
289 ms 162.241.78.166
14 2026-08-27 04:37 639234014311170162
771 ms 162.241.78.166
13 2026-08-27 04:19 639234003806017640
279 ms 162.241.78.166
12 2026-08-27 04:02 639233993356203030
273 ms 162.241.78.166
11 2026-08-27 03:09 639233961301716608
772 ms 162.241.78.166
10 2026-08-27 02:51 639233950834200647
272 ms 162.241.78.166
9 2026-08-27 02:34 639233940431849026
290 ms 162.241.78.166
8 2026-08-27 02:16 639233930110596398
4 ms 162.241.78.166
7 2026-08-27 01:59 639233919705434540
221 ms 162.241.78.166
6 2026-08-27 01:42 639233909452807845
346 ms 162.241.78.166
5 2026-08-27 01:25 639233899096420820
847 ms 162.241.78.166
4 2026-08-27 01:08 639233888707824939
18 ms 162.241.78.166
3 2026-08-27 00:50 639233878461203802
304 ms 162.241.78.166
2 2026-08-27 00:33 639233868060868209
346 ms 162.241.78.166
1 2026-08-27 00:16 639233857450922991
847 ms 162.241.78.166