DNS response history for ns-c.i-possible.net

ns-c.i-possible.net 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, 31 successful responses, 1 failed responses, and 158 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-c.i-possible.net.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

158 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.80.126.159

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 ns-c.i-possible.net

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:23 639231745628278877
23 ms 208.80.126.159
31 2026-08-24 13:06 639231735407682062
15 ms 208.80.126.159
30 2026-08-24 12:14 639231703815441688
17 ms 208.80.126.159
29 2026-08-24 11:57 639231693747052549
38 ms 208.80.126.159
28 2026-08-24 11:40 639231683712487276
21 ms 208.80.126.159
27 2026-08-24 11:23 639231673513573868
15 ms 208.80.126.159
26 2026-08-24 10:30 639231641791249939
29 ms 208.80.126.159
25 2026-08-24 10:14 639231631866211033
11 ms 208.80.126.159
24 2026-08-24 09:57 639231621644955316
112 ms 208.80.126.159
23 2026-08-24 09:40 639231611478799259
27 ms 208.80.126.159
22 2026-08-24 08:47 639231579923718211
13 ms 208.80.126.159
21 2026-08-24 08:30 639231569810702936
10 ms 208.80.126.159
20 2026-08-24 08:14 639231559762411619
20 ms 208.80.126.159
19 2026-08-24 07:57 639231549663595407
172 ms 208.80.126.159
18 2026-08-24 07:04 639231518076817246
24 ms 208.80.126.159
17 2026-08-24 06:48 639231508078650885
4061 ms 208.80.126.159
16 2026-08-24 06:31 639231498210697093
23 ms 208.80.126.159
15 2026-08-24 06:14 639231488109699360
10 ms 208.80.126.159
14 2026-08-24 05:22 639231456772510692
18 ms 208.80.126.159
13 2026-08-24 05:06 639231447084631185
20 ms 208.80.126.159
12 2026-08-24 04:49 639231437208519473
18 ms 208.80.126.159
11 2026-08-24 04:33 639231427209627490
23 ms 208.80.126.159
10 2026-08-24 03:40 639231395791246644
8 ms 208.80.126.159
9 2026-08-24 03:24 639231386075551458
9 ms 208.80.126.159
8 2026-08-24 03:08 639231376208713791
4 ms 208.80.126.159
7 2026-08-24 02:51 639231366170589276
44 ms 208.80.126.159
6 2026-08-24 01:59 639231334732159368
19 ms 208.80.126.159
5 2026-08-24 01:42 639231325035670078
18 ms 208.80.126.159
4 2026-08-24 01:26 639231315132253837
41 ms 208.80.126.159
3 2026-08-24 01:09 639231305014280808
19 ms 208.80.126.159
2 2026-08-24 00:17 639231273779380675
-
1 2026-08-24 00:01 639231264180839154
21 ms 208.80.126.159