DNS response history for ns2.futurehealthconnections.com

ns2.futurehealthconnections.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-26. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 431 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.futurehealthconnections.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

431 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

130.51.23.228

Most recently resolved hosting IP on selected date

Successful Responses

33

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.futurehealthconnections.com

Showing DNS history for 2026-08-26 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
33 2026-08-26 10:41 639233370841350248
9 ms 130.51.23.228
32 2026-08-26 10:24 639233360361507238
297 ms 130.51.23.228
31 2026-08-26 10:06 639233350067824371
2168 ms 130.51.23.228
30 2026-08-26 09:49 639233339545274518
297 ms 130.51.23.228
29 2026-08-26 09:31 639233329214918079
2127 ms 130.51.23.228
28 2026-08-26 09:14 639233318749762337
131 ms 130.51.23.228
27 2026-08-26 08:57 639233308387917838
132 ms 130.51.23.228
26 2026-08-26 08:39 639233297961740122
292 ms 130.51.23.228
25 2026-08-26 08:22 639233287487159094
289 ms 130.51.23.228
24 2026-08-26 08:05 639233276995531707
108 ms 130.51.23.228
23 2026-08-26 07:47 639233266521568229
297 ms 130.51.23.228
22 2026-08-26 07:30 639233256081047431
293 ms 130.51.23.228
21 2026-08-26 06:36 639233223620132921
282 ms 130.51.23.228
20 2026-08-26 06:18 639233213287814244
319 ms 130.51.23.228
19 2026-08-26 06:01 639233202925983161
279 ms 130.51.23.228
18 2026-08-26 05:44 639233192644780696
284 ms 130.51.23.228
17 2026-08-26 05:27 639233182401183833
296 ms 130.51.23.228
16 2026-08-26 05:10 639233172074181051
288 ms 130.51.23.228
15 2026-08-26 04:52 639233161808421455
2157 ms 130.51.23.228
14 2026-08-26 04:35 639233151357344052
172 ms 130.51.23.228
13 2026-08-26 04:18 639233141034116946
292 ms 130.51.23.228
12 2026-08-26 04:01 639233130828334142
301 ms 130.51.23.228
11 2026-08-26 03:44 639233120373450007
291 ms 130.51.23.228
10 2026-08-26 03:26 639233110066216193
296 ms 130.51.23.228
9 2026-08-26 02:33 639233078065410564
292 ms 130.51.23.228
8 2026-08-26 02:16 639233067787457832
291 ms 130.51.23.228
7 2026-08-26 01:59 639233057501801162
292 ms 130.51.23.228
6 2026-08-26 01:41 639233047089431703
298 ms 130.51.23.228
5 2026-08-26 01:24 639233036754790688
305 ms 130.51.23.228
4 2026-08-26 01:07 639233026412602472
284 ms 130.51.23.228
3 2026-08-26 00:50 639233016064066127
297 ms 130.51.23.228
2 2026-08-26 00:33 639233005922655772
284 ms 130.51.23.228
1 2026-08-26 00:15 639232995672256907
177 ms 130.51.23.228