DNS response history for ns2.hanzadeparkhotel.com

ns2.hanzadeparkhotel.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 39 DNS check records, 38 successful responses, 1 failed responses, and 454 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.hanzadeparkhotel.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

454 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

187.77.81.41

Most recently resolved hosting IP on selected date

Successful Responses

38

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 ns2.hanzadeparkhotel.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
39 2026-08-26 12:57 639233455747096265
46 ms 187.77.81.41
38 2026-08-26 12:40 639233445367152284
10 ms 187.77.81.41
37 2026-08-26 12:23 639233434974187439
14 ms 187.77.81.41
36 2026-08-26 12:05 639233424567558554
45 ms 187.77.81.41
35 2026-08-26 11:48 639233414056832719
39 ms 187.77.81.41
34 2026-08-26 11:30 639233403515141099
53 ms 187.77.81.41
33 2026-08-26 10:36 639233370841350248
35 ms 187.77.81.41
32 2026-08-26 10:18 639233360361507238
4056 ms 187.77.81.41
31 2026-08-26 10:01 639233350067824371
2027 ms 187.77.81.41
30 2026-08-26 09:44 639233339545274518
24 ms 187.77.81.41
29 2026-08-26 09:26 639233329214918079
53 ms 187.77.81.41
28 2026-08-26 09:09 639233318749762337
20 ms 187.77.81.41
27 2026-08-26 08:52 639233308387917838
17 ms 187.77.81.41
26 2026-08-26 08:34 639233297961740122
23 ms 187.77.81.41
25 2026-08-26 08:17 639233287487159094
68 ms 187.77.81.41
24 2026-08-26 07:59 639233276995531707
9 ms 187.77.81.41
23 2026-08-26 07:42 639233266521568229
25 ms 187.77.81.41
22 2026-08-26 07:25 639233256081047431
26 ms 187.77.81.41
21 2026-08-26 06:31 639233223620132921
9 ms 187.77.81.41
20 2026-08-26 06:13 639233213287814244
24 ms 187.77.81.41
19 2026-08-26 05:56 639233202925983161
20 ms 187.77.81.41
18 2026-08-26 05:39 639233192644780696
-
17 2026-08-26 05:22 639233182401183833
8 ms 187.77.81.41
16 2026-08-26 05:05 639233172074181051
70 ms 187.77.81.41
15 2026-08-26 04:47 639233161808421455
46 ms 187.77.81.41
14 2026-08-26 04:30 639233151357344052
29 ms 187.77.81.41
13 2026-08-26 04:13 639233141034116946
39 ms 187.77.81.41
12 2026-08-26 03:56 639233130828334142
47 ms 187.77.81.41
11 2026-08-26 03:38 639233120373450007
2008 ms 187.77.81.41
10 2026-08-26 03:21 639233110066216193
2021 ms 187.77.81.41
9 2026-08-26 02:28 639233078065410564
24 ms 187.77.81.41
8 2026-08-26 02:11 639233067787457832
10 ms 187.77.81.41
7 2026-08-26 01:54 639233057501801162
27 ms 187.77.81.41
6 2026-08-26 01:36 639233047089431703
2008 ms 187.77.81.41
5 2026-08-26 01:19 639233036754790688
15 ms 187.77.81.41
4 2026-08-26 01:02 639233026412602472
4029 ms 187.77.81.41
3 2026-08-26 00:45 639233016064066127
165 ms 187.77.81.41
2 2026-08-26 00:27 639233005922655772
34 ms 187.77.81.41
1 2026-08-26 00:11 639232995672256907
35 ms 187.77.81.41