DNS response history for ns2.furchives.org

ns2.furchives.org 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 29 DNS check records, 29 successful responses, 0 failed responses, and 302 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.furchives.org.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

302 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.30.205.173

Most recently resolved hosting IP on selected date

Successful Responses

29

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.furchives.org

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
29 2026-08-26 09:21 639233318749762337
380 ms 69.30.205.173
28 2026-08-26 09:03 639233308387917838
253 ms 69.30.205.173
27 2026-08-26 08:46 639233297961740122
258 ms 69.30.205.173
26 2026-08-26 08:29 639233287487159094
267 ms 69.30.205.173
25 2026-08-26 08:11 639233276995531707
501 ms 69.30.205.173
24 2026-08-26 07:54 639233266521568229
374 ms 69.30.205.173
23 2026-08-26 07:36 639233256081047431
481 ms 69.30.205.173
22 2026-08-26 06:42 639233223620132921
264 ms 69.30.205.173
21 2026-08-26 06:25 639233213287814244
482 ms 69.30.205.173
20 2026-08-26 06:07 639233202925983161
254 ms 69.30.205.173
19 2026-08-26 05:50 639233192644780696
123 ms 69.30.205.173
18 2026-08-26 05:33 639233182401183833
262 ms 69.30.205.173
17 2026-08-26 05:16 639233172074181051
611 ms 69.30.205.173
16 2026-08-26 04:59 639233161808421455
122 ms 69.30.205.173
15 2026-08-26 04:42 639233151357344052
257 ms 69.30.205.173
14 2026-08-26 04:24 639233141034116946
128 ms 69.30.205.173
13 2026-08-26 04:07 639233130828334142
122 ms 69.30.205.173
12 2026-08-26 03:50 639233120373450007
423 ms 69.30.205.173
11 2026-08-26 03:33 639233110066216193
264 ms 69.30.205.173
10 2026-08-26 02:39 639233078065410564
486 ms 69.30.205.173
9 2026-08-26 02:22 639233067787457832
260 ms 69.30.205.173
8 2026-08-26 02:05 639233057501801162
260 ms 69.30.205.173
7 2026-08-26 01:48 639233047089431703
122 ms 69.30.205.173
6 2026-08-26 01:30 639233036754790688
269 ms 69.30.205.173
5 2026-08-26 01:13 639233026412602472
261 ms 69.30.205.173
4 2026-08-26 00:56 639233016064066127
259 ms 69.30.205.173
3 2026-08-26 00:39 639233005922655772
128 ms 69.30.205.173
2 2026-08-26 00:22 639232995672256907
516 ms 69.30.205.173
1 2026-08-26 00:05 639232985300872416
382 ms 69.30.205.173