DNS response history for ns2.future-interactive.net

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

33

Historical checks stored for this nameserver on selected date

Average Latency

66 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.28.164.107

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.future-interactive.net

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:32 639233370841350248
50 ms 185.28.164.107
32 2026-08-26 10:15 639233360361507238
50 ms 185.28.164.107
31 2026-08-26 09:58 639233350067824371
47 ms 185.28.164.107
30 2026-08-26 09:40 639233339545274518
57 ms 185.28.164.107
29 2026-08-26 09:23 639233329214918079
46 ms 185.28.164.107
28 2026-08-26 09:06 639233318749762337
26 ms 185.28.164.107
27 2026-08-26 08:48 639233308387917838
112 ms 185.28.164.107
26 2026-08-26 08:31 639233297961740122
60 ms 185.28.164.107
25 2026-08-26 08:13 639233287487159094
65 ms 185.28.164.107
24 2026-08-26 07:56 639233276995531707
133 ms 185.28.164.107
23 2026-08-26 07:38 639233266521568229
76 ms 185.28.164.107
22 2026-08-26 07:21 639233256081047431
70 ms 185.28.164.107
21 2026-08-26 06:27 639233223620132921
25 ms 185.28.164.107
20 2026-08-26 06:10 639233213287814244
4 ms 185.28.164.107
19 2026-08-26 05:52 639233202925983161
46 ms 185.28.164.107
18 2026-08-26 05:35 639233192644780696
130 ms 185.28.164.107
17 2026-08-26 05:18 639233182401183833
49 ms 185.28.164.107
16 2026-08-26 05:01 639233172074181051
57 ms 185.28.164.107
15 2026-08-26 04:44 639233161808421455
115 ms 185.28.164.107
14 2026-08-26 04:27 639233151357344052
45 ms 185.28.164.107
13 2026-08-26 04:09 639233141034116946
59 ms 185.28.164.107
12 2026-08-26 03:52 639233130828334142
47 ms 185.28.164.107
11 2026-08-26 03:35 639233120373450007
38 ms 185.28.164.107
10 2026-08-26 03:18 639233110066216193
111 ms 185.28.164.107
9 2026-08-26 02:24 639233078065410564
95 ms 185.28.164.107
8 2026-08-26 02:07 639233067787457832
46 ms 185.28.164.107
7 2026-08-26 01:50 639233057501801162
47 ms 185.28.164.107
6 2026-08-26 01:33 639233047089431703
47 ms 185.28.164.107
5 2026-08-26 01:16 639233036754790688
182 ms 185.28.164.107
4 2026-08-26 00:58 639233026412602472
74 ms 185.28.164.107
3 2026-08-26 00:41 639233016064066127
23 ms 185.28.164.107
2 2026-08-26 00:24 639233005922655772
103 ms 185.28.164.107
1 2026-08-26 00:07 639232995672256907
56 ms 185.28.164.107