DNS response history for ns1.dirty-japanporn.com

ns1.dirty-japanporn.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-08-24. For this date, NameServerHistory found 28 DNS check records, 27 successful responses, 1 failed responses, and 521 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.dirty-japanporn.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

521 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.182.166.175

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.dirty-japanporn.com

Showing DNS history for 2026-08-24 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-24 11:51 639231683712487276
159 ms 199.182.166.175
27 2026-08-24 11:34 639231673513573868
2188 ms 199.182.166.175
26 2026-08-24 10:41 639231641791249939
341 ms 199.182.166.175
25 2026-08-24 10:25 639231631866211033
329 ms 199.182.166.175
24 2026-08-24 10:08 639231621644955316
318 ms 199.182.166.175
23 2026-08-24 09:51 639231611478799259
349 ms 199.182.166.175
22 2026-08-24 08:58 639231579923718211
341 ms 199.182.166.175
21 2026-08-24 08:42 639231569810702936
422 ms 199.182.166.175
20 2026-08-24 08:25 639231559762411619
470 ms 199.182.166.175
19 2026-08-24 08:08 639231549663595407
334 ms 199.182.166.175
18 2026-08-24 07:15 639231518076817246
315 ms 199.182.166.175
17 2026-08-24 06:59 639231508078650885
343 ms 199.182.166.175
16 2026-08-24 06:42 639231498210697093
334 ms 199.182.166.175
15 2026-08-24 06:25 639231488109699360
345 ms 199.182.166.175
14 2026-08-24 05:33 639231456772510692
2276 ms 199.182.166.175
13 2026-08-24 05:17 639231447084631185
194 ms 199.182.166.175
12 2026-08-24 05:00 639231437208519473
154 ms 199.182.166.175
11 2026-08-24 04:44 639231427209627490
264 ms 199.182.166.175
10 2026-08-24 03:51 639231395791246644
-
9 2026-08-24 03:35 639231386075551458
376 ms 199.182.166.175
8 2026-08-24 03:19 639231376208713791
158 ms 199.182.166.175
7 2026-08-24 03:02 639231366170589276
334 ms 199.182.166.175
6 2026-08-24 02:10 639231334732159368
368 ms 199.182.166.175
5 2026-08-24 01:53 639231325035670078
189 ms 199.182.166.175
4 2026-08-24 01:37 639231315132253837
329 ms 199.182.166.175
3 2026-08-24 01:20 639231305014280808
341 ms 199.182.166.175
2 2026-08-24 00:28 639231273779380675
322 ms 199.182.166.175
1 2026-08-24 00:12 639231264180839154
2162 ms 199.182.166.175