DNS response history for ns2.healthnewsminute.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

272 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.236.101.148

Most recently resolved hosting IP on selected date

Successful Responses

36

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.healthnewsminute.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
36 2026-08-24 15:15 639231807961539652
232 ms 173.236.101.148
35 2026-08-24 14:58 639231797631669865
247 ms 173.236.101.148
34 2026-08-24 14:05 639231765923559455
5 ms 173.236.101.148
33 2026-08-24 13:48 639231755868832964
228 ms 173.236.101.148
32 2026-08-24 13:31 639231745628278877
226 ms 173.236.101.148
31 2026-08-24 13:14 639231735407682062
231 ms 173.236.101.148
30 2026-08-24 12:21 639231703815441688
140 ms 173.236.101.148
29 2026-08-24 12:05 639231693747052549
137 ms 173.236.101.148
28 2026-08-24 11:48 639231683712487276
113 ms 173.236.101.148
27 2026-08-24 11:31 639231673513573868
163 ms 173.236.101.148
26 2026-08-24 10:38 639231641791249939
3 ms 173.236.101.148
25 2026-08-24 10:21 639231631866211033
227 ms 173.236.101.148
24 2026-08-24 10:05 639231621644955316
233 ms 173.236.101.148
23 2026-08-24 09:48 639231611478799259
6 ms 173.236.101.148
22 2026-08-24 08:55 639231579923718211
118 ms 173.236.101.148
21 2026-08-24 08:38 639231569810702936
230 ms 173.236.101.148
20 2026-08-24 08:21 639231559762411619
226 ms 173.236.101.148
19 2026-08-24 08:04 639231549663595407
124 ms 173.236.101.148
18 2026-08-24 07:12 639231518076817246
2008 ms 173.236.101.148
17 2026-08-24 06:55 639231508078650885
2143 ms 173.236.101.148
16 2026-08-24 06:39 639231498210697093
227 ms 173.236.101.148
15 2026-08-24 06:22 639231488109699360
235 ms 173.236.101.148
14 2026-08-24 05:30 639231456772510692
2 ms 173.236.101.148
13 2026-08-24 05:14 639231447084631185
227 ms 173.236.101.148
12 2026-08-24 04:57 639231437208519473
241 ms 173.236.101.148
11 2026-08-24 04:40 639231427209627490
227 ms 173.236.101.148
10 2026-08-24 03:48 639231395791246644
3 ms 173.236.101.148
9 2026-08-24 03:32 639231386075551458
276 ms 173.236.101.148
8 2026-08-24 03:16 639231376208713791
141 ms 173.236.101.148
7 2026-08-24 02:59 639231366170589276
3 ms 173.236.101.148
6 2026-08-24 02:06 639231334732159368
224 ms 173.236.101.148
5 2026-08-24 01:50 639231325035670078
252 ms 173.236.101.148
4 2026-08-24 01:34 639231315132253837
222 ms 173.236.101.148
3 2026-08-24 01:17 639231305014280808
114 ms 173.236.101.148
2 2026-08-24 00:25 639231273779380675
222 ms 173.236.101.148
1 2026-08-24 00:09 639231264180839154
119 ms 173.236.101.148