DNS response history for ns2.futuregeological.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

223 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.215.171.153

Most recently resolved hosting IP on selected date

Successful Responses

32

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.futuregeological.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
32 2026-08-26 10:08 639233350067824371
299 ms 162.215.171.153
31 2026-08-26 09:51 639233339545274518
292 ms 162.215.171.153
30 2026-08-26 09:33 639233329214918079
38 ms 162.215.171.153
29 2026-08-26 09:16 639233318749762337
317 ms 162.215.171.153
28 2026-08-26 08:58 639233308387917838
160 ms 162.215.171.153
27 2026-08-26 08:41 639233297961740122
332 ms 162.215.171.153
26 2026-08-26 08:24 639233287487159094
159 ms 162.215.171.153
25 2026-08-26 08:06 639233276995531707
318 ms 162.215.171.153
24 2026-08-26 07:49 639233266521568229
293 ms 162.215.171.153
23 2026-08-26 07:31 639233256081047431
304 ms 162.215.171.153
22 2026-08-26 06:37 639233223620132921
291 ms 162.215.171.153
21 2026-08-26 06:20 639233213287814244
145 ms 162.215.171.153
20 2026-08-26 06:03 639233202925983161
289 ms 162.215.171.153
19 2026-08-26 05:45 639233192644780696
292 ms 162.215.171.153
18 2026-08-26 05:28 639233182401183833
146 ms 162.215.171.153
17 2026-08-26 05:11 639233172074181051
291 ms 162.215.171.153
16 2026-08-26 04:54 639233161808421455
293 ms 162.215.171.153
15 2026-08-26 04:37 639233151357344052
8 ms 162.215.171.153
14 2026-08-26 04:19 639233141034116946
288 ms 162.215.171.153
13 2026-08-26 04:02 639233130828334142
290 ms 162.215.171.153
12 2026-08-26 03:45 639233120373450007
145 ms 162.215.171.153
11 2026-08-26 03:28 639233110066216193
147 ms 162.215.171.153
10 2026-08-26 02:34 639233078065410564
287 ms 162.215.171.153
9 2026-08-26 02:17 639233067787457832
288 ms 162.215.171.153
8 2026-08-26 02:00 639233057501801162
145 ms 162.215.171.153
7 2026-08-26 01:43 639233047089431703
288 ms 162.215.171.153
6 2026-08-26 01:26 639233036754790688
290 ms 162.215.171.153
5 2026-08-26 01:08 639233026412602472
323 ms 162.215.171.153
4 2026-08-26 00:51 639233016064066127
23 ms 162.215.171.153
3 2026-08-26 00:34 639233005922655772
33 ms 162.215.171.153
2 2026-08-26 00:17 639232995672256907
291 ms 162.215.171.153
1 2026-08-26 00:00 639232985300872416
31 ms 162.215.171.153