DNS response history for ns-can-2.acciss.com

ns-can-2.acciss.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 37 DNS check records, 37 successful responses, 0 failed responses, and 313 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-can-2.acciss.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

313 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

148.113.209.7

Most recently resolved hosting IP on selected date

Successful Responses

37

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-can-2.acciss.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
37 2026-08-24 15:34 639231818080917481
304 ms 148.113.209.7
36 2026-08-24 15:17 639231807961539652
170 ms 148.113.209.7
35 2026-08-24 15:00 639231797631669865
333 ms 148.113.209.7
34 2026-08-24 14:07 639231765923559455
341 ms 148.113.209.7
33 2026-08-24 13:50 639231755868832964
311 ms 148.113.209.7
32 2026-08-24 13:33 639231745628278877
323 ms 148.113.209.7
31 2026-08-24 13:16 639231735407682062
183 ms 148.113.209.7
30 2026-08-24 12:23 639231703815441688
5 ms 148.113.209.7
29 2026-08-24 12:07 639231693747052549
7 ms 148.113.209.7
28 2026-08-24 11:50 639231683712487276
324 ms 148.113.209.7
27 2026-08-24 11:33 639231673513573868
327 ms 148.113.209.7
26 2026-08-24 10:40 639231641791249939
3 ms 148.113.209.7
25 2026-08-24 10:23 639231631866211033
3 ms 148.113.209.7
24 2026-08-24 10:07 639231621644955316
4 ms 148.113.209.7
23 2026-08-24 09:50 639231611478799259
330 ms 148.113.209.7
22 2026-08-24 08:57 639231579923718211
3 ms 148.113.209.7
21 2026-08-24 08:40 639231569810702936
6 ms 148.113.209.7
20 2026-08-24 08:23 639231559762411619
306 ms 148.113.209.7
19 2026-08-24 08:06 639231549663595407
152 ms 148.113.209.7
18 2026-08-24 07:14 639231518076817246
2194 ms 148.113.209.7
17 2026-08-24 06:57 639231508078650885
264 ms 148.113.209.7
16 2026-08-24 06:41 639231498210697093
324 ms 148.113.209.7
15 2026-08-24 06:24 639231488109699360
349 ms 148.113.209.7
14 2026-08-24 05:32 639231456772510692
177 ms 148.113.209.7
13 2026-08-24 05:16 639231447084631185
321 ms 148.113.209.7
12 2026-08-24 04:59 639231437208519473
174 ms 148.113.209.7
11 2026-08-24 04:42 639231427209627490
213 ms 148.113.209.7
10 2026-08-24 03:50 639231395791246644
3 ms 148.113.209.7
9 2026-08-24 03:34 639231386075551458
165 ms 148.113.209.7
8 2026-08-24 03:17 639231376208713791
173 ms 148.113.209.7
7 2026-08-24 03:01 639231366170589276
339 ms 148.113.209.7
6 2026-08-24 02:08 639231334732159368
327 ms 148.113.209.7
5 2026-08-24 01:52 639231325035670078
165 ms 148.113.209.7
4 2026-08-24 01:36 639231315132253837
157 ms 148.113.209.7
3 2026-08-24 01:19 639231305014280808
331 ms 148.113.209.7
2 2026-08-24 00:27 639231273779380675
2154 ms 148.113.209.7
1 2026-08-24 00:11 639231264180839154
304 ms 148.113.209.7