DNS response history for lynx.fujikyu.co.jp

lynx.fujikyu.co.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 33 DNS check records, 33 successful responses, 0 failed responses, and 471 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 lynx.fujikyu.co.jp.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

471 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.5.121.161

Most recently resolved hosting IP on selected date

Successful Responses

33

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 lynx.fujikyu.co.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
33 2026-08-25 11:50 639232545839529039
580 ms 211.5.121.161
32 2026-08-25 11:32 639232535349285207
304 ms 211.5.121.161
31 2026-08-25 11:15 639232524938080723
295 ms 211.5.121.161
30 2026-08-25 10:21 639232492740373468
573 ms 211.5.121.161
29 2026-08-25 10:04 639232482235303141
577 ms 211.5.121.161
28 2026-08-25 09:46 639232471861770303
581 ms 211.5.121.161
27 2026-08-25 09:29 639232461630217327
286 ms 211.5.121.161
26 2026-08-25 09:12 639232451282965990
558 ms 211.5.121.161
25 2026-08-25 08:55 639232440814614938
290 ms 211.5.121.161
24 2026-08-25 08:37 639232430410720425
287 ms 211.5.121.161
23 2026-08-25 08:20 639232420003096185
279 ms 211.5.121.161
22 2026-08-25 08:03 639232409467287444
296 ms 211.5.121.161
21 2026-08-25 07:45 639232399077195997
279 ms 211.5.121.161
20 2026-08-25 07:28 639232388731528337
614 ms 211.5.121.161
19 2026-08-25 07:10 639232378288598612
837 ms 211.5.121.161
18 2026-08-25 06:17 639232346196373643
287 ms 211.5.121.161
17 2026-08-25 06:00 639232336112370741
568 ms 211.5.121.161
16 2026-08-25 05:43 639232326146508970
3 ms 211.5.121.161
15 2026-08-25 05:27 639232316189381720
2035 ms 211.5.121.161
14 2026-08-25 05:10 639232306217998913
809 ms 211.5.121.161
13 2026-08-25 04:53 639232296255744174
298 ms 211.5.121.161
12 2026-08-25 04:37 639232286095760789
564 ms 211.5.121.161
11 2026-08-25 04:20 639232276086186273
2 ms 211.5.121.161
10 2026-08-25 04:03 639232265900986425
565 ms 211.5.121.161
9 2026-08-25 03:46 639232255723518075
279 ms 211.5.121.161
8 2026-08-25 03:29 639232245484452890
831 ms 211.5.121.161
7 2026-08-25 03:12 639232235157175331
293 ms 211.5.121.161
6 2026-08-25 02:18 639232203197189095
560 ms 211.5.121.161
5 2026-08-25 02:01 639232192844564298
353 ms 211.5.121.161
4 2026-08-25 01:44 639232182496008942
547 ms 211.5.121.161
3 2026-08-25 01:27 639232172197053132
294 ms 211.5.121.161
2 2026-08-25 00:33 639232140250307418
3 ms 211.5.121.161
1 2026-08-25 00:17 639232129927860324
605 ms 211.5.121.161