DNS response history for ns.fnet.ne.jp

ns.fnet.ne.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-27. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 579 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 ns.fnet.ne.jp.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

579 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

157.112.116.135

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns.fnet.ne.jp

Showing DNS history for 2026-08-27 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
28 2026-08-27 09:16 639234181105879568
773 ms 157.112.116.135
27 2026-08-27 08:59 639234170713214496
541 ms 157.112.116.135
26 2026-08-27 08:41 639234160341037652
553 ms 157.112.116.135
25 2026-08-27 08:24 639234149799404224
597 ms 157.112.116.135
24 2026-08-27 08:06 639234139553286469
874 ms 157.112.116.135
23 2026-08-27 07:13 639234107183588293
746 ms 157.112.116.135
22 2026-08-27 06:55 639234096905435724
612 ms 157.112.116.135
21 2026-08-27 06:38 639234086579410775
541 ms 157.112.116.135
20 2026-08-27 06:21 639234076291157956
590 ms 157.112.116.135
19 2026-08-27 06:04 639234065981939454
542 ms 157.112.116.135
18 2026-08-27 05:47 639234055548642997
666 ms 157.112.116.135
17 2026-08-27 05:29 639234045267979603
502 ms 157.112.116.135
16 2026-08-27 05:12 639234034999717463
512 ms 157.112.116.135
15 2026-08-27 04:55 639234024739225358
524 ms 157.112.116.135
14 2026-08-27 04:38 639234014311170162
572 ms 157.112.116.135
13 2026-08-27 04:21 639234003806017640
525 ms 157.112.116.135
12 2026-08-27 04:03 639233993356203030
553 ms 157.112.116.135
11 2026-08-27 03:10 639233961301716608
689 ms 157.112.116.135
10 2026-08-27 02:52 639233950834200647
538 ms 157.112.116.135
9 2026-08-27 02:35 639233940431849026
551 ms 157.112.116.135
8 2026-08-27 02:18 639233930110596398
518 ms 157.112.116.135
7 2026-08-27 02:00 639233919705434540
503 ms 157.112.116.135
6 2026-08-27 01:43 639233909452807845
545 ms 157.112.116.135
5 2026-08-27 01:26 639233899096420820
507 ms 157.112.116.135
4 2026-08-27 01:09 639233888707824939
517 ms 157.112.116.135
3 2026-08-27 00:51 639233878461203802
530 ms 157.112.116.135
2 2026-08-27 00:34 639233868060868209
549 ms 157.112.116.135
1 2026-08-27 00:17 639233857450922991
534 ms 157.112.116.135