DNS response history for ns2.dynamedhealthcare.com

ns2.dynamedhealthcare.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 536 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.dynamedhealthcare.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

536 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.99.39.165

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 ns2.dynamedhealthcare.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:03 639231765923559455
49 ms 192.99.39.165
33 2026-08-24 13:47 639231755868832964
2161 ms 192.99.39.165
32 2026-08-24 13:30 639231745628278877
222 ms 192.99.39.165
31 2026-08-24 13:12 639231735407682062
2023 ms 192.99.39.165
30 2026-08-24 12:20 639231703815441688
237 ms 192.99.39.165
29 2026-08-24 12:03 639231693747052549
2232 ms 192.99.39.165
28 2026-08-24 11:46 639231683712487276
224 ms 192.99.39.165
27 2026-08-24 11:29 639231673513573868
218 ms 192.99.39.165
26 2026-08-24 10:36 639231641791249939
231 ms 192.99.39.165
25 2026-08-24 10:20 639231631866211033
234 ms 192.99.39.165
24 2026-08-24 10:03 639231621644955316
30 ms 192.99.39.165
23 2026-08-24 09:46 639231611478799259
2105 ms 192.99.39.165
22 2026-08-24 08:53 639231579923718211
214 ms 192.99.39.165
21 2026-08-24 08:36 639231569810702936
248 ms 192.99.39.165
20 2026-08-24 08:20 639231559762411619
2120 ms 192.99.39.165
19 2026-08-24 08:03 639231549663595407
4 ms 192.99.39.165
18 2026-08-24 07:10 639231518076817246
107 ms 192.99.39.165
17 2026-08-24 06:54 639231508078650885
223 ms 192.99.39.165
16 2026-08-24 06:37 639231498210697093
3 ms 192.99.39.165
15 2026-08-24 06:20 639231488109699360
3 ms 192.99.39.165
14 2026-08-24 05:28 639231456772510692
231 ms 192.99.39.165
13 2026-08-24 05:12 639231447084631185
5 ms 192.99.39.165
12 2026-08-24 04:55 639231437208519473
2 ms 192.99.39.165
11 2026-08-24 04:39 639231427209627490
217 ms 192.99.39.165
10 2026-08-24 03:46 639231395791246644
249 ms 192.99.39.165
9 2026-08-24 03:30 639231386075551458
5 ms 192.99.39.165
8 2026-08-24 03:14 639231376208713791
3 ms 192.99.39.165
7 2026-08-24 02:57 639231366170589276
224 ms 192.99.39.165
6 2026-08-24 02:05 639231334732159368
129 ms 192.99.39.165
5 2026-08-24 01:48 639231325035670078
2121 ms 192.99.39.165
4 2026-08-24 01:32 639231315132253837
108 ms 192.99.39.165
3 2026-08-24 01:15 639231305014280808
2022 ms 192.99.39.165
2 2026-08-24 00:23 639231273779380675
6 ms 192.99.39.165
1 2026-08-24 00:07 639231264180839154
4 ms 192.99.39.165