DNS response history for ns1.japanpornclub.com

ns1.japanpornclub.com 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-09-01. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 287 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.japanpornclub.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

287 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

46.229.169.33

Most recently resolved hosting IP on selected date

Successful Responses

37

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.japanpornclub.com

Showing DNS history for 2026-09-01 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
37 2026-09-01 12:43 639238628486902752
151 ms 46.229.169.33
36 2026-09-01 12:26 639238617906743100
191 ms 46.229.169.33
35 2026-09-01 12:08 639238607506044626
186 ms 46.229.169.33
34 2026-09-01 11:51 639238597040761406
190 ms 46.229.169.33
33 2026-09-01 11:33 639238586261546969
2149 ms 46.229.169.33
32 2026-09-01 11:15 639238575587642333
190 ms 46.229.169.33
31 2026-09-01 10:21 639238543127398267
190 ms 46.229.169.33
30 2026-09-01 10:03 639238532668234016
192 ms 46.229.169.33
29 2026-09-01 09:46 639238522029321761
6 ms 46.229.169.33
28 2026-09-01 09:28 639238511519050351
203 ms 46.229.169.33
27 2026-09-01 09:11 639238500942239673
190 ms 46.229.169.33
26 2026-09-01 08:53 639238490412377398
195 ms 46.229.169.33
25 2026-09-01 08:35 639238479833203021
186 ms 46.229.169.33
24 2026-09-01 08:18 639238469140507479
191 ms 46.229.169.33
23 2026-09-01 08:00 639238458443560361
201 ms 46.229.169.33
22 2026-09-01 07:42 639238447694851502
210 ms 46.229.169.33
21 2026-09-01 07:24 639238436624109087
200 ms 46.229.169.33
20 2026-09-01 07:05 639238425565611335
190 ms 46.229.169.33
19 2026-09-01 06:10 639238392250222581
191 ms 46.229.169.33
18 2026-09-01 05:51 639238381322537831
146 ms 46.229.169.33
17 2026-09-01 05:33 639238370248186084
193 ms 46.229.169.33
16 2026-09-01 05:15 639238359264687845
196 ms 46.229.169.33
15 2026-09-01 04:57 639238348534621818
214 ms 46.229.169.33
14 2026-09-01 04:39 639238337725739433
194 ms 46.229.169.33
13 2026-09-01 04:20 639238326844749368
195 ms 46.229.169.33
12 2026-09-01 04:02 639238315792024737
185 ms 46.229.169.33
11 2026-09-01 03:44 639238304931064768
184 ms 46.229.169.33
10 2026-09-01 03:26 639238294131483803
190 ms 46.229.169.33
9 2026-09-01 03:08 639238283314985519
188 ms 46.229.169.33
8 2026-09-01 02:50 639238272374093187
2097 ms 46.229.169.33
7 2026-09-01 01:56 639238240032549922
98 ms 46.229.169.33
6 2026-09-01 01:38 639238229204177368
186 ms 46.229.169.33
5 2026-09-01 01:20 639238218326150282
184 ms 46.229.169.33
4 2026-09-01 01:02 639238207574700853
184 ms 46.229.169.33
3 2026-09-01 00:43 639238196660283915
186 ms 46.229.169.33
2 2026-09-01 00:25 639238185782358546
183 ms 46.229.169.33
1 2026-09-01 00:07 639238175054391781
197 ms 46.229.169.33