DNS response history for ns1.dynamichealthllc.com

ns1.dynamichealthllc.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 461 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 ns1.dynamichealthllc.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

461 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.167.170.250

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 ns1.dynamichealthllc.com

Showing DNS history for 2026-08-27 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-27 11:12 639234253963286387
238 ms 69.167.170.250
34 2026-08-27 10:54 639234243654907465
230 ms 69.167.170.250
33 2026-08-27 10:37 639234233269654413
140 ms 69.167.170.250
32 2026-08-27 10:20 639234222943951923
119 ms 69.167.170.250
31 2026-08-27 10:03 639234212558002823
111 ms 69.167.170.250
30 2026-08-27 09:45 639234202117531850
2129 ms 69.167.170.250
29 2026-08-27 09:28 639234191649612722
240 ms 69.167.170.250
28 2026-08-27 09:10 639234181105879568
2141 ms 69.167.170.250
27 2026-08-27 08:53 639234170713214496
241 ms 69.167.170.250
26 2026-08-27 08:36 639234160341037652
120 ms 69.167.170.250
25 2026-08-27 08:18 639234149799404224
169 ms 69.167.170.250
24 2026-08-27 08:01 639234139553286469
230 ms 69.167.170.250
23 2026-08-27 07:07 639234107183588293
224 ms 69.167.170.250
22 2026-08-27 06:50 639234096905435724
121 ms 69.167.170.250
21 2026-08-27 06:33 639234086579410775
234 ms 69.167.170.250
20 2026-08-27 06:15 639234076291157956
247 ms 69.167.170.250
19 2026-08-27 05:58 639234065981939454
240 ms 69.167.170.250
18 2026-08-27 05:41 639234055548642997
220 ms 69.167.170.250
17 2026-08-27 05:24 639234045267979603
223 ms 69.167.170.250
16 2026-08-27 05:07 639234034999717463
246 ms 69.167.170.250
15 2026-08-27 04:50 639234024739225358
4146 ms 69.167.170.250
14 2026-08-27 04:32 639234014311170162
7 ms 69.167.170.250
13 2026-08-27 04:15 639234003806017640
221 ms 69.167.170.250
12 2026-08-27 03:57 639233993356203030
230 ms 69.167.170.250
11 2026-08-27 03:04 639233961301716608
110 ms 69.167.170.250
10 2026-08-27 02:47 639233950834200647
2007 ms 69.167.170.250
9 2026-08-27 02:29 639233940431849026
236 ms 69.167.170.250
8 2026-08-27 02:12 639233930110596398
159 ms 69.167.170.250
7 2026-08-27 01:55 639233919705434540
228 ms 69.167.170.250
6 2026-08-27 01:38 639233909452807845
226 ms 69.167.170.250
5 2026-08-27 01:20 639233899096420820
238 ms 69.167.170.250
4 2026-08-27 01:03 639233888707824939
229 ms 69.167.170.250
3 2026-08-27 00:46 639233878461203802
110 ms 69.167.170.250
2 2026-08-27 00:29 639233868060868209
7 ms 69.167.170.250
1 2026-08-27 00:11 639233857450922991
115 ms 69.167.170.250