DNS response history for ns2.futurohr.com

ns2.futurohr.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 27 DNS check records, 27 successful responses, 0 failed responses, and 195 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.futurohr.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

195 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.88.73.168

Most recently resolved hosting IP on selected date

Successful Responses

27

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.futurohr.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
27 2026-08-26 08:47 639233308387917838
60 ms 23.88.73.168
26 2026-08-26 08:30 639233297961740122
32 ms 23.88.73.168
25 2026-08-26 08:13 639233287487159094
54 ms 23.88.73.168
24 2026-08-26 07:55 639233276995531707
53 ms 23.88.73.168
23 2026-08-26 07:38 639233266521568229
2011 ms 23.88.73.168
22 2026-08-26 07:20 639233256081047431
68 ms 23.88.73.168
21 2026-08-26 06:26 639233223620132921
68 ms 23.88.73.168
20 2026-08-26 06:09 639233213287814244
61 ms 23.88.73.168
19 2026-08-26 05:52 639233202925983161
2034 ms 23.88.73.168
18 2026-08-26 05:35 639233192644780696
33 ms 23.88.73.168
17 2026-08-26 05:17 639233182401183833
12 ms 23.88.73.168
16 2026-08-26 05:00 639233172074181051
71 ms 23.88.73.168
15 2026-08-26 04:43 639233161808421455
51 ms 23.88.73.168
14 2026-08-26 04:26 639233151357344052
68 ms 23.88.73.168
13 2026-08-26 04:08 639233141034116946
31 ms 23.88.73.168
12 2026-08-26 03:51 639233130828334142
49 ms 23.88.73.168
11 2026-08-26 03:34 639233120373450007
76 ms 23.88.73.168
10 2026-08-26 03:17 639233110066216193
41 ms 23.88.73.168
9 2026-08-26 02:24 639233078065410564
45 ms 23.88.73.168
8 2026-08-26 02:06 639233067787457832
16 ms 23.88.73.168
7 2026-08-26 01:49 639233057501801162
57 ms 23.88.73.168
6 2026-08-26 01:32 639233047089431703
52 ms 23.88.73.168
5 2026-08-26 01:15 639233036754790688
60 ms 23.88.73.168
4 2026-08-26 00:57 639233026412602472
29 ms 23.88.73.168
3 2026-08-26 00:40 639233016064066127
50 ms 23.88.73.168
2 2026-08-26 00:23 639233005922655772
41 ms 23.88.73.168
1 2026-08-26 00:06 639232995672256907
45 ms 23.88.73.168