DNS response history for ns.pyonpyon.jp

ns.pyonpyon.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 539 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.pyonpyon.jp.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

539 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

160.16.85.171

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 ns.pyonpyon.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
544 ms 160.16.85.171
32 2026-08-25 11:32 639232535349285207
562 ms 160.16.85.171
31 2026-08-25 11:15 639232524938080723
6 ms 160.16.85.171
30 2026-08-25 10:21 639232492740373468
4 ms 160.16.85.171
29 2026-08-25 10:04 639232482235303141
3 ms 160.16.85.171
28 2026-08-25 09:46 639232471861770303
526 ms 160.16.85.171
27 2026-08-25 09:29 639232461630217327
549 ms 160.16.85.171
26 2026-08-25 09:12 639232451282965990
2611 ms 160.16.85.171
25 2026-08-25 08:55 639232440814614938
570 ms 160.16.85.171
24 2026-08-25 08:37 639232430410720425
326 ms 160.16.85.171
23 2026-08-25 08:20 639232420003096185
558 ms 160.16.85.171
22 2026-08-25 08:03 639232409467287444
823 ms 160.16.85.171
21 2026-08-25 07:45 639232399077195997
8 ms 160.16.85.171
20 2026-08-25 07:28 639232388731528337
555 ms 160.16.85.171
19 2026-08-25 07:10 639232378288598612
548 ms 160.16.85.171
18 2026-08-25 06:17 639232346196373643
559 ms 160.16.85.171
17 2026-08-25 06:00 639232336112370741
550 ms 160.16.85.171
16 2026-08-25 05:43 639232326146508970
556 ms 160.16.85.171
15 2026-08-25 05:27 639232316189381720
555 ms 160.16.85.171
14 2026-08-25 05:10 639232306217998913
277 ms 160.16.85.171
13 2026-08-25 04:53 639232296255744174
327 ms 160.16.85.171
12 2026-08-25 04:37 639232286095760789
543 ms 160.16.85.171
11 2026-08-25 04:20 639232276086186273
727 ms 160.16.85.171
10 2026-08-25 04:03 639232265900986425
561 ms 160.16.85.171
9 2026-08-25 03:46 639232255723518075
561 ms 160.16.85.171
8 2026-08-25 03:29 639232245484452890
562 ms 160.16.85.171
7 2026-08-25 03:12 639232235157175331
554 ms 160.16.85.171
6 2026-08-25 02:18 639232203197189095
562 ms 160.16.85.171
5 2026-08-25 02:01 639232192844564298
536 ms 160.16.85.171
4 2026-08-25 01:44 639232182496008942
552 ms 160.16.85.171
3 2026-08-25 01:27 639232172197053132
547 ms 160.16.85.171
2 2026-08-25 00:33 639232140250307418
539 ms 160.16.85.171
1 2026-08-25 00:17 639232129927860324
540 ms 160.16.85.171