DNS response history for www.4healthplans.net

www.4healthplans.net 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 218 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 www.4healthplans.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

218 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.17.116.163

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 www.4healthplans.net

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:11 639234253963286387
166 ms 209.17.116.163
34 2026-08-27 10:53 639234243654907465
326 ms 209.17.116.163
33 2026-08-27 10:36 639234233269654413
49 ms 209.17.116.163
32 2026-08-27 10:19 639234222943951923
291 ms 209.17.116.163
31 2026-08-27 10:02 639234212558002823
170 ms 209.17.116.163
30 2026-08-27 09:44 639234202117531850
10 ms 209.17.116.163
29 2026-08-27 09:27 639234191649612722
308 ms 209.17.116.163
28 2026-08-27 09:09 639234181105879568
156 ms 209.17.116.163
27 2026-08-27 08:52 639234170713214496
37 ms 209.17.116.163
26 2026-08-27 08:35 639234160341037652
313 ms 209.17.116.163
25 2026-08-27 08:17 639234149799404224
164 ms 209.17.116.163
24 2026-08-27 08:00 639234139553286469
163 ms 209.17.116.163
23 2026-08-27 07:06 639234107183588293
213 ms 209.17.116.163
22 2026-08-27 06:49 639234096905435724
134 ms 209.17.116.163
21 2026-08-27 06:32 639234086579410775
293 ms 209.17.116.163
20 2026-08-27 06:14 639234076291157956
48 ms 209.17.116.163
19 2026-08-27 05:57 639234065981939454
142 ms 209.17.116.163
18 2026-08-27 05:40 639234055548642997
249 ms 209.17.116.163
17 2026-08-27 05:23 639234045267979603
226 ms 209.17.116.163
16 2026-08-27 05:06 639234034999717463
153 ms 209.17.116.163
15 2026-08-27 04:49 639234024739225358
174 ms 209.17.116.163
14 2026-08-27 04:31 639234014311170162
182 ms 209.17.116.163
13 2026-08-27 04:14 639234003806017640
274 ms 209.17.116.163
12 2026-08-27 03:56 639233993356203030
290 ms 209.17.116.163
11 2026-08-27 03:03 639233961301716608
170 ms 209.17.116.163
10 2026-08-27 02:46 639233950834200647
198 ms 209.17.116.163
9 2026-08-27 02:28 639233940431849026
537 ms 209.17.116.163
8 2026-08-27 02:11 639233930110596398
1130 ms 209.17.116.163
7 2026-08-27 01:54 639233919705434540
140 ms 209.17.116.163
6 2026-08-27 01:37 639233909452807845
130 ms 209.17.116.163
5 2026-08-27 01:19 639233899096420820
174 ms 209.17.116.163
4 2026-08-27 01:02 639233888707824939
127 ms 209.17.116.163
3 2026-08-27 00:45 639233878461203802
249 ms 209.17.116.163
2 2026-08-27 00:28 639233868060868209
126 ms 209.17.116.163
1 2026-08-27 00:10 639233857450922991
132 ms 209.17.116.163