DNS response history for ns2.hardcore-japanporn.com

ns2.hardcore-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-26. For this date, NameServerHistory found 24 DNS check records, 24 successful responses, 0 failed responses, and 294 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 ns2.hardcore-japanporn.com.
Records on Selected Date

24

Historical checks stored for this nameserver on selected date

Average Latency

294 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 07:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.182.166.191

Most recently resolved hosting IP on selected date

Successful Responses

24

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 ns2.hardcore-japanporn.com

Showing DNS history for 2026-08-26 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
24 2026-08-26 07:48 639233266521568229
338 ms 199.182.166.191
23 2026-08-26 07:31 639233256081047431
361 ms 199.182.166.191
22 2026-08-26 06:37 639233223620132921
337 ms 199.182.166.191
21 2026-08-26 06:20 639233213287814244
364 ms 199.182.166.191
20 2026-08-26 06:02 639233202925983161
347 ms 199.182.166.191
19 2026-08-26 05:45 639233192644780696
345 ms 199.182.166.191
18 2026-08-26 05:28 639233182401183833
175 ms 199.182.166.191
17 2026-08-26 05:11 639233172074181051
332 ms 199.182.166.191
16 2026-08-26 04:54 639233161808421455
183 ms 199.182.166.191
15 2026-08-26 04:36 639233151357344052
324 ms 199.182.166.191
14 2026-08-26 04:19 639233141034116946
314 ms 199.182.166.191
13 2026-08-26 04:02 639233130828334142
375 ms 199.182.166.191
12 2026-08-26 03:45 639233120373450007
322 ms 199.182.166.191
11 2026-08-26 03:27 639233110066216193
163 ms 199.182.166.191
10 2026-08-26 02:34 639233078065410564
176 ms 199.182.166.191
9 2026-08-26 02:17 639233067787457832
344 ms 199.182.166.191
8 2026-08-26 02:00 639233057501801162
154 ms 199.182.166.191
7 2026-08-26 01:43 639233047089431703
333 ms 199.182.166.191
6 2026-08-26 01:25 639233036754790688
337 ms 199.182.166.191
5 2026-08-26 01:08 639233026412602472
352 ms 199.182.166.191
4 2026-08-26 00:51 639233016064066127
335 ms 199.182.166.191
3 2026-08-26 00:34 639233005922655772
3 ms 199.182.166.191
2 2026-08-26 00:17 639232995672256907
367 ms 199.182.166.191
1 2026-08-26 00:00 639232985300872416
363 ms 199.182.166.191