DNS response history for ns2.healthmonitor365.info

ns2.healthmonitor365.info 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 35 DNS check records, 35 successful responses, 0 failed responses, and 357 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.healthmonitor365.info.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

357 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

107.152.33.199

Most recently resolved hosting IP on selected date

Successful Responses

35

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.healthmonitor365.info

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
35 2026-08-24 14:58 639231797631669865
299 ms 107.152.33.199
34 2026-08-24 14:05 639231765923559455
146 ms 107.152.33.199
33 2026-08-24 13:49 639231755868832964
290 ms 107.152.33.199
32 2026-08-24 13:32 639231745628278877
292 ms 107.152.33.199
31 2026-08-24 13:14 639231735407682062
130 ms 107.152.33.199
30 2026-08-24 12:22 639231703815441688
303 ms 107.152.33.199
29 2026-08-24 12:05 639231693747052549
138 ms 107.152.33.199
28 2026-08-24 11:48 639231683712487276
302 ms 107.152.33.199
27 2026-08-24 11:31 639231673513573868
292 ms 107.152.33.199
26 2026-08-24 10:38 639231641791249939
165 ms 107.152.33.199
25 2026-08-24 10:22 639231631866211033
298 ms 107.152.33.199
24 2026-08-24 10:05 639231621644955316
292 ms 107.152.33.199
23 2026-08-24 09:48 639231611478799259
2178 ms 107.152.33.199
22 2026-08-24 08:56 639231579923718211
256 ms 107.152.33.199
21 2026-08-24 08:39 639231569810702936
147 ms 107.152.33.199
20 2026-08-24 08:22 639231559762411619
2116 ms 107.152.33.199
19 2026-08-24 08:05 639231549663595407
306 ms 107.152.33.199
18 2026-08-24 07:12 639231518076817246
430 ms 107.152.33.199
17 2026-08-24 06:56 639231508078650885
149 ms 107.152.33.199
16 2026-08-24 06:39 639231498210697093
165 ms 107.152.33.199
15 2026-08-24 06:23 639231488109699360
3 ms 107.152.33.199
14 2026-08-24 05:30 639231456772510692
118 ms 107.152.33.199
13 2026-08-24 05:14 639231447084631185
5 ms 107.152.33.199
12 2026-08-24 04:58 639231437208519473
3 ms 107.152.33.199
11 2026-08-24 04:41 639231427209627490
2148 ms 107.152.33.199
10 2026-08-24 03:48 639231395791246644
302 ms 107.152.33.199
9 2026-08-24 03:32 639231386075551458
303 ms 107.152.33.199
8 2026-08-24 03:16 639231376208713791
300 ms 107.152.33.199
7 2026-08-24 02:59 639231366170589276
302 ms 107.152.33.199
6 2026-08-24 02:07 639231334732159368
287 ms 107.152.33.199
5 2026-08-24 01:51 639231325035670078
4 ms 107.152.33.199
4 2026-08-24 01:34 639231315132253837
4 ms 107.152.33.199
3 2026-08-24 01:17 639231305014280808
3 ms 107.152.33.199
2 2026-08-24 00:25 639231273779380675
3 ms 107.152.33.199
1 2026-08-24 00:09 639231264180839154
6 ms 107.152.33.199