DNS response history for ns1.japanporn.name

ns1.japanporn.name 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 18 DNS check records, 18 successful responses, 0 failed responses, and 59 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 ns1.japanporn.name.
Records on Selected Date

18

Historical checks stored for this nameserver on selected date

Average Latency

59 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 06:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

62.122.168.8

Most recently resolved hosting IP on selected date

Successful Responses

18

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 ns1.japanporn.name

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
18 2026-08-25 06:10 639232346196373643
57 ms 62.122.168.8
17 2026-08-25 05:53 639232336112370741
33 ms 62.122.168.8
16 2026-08-25 05:37 639232326146508970
17 ms 62.122.168.8
15 2026-08-25 05:20 639232316189381720
21 ms 62.122.168.8
14 2026-08-25 05:04 639232306217998913
175 ms 62.122.168.8
13 2026-08-25 04:47 639232296255744174
17 ms 62.122.168.8
12 2026-08-25 04:30 639232286095760789
25 ms 62.122.168.8
11 2026-08-25 04:13 639232276086186273
53 ms 62.122.168.8
10 2026-08-25 03:56 639232265900986425
64 ms 62.122.168.8
9 2026-08-25 03:39 639232255723518075
62 ms 62.122.168.8
8 2026-08-25 03:22 639232245484452890
27 ms 62.122.168.8
7 2026-08-25 03:05 639232235157175331
57 ms 62.122.168.8
6 2026-08-25 02:12 639232203197189095
59 ms 62.122.168.8
5 2026-08-25 01:55 639232192844564298
50 ms 62.122.168.8
4 2026-08-25 01:37 639232182496008942
82 ms 62.122.168.8
3 2026-08-25 01:20 639232172197053132
129 ms 62.122.168.8
2 2026-08-25 00:27 639232140250307418
86 ms 62.122.168.8
1 2026-08-25 00:10 639232129927860324
51 ms 62.122.168.8