DNS response history for ns2.hassanbcs.com

ns2.hassanbcs.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 33 DNS check records, 32 successful responses, 1 failed responses, and 206 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.hassanbcs.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

206 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:36

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

32

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.hassanbcs.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
33 2026-08-26 10:36 639233370841350248
2090 ms 78.135.79.55
32 2026-08-26 10:19 639233360361507238
92 ms 78.135.79.55
31 2026-08-26 10:02 639233350067824371
2065 ms 78.135.79.55
30 2026-08-26 09:44 639233339545274518
84 ms 78.135.79.55
29 2026-08-26 09:27 639233329214918079
43 ms 78.135.79.55
28 2026-08-26 09:09 639233318749762337
82 ms 78.135.79.55
27 2026-08-26 08:52 639233308387917838
98 ms 78.135.79.55
26 2026-08-26 08:35 639233297961740122
82 ms 78.135.79.55
25 2026-08-26 08:17 639233287487159094
7 ms 78.135.79.55
24 2026-08-26 08:00 639233276995531707
72 ms 78.135.79.55
23 2026-08-26 07:42 639233266521568229
53 ms 78.135.79.55
22 2026-08-26 07:25 639233256081047431
83 ms 78.135.79.55
21 2026-08-26 06:31 639233223620132921
74 ms 78.135.79.55
20 2026-08-26 06:14 639233213287814244
16 ms 78.135.79.55
19 2026-08-26 05:56 639233202925983161
85 ms 78.135.79.55
18 2026-08-26 05:39 639233192644780696
89 ms 78.135.79.55
17 2026-08-26 05:22 639233182401183833
53 ms 78.135.79.55
16 2026-08-26 05:05 639233172074181051
81 ms 78.135.79.55
15 2026-08-26 04:48 639233161808421455
202 ms 78.135.79.55
14 2026-08-26 04:30 639233151357344052
82 ms 78.135.79.55
13 2026-08-26 04:13 639233141034116946
11 ms 78.135.79.55
12 2026-08-26 03:56 639233130828334142
85 ms 78.135.79.55
11 2026-08-26 03:39 639233120373450007
106 ms 78.135.79.55
10 2026-08-26 03:21 639233110066216193
110 ms 78.135.79.55
9 2026-08-26 02:28 639233078065410564
78 ms 78.135.79.55
8 2026-08-26 02:11 639233067787457832
80 ms 78.135.79.55
7 2026-08-26 01:54 639233057501801162
163 ms 78.135.79.55
6 2026-08-26 01:37 639233047089431703
110 ms 78.135.79.55
5 2026-08-26 01:19 639233036754790688
80 ms 78.135.79.55
4 2026-08-26 01:02 639233026412602472
-
3 2026-08-26 00:45 639233016064066127
97 ms 78.135.79.55
2 2026-08-26 00:28 639233005922655772
80 ms 78.135.79.55
1 2026-08-26 00:11 639232995672256907
44 ms 78.135.79.55