DNS response history for ns2.j-cnet.jp

ns2.j-cnet.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-26. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 364 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.j-cnet.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

364 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.178.95.7

Most recently resolved hosting IP on selected date

Successful Responses

30

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.j-cnet.jp

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
30 2026-08-26 09:35 639233329214918079
420 ms 202.178.95.7
29 2026-08-26 09:17 639233318749762337
257 ms 202.178.95.7
28 2026-08-26 09:00 639233308387917838
582 ms 202.178.95.7
27 2026-08-26 08:43 639233297961740122
275 ms 202.178.95.7
26 2026-08-26 08:25 639233287487159094
565 ms 202.178.95.7
25 2026-08-26 08:08 639233276995531707
302 ms 202.178.95.7
24 2026-08-26 07:50 639233266521568229
10 ms 202.178.95.7
23 2026-08-26 07:33 639233256081047431
7 ms 202.178.95.7
22 2026-08-26 06:39 639233223620132921
553 ms 202.178.95.7
21 2026-08-26 06:21 639233213287814244
543 ms 202.178.95.7
20 2026-08-26 06:04 639233202925983161
558 ms 202.178.95.7
19 2026-08-26 05:47 639233192644780696
20 ms 202.178.95.7
18 2026-08-26 05:30 639233182401183833
3 ms 202.178.95.7
17 2026-08-26 05:13 639233172074181051
567 ms 202.178.95.7
16 2026-08-26 04:55 639233161808421455
12 ms 202.178.95.7
15 2026-08-26 04:38 639233151357344052
289 ms 202.178.95.7
14 2026-08-26 04:21 639233141034116946
559 ms 202.178.95.7
13 2026-08-26 04:04 639233130828334142
547 ms 202.178.95.7
12 2026-08-26 03:47 639233120373450007
564 ms 202.178.95.7
11 2026-08-26 03:29 639233110066216193
9 ms 202.178.95.7
10 2026-08-26 02:36 639233078065410564
274 ms 202.178.95.7
9 2026-08-26 02:19 639233067787457832
2 ms 202.178.95.7
8 2026-08-26 02:02 639233057501801162
560 ms 202.178.95.7
7 2026-08-26 01:45 639233047089431703
9 ms 202.178.95.7
6 2026-08-26 01:27 639233036754790688
555 ms 202.178.95.7
5 2026-08-26 01:10 639233026412602472
575 ms 202.178.95.7
4 2026-08-26 00:53 639233016064066127
587 ms 202.178.95.7
3 2026-08-26 00:36 639233005922655772
572 ms 202.178.95.7
2 2026-08-26 00:19 639232995672256907
567 ms 202.178.95.7
1 2026-08-26 00:01 639232985300872416
562 ms 202.178.95.7