DNS response history for ns4.cyberhenge.com

ns4.cyberhenge.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 34 DNS check records, 34 successful responses, 0 failed responses, and 222 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 ns4.cyberhenge.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

222 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.45.223.89

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns4.cyberhenge.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
34 2026-08-24 14:06 639231765923559455
7 ms 52.45.223.89
33 2026-08-24 13:50 639231755868832964
2230 ms 52.45.223.89
32 2026-08-24 13:32 639231745628278877
95 ms 52.45.223.89
31 2026-08-24 13:15 639231735407682062
93 ms 52.45.223.89
30 2026-08-24 12:23 639231703815441688
270 ms 52.45.223.89
29 2026-08-24 12:06 639231693747052549
363 ms 52.45.223.89
28 2026-08-24 11:49 639231683712487276
269 ms 52.45.223.89
27 2026-08-24 11:32 639231673513573868
284 ms 52.45.223.89
26 2026-08-24 10:39 639231641791249939
90 ms 52.45.223.89
25 2026-08-24 10:23 639231631866211033
266 ms 52.45.223.89
24 2026-08-24 10:06 639231621644955316
270 ms 52.45.223.89
23 2026-08-24 09:49 639231611478799259
92 ms 52.45.223.89
22 2026-08-24 08:56 639231579923718211
273 ms 52.45.223.89
21 2026-08-24 08:39 639231569810702936
272 ms 52.45.223.89
20 2026-08-24 08:22 639231559762411619
14 ms 52.45.223.89
19 2026-08-24 08:06 639231549663595407
7 ms 52.45.223.89
18 2026-08-24 07:13 639231518076817246
234 ms 52.45.223.89
17 2026-08-24 06:57 639231508078650885
3 ms 52.45.223.89
16 2026-08-24 06:40 639231498210697093
3 ms 52.45.223.89
15 2026-08-24 06:23 639231488109699360
357 ms 52.45.223.89
14 2026-08-24 05:31 639231456772510692
2 ms 52.45.223.89
13 2026-08-24 05:15 639231447084631185
3 ms 52.45.223.89
12 2026-08-24 04:58 639231437208519473
4 ms 52.45.223.89
11 2026-08-24 04:42 639231427209627490
344 ms 52.45.223.89
10 2026-08-24 03:49 639231395791246644
270 ms 52.45.223.89
9 2026-08-24 03:33 639231386075551458
3 ms 52.45.223.89
8 2026-08-24 03:17 639231376208713791
270 ms 52.45.223.89
7 2026-08-24 03:00 639231366170589276
276 ms 52.45.223.89
6 2026-08-24 02:08 639231334732159368
2 ms 52.45.223.89
5 2026-08-24 01:51 639231325035670078
356 ms 52.45.223.89
4 2026-08-24 01:35 639231315132253837
2 ms 52.45.223.89
3 2026-08-24 01:18 639231305014280808
206 ms 52.45.223.89
2 2026-08-24 00:26 639231273779380675
120 ms 52.45.223.89
1 2026-08-24 00:10 639231264180839154
210 ms 52.45.223.89