DNS response history for ns2.hancarbcs.com

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

40

Historical checks stored for this nameserver on selected date

Average Latency

177 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 13:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.135.79.55

Most recently resolved hosting IP on selected date

Successful Responses

40

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.hancarbcs.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
40 2026-08-26 13:13 639233466171592605
80 ms 78.135.79.55
39 2026-08-26 12:56 639233455747096265
48 ms 78.135.79.55
38 2026-08-26 12:38 639233445367152284
44 ms 78.135.79.55
37 2026-08-26 12:21 639233434974187439
101 ms 78.135.79.55
36 2026-08-26 12:04 639233424567558554
51 ms 78.135.79.55
35 2026-08-26 11:46 639233414056832719
111 ms 78.135.79.55
34 2026-08-26 11:29 639233403515141099
9 ms 78.135.79.55
33 2026-08-26 10:34 639233370841350248
48 ms 78.135.79.55
32 2026-08-26 10:17 639233360361507238
95 ms 78.135.79.55
31 2026-08-26 10:00 639233350067824371
97 ms 78.135.79.55
30 2026-08-26 09:42 639233339545274518
173 ms 78.135.79.55
29 2026-08-26 09:25 639233329214918079
64 ms 78.135.79.55
28 2026-08-26 09:08 639233318749762337
14 ms 78.135.79.55
27 2026-08-26 08:50 639233308387917838
2073 ms 78.135.79.55
26 2026-08-26 08:33 639233297961740122
91 ms 78.135.79.55
25 2026-08-26 08:15 639233287487159094
95 ms 78.135.79.55
24 2026-08-26 07:58 639233276995531707
80 ms 78.135.79.55
23 2026-08-26 07:40 639233266521568229
83 ms 78.135.79.55
22 2026-08-26 07:23 639233256081047431
95 ms 78.135.79.55
21 2026-08-26 06:29 639233223620132921
108 ms 78.135.79.55
20 2026-08-26 06:12 639233213287814244
105 ms 78.135.79.55
19 2026-08-26 05:54 639233202925983161
120 ms 78.135.79.55
18 2026-08-26 05:37 639233192644780696
79 ms 78.135.79.55
17 2026-08-26 05:20 639233182401183833
92 ms 78.135.79.55
16 2026-08-26 05:03 639233172074181051
85 ms 78.135.79.55
15 2026-08-26 04:46 639233161808421455
80 ms 78.135.79.55
14 2026-08-26 04:28 639233151357344052
2009 ms 78.135.79.55
13 2026-08-26 04:11 639233141034116946
80 ms 78.135.79.55
12 2026-08-26 03:54 639233130828334142
65 ms 78.135.79.55
11 2026-08-26 03:37 639233120373450007
9 ms 78.135.79.55
10 2026-08-26 03:20 639233110066216193
69 ms 78.135.79.55
9 2026-08-26 02:26 639233078065410564
113 ms 78.135.79.55
8 2026-08-26 02:09 639233067787457832
83 ms 78.135.79.55
7 2026-08-26 01:52 639233057501801162
88 ms 78.135.79.55
6 2026-08-26 01:35 639233047089431703
21 ms 78.135.79.55
5 2026-08-26 01:17 639233036754790688
78 ms 78.135.79.55
4 2026-08-26 01:00 639233026412602472
101 ms 78.135.79.55
3 2026-08-26 00:43 639233016064066127
103 ms 78.135.79.55
2 2026-08-26 00:26 639233005922655772
81 ms 78.135.79.55
1 2026-08-26 00:09 639232995672256907
60 ms 78.135.79.55