DNS response history for ns2.futuring.one

ns2.futuring.one 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 388 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.futuring.one.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

388 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.126.127.83

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.futuring.one

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:42 639233297961740122
460 ms 209.126.127.83
26 2026-08-26 08:25 639233287487159094
476 ms 209.126.127.83
25 2026-08-26 08:08 639233276995531707
468 ms 209.126.127.83
24 2026-08-26 07:50 639233266521568229
466 ms 209.126.127.83
23 2026-08-26 07:32 639233256081047431
469 ms 209.126.127.83
22 2026-08-26 06:38 639233223620132921
469 ms 209.126.127.83
21 2026-08-26 06:21 639233213287814244
467 ms 209.126.127.83
20 2026-08-26 06:04 639233202925983161
235 ms 209.126.127.83
19 2026-08-26 05:47 639233192644780696
463 ms 209.126.127.83
18 2026-08-26 05:29 639233182401183833
118 ms 209.126.127.83
17 2026-08-26 05:13 639233172074181051
115 ms 209.126.127.83
16 2026-08-26 04:55 639233161808421455
483 ms 209.126.127.83
15 2026-08-26 04:38 639233151357344052
461 ms 209.126.127.83
14 2026-08-26 04:21 639233141034116946
461 ms 209.126.127.83
13 2026-08-26 04:04 639233130828334142
467 ms 209.126.127.83
12 2026-08-26 03:46 639233120373450007
466 ms 209.126.127.83
11 2026-08-26 03:29 639233110066216193
461 ms 209.126.127.83
10 2026-08-26 02:36 639233078065410564
230 ms 209.126.127.83
9 2026-08-26 02:19 639233067787457832
452 ms 209.126.127.83
8 2026-08-26 02:01 639233057501801162
114 ms 209.126.127.83
7 2026-08-26 01:44 639233047089431703
454 ms 209.126.127.83
6 2026-08-26 01:27 639233036754790688
117 ms 209.126.127.83
5 2026-08-26 01:10 639233026412602472
483 ms 209.126.127.83
4 2026-08-26 00:52 639233016064066127
462 ms 209.126.127.83
3 2026-08-26 00:35 639233005922655772
467 ms 209.126.127.83
2 2026-08-26 00:18 639232995672256907
235 ms 209.126.127.83
1 2026-08-26 00:01 639232985300872416
461 ms 209.126.127.83