DNS response history for ns2.j-times.jp

ns2.j-times.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 36 DNS check records, 36 successful responses, 0 failed responses, and 458 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-times.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

458 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.152.66.60

Most recently resolved hosting IP on selected date

Successful Responses

36

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-times.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
36 2026-08-26 11:56 639233414056832719
554 ms 103.152.66.60
35 2026-08-26 11:38 639233403515141099
543 ms 103.152.66.60
34 2026-08-26 10:44 639233370841350248
533 ms 103.152.66.60
33 2026-08-26 10:27 639233360361507238
5 ms 103.152.66.60
32 2026-08-26 10:09 639233350067824371
3 ms 103.152.66.60
31 2026-08-26 09:52 639233339545274518
4 ms 103.152.66.60
30 2026-08-26 09:34 639233329214918079
2265 ms 103.152.66.60
29 2026-08-26 09:17 639233318749762337
413 ms 103.152.66.60
28 2026-08-26 09:00 639233308387917838
3 ms 103.152.66.60
27 2026-08-26 08:43 639233297961740122
2259 ms 103.152.66.60
26 2026-08-26 08:25 639233287487159094
2 ms 103.152.66.60
25 2026-08-26 08:08 639233276995531707
570 ms 103.152.66.60
24 2026-08-26 07:50 639233266521568229
4 ms 103.152.66.60
23 2026-08-26 07:33 639233256081047431
570 ms 103.152.66.60
22 2026-08-26 06:39 639233223620132921
4 ms 103.152.66.60
21 2026-08-26 06:21 639233213287814244
280 ms 103.152.66.60
20 2026-08-26 06:04 639233202925983161
2 ms 103.152.66.60
19 2026-08-26 05:47 639233192644780696
555 ms 103.152.66.60
18 2026-08-26 05:30 639233182401183833
573 ms 103.152.66.60
17 2026-08-26 05:13 639233172074181051
582 ms 103.152.66.60
16 2026-08-26 04:55 639233161808421455
562 ms 103.152.66.60
15 2026-08-26 04:38 639233151357344052
560 ms 103.152.66.60
14 2026-08-26 04:21 639233141034116946
564 ms 103.152.66.60
13 2026-08-26 04:04 639233130828334142
572 ms 103.152.66.60
12 2026-08-26 03:47 639233120373450007
565 ms 103.152.66.60
11 2026-08-26 03:29 639233110066216193
558 ms 103.152.66.60
10 2026-08-26 02:36 639233078065410564
2 ms 103.152.66.60
9 2026-08-26 02:19 639233067787457832
3 ms 103.152.66.60
8 2026-08-26 02:02 639233057501801162
3 ms 103.152.66.60
7 2026-08-26 01:44 639233047089431703
2278 ms 103.152.66.60
6 2026-08-26 01:27 639233036754790688
3 ms 103.152.66.60
5 2026-08-26 01:10 639233026412602472
557 ms 103.152.66.60
4 2026-08-26 00:53 639233016064066127
3 ms 103.152.66.60
3 2026-08-26 00:35 639233005922655772
539 ms 103.152.66.60
2 2026-08-26 00:18 639232995672256907
4 ms 103.152.66.60
1 2026-08-26 00:01 639232985300872416
3 ms 103.152.66.60