DNS response history for venus.f-com.jp

venus.f-com.jp 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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 1647 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 venus.f-com.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

1647 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.214.240.33

Most recently resolved hosting IP on selected date

Successful Responses

30

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 venus.f-com.jp

Showing DNS history for 2026-08-25 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
30 2026-08-25 10:05 639232482235303141
1543 ms 61.214.240.33
29 2026-08-25 09:47 639232471861770303
1200 ms 61.214.240.33
28 2026-08-25 09:30 639232461630217327
1195 ms 61.214.240.33
27 2026-08-25 09:13 639232451282965990
1199 ms 61.214.240.33
26 2026-08-25 08:55 639232440814614938
2031 ms 61.214.240.33
25 2026-08-25 08:38 639232430410720425
2009 ms 61.214.240.33
24 2026-08-25 08:21 639232420003096185
2032 ms 61.214.240.33
23 2026-08-25 08:03 639232409467287444
2032 ms 61.214.240.33
22 2026-08-25 07:46 639232399077195997
1197 ms 61.214.240.33
21 2026-08-25 07:28 639232388731528337
1216 ms 61.214.240.33
20 2026-08-25 07:11 639232378288598612
3847 ms 61.214.240.33
19 2026-08-25 06:17 639232346196373643
1197 ms 61.214.240.33
18 2026-08-25 06:00 639232336112370741
2032 ms 61.214.240.33
17 2026-08-25 05:44 639232326146508970
1223 ms 61.214.240.33
16 2026-08-25 05:27 639232316189381720
523 ms 61.214.240.33
15 2026-08-25 05:11 639232306217998913
3 ms 61.214.240.33
14 2026-08-25 04:54 639232296255744174
2363 ms 61.214.240.33
13 2026-08-25 04:37 639232286095760789
3 ms 61.214.240.33
12 2026-08-25 04:20 639232276086186273
3 ms 61.214.240.33
11 2026-08-25 04:04 639232265900986425
3 ms 61.214.240.33
10 2026-08-25 03:47 639232255723518075
2008 ms 61.214.240.33
9 2026-08-25 03:30 639232245484452890
3785 ms 61.214.240.33
8 2026-08-25 03:13 639232235157175331
2008 ms 61.214.240.33
7 2026-08-25 02:19 639232203197189095
2580 ms 61.214.240.33
6 2026-08-25 02:02 639232192844564298
2008 ms 61.214.240.33
5 2026-08-25 01:45 639232182496008942
2007 ms 61.214.240.33
4 2026-08-25 01:27 639232172197053132
2007 ms 61.214.240.33
3 2026-08-25 00:34 639232140250307418
1188 ms 61.214.240.33
2 2026-08-25 00:17 639232129927860324
3779 ms 61.214.240.33
1 2026-08-25 00:00 639232119551972438
1201 ms 61.214.240.33