DNS response history for dns2.incl.ne.jp

dns2.incl.ne.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 35 DNS check records, 35 successful responses, 0 failed responses, and 642 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 dns2.incl.ne.jp.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

642 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

219.121.225.2

Most recently resolved hosting IP on selected date

Successful Responses

35

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 dns2.incl.ne.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
35 2026-08-26 11:40 639233403515141099
1092 ms 219.121.225.2
34 2026-08-26 10:45 639233370841350248
516 ms 219.121.225.2
33 2026-08-26 10:28 639233360361507238
519 ms 219.121.225.2
32 2026-08-26 10:11 639233350067824371
538 ms 219.121.225.2
31 2026-08-26 09:54 639233339545274518
548 ms 219.121.225.2
30 2026-08-26 09:36 639233329214918079
527 ms 219.121.225.2
29 2026-08-26 09:19 639233318749762337
510 ms 219.121.225.2
28 2026-08-26 09:01 639233308387917838
290 ms 219.121.225.2
27 2026-08-26 08:44 639233297961740122
4 ms 219.121.225.2
26 2026-08-26 08:27 639233287487159094
546 ms 219.121.225.2
25 2026-08-26 08:09 639233276995531707
521 ms 219.121.225.2
24 2026-08-26 07:52 639233266521568229
1096 ms 219.121.225.2
23 2026-08-26 07:34 639233256081047431
523 ms 219.121.225.2
22 2026-08-26 06:40 639233223620132921
1088 ms 219.121.225.2
21 2026-08-26 06:23 639233213287814244
543 ms 219.121.225.2
20 2026-08-26 06:06 639233202925983161
526 ms 219.121.225.2
19 2026-08-26 05:48 639233192644780696
549 ms 219.121.225.2
18 2026-08-26 05:31 639233182401183833
525 ms 219.121.225.2
17 2026-08-26 05:14 639233172074181051
1126 ms 219.121.225.2
16 2026-08-26 04:57 639233161808421455
529 ms 219.121.225.2
15 2026-08-26 04:40 639233151357344052
1118 ms 219.121.225.2
14 2026-08-26 04:22 639233141034116946
1114 ms 219.121.225.2
13 2026-08-26 04:05 639233130828334142
528 ms 219.121.225.2
12 2026-08-26 03:48 639233120373450007
774 ms 219.121.225.2
11 2026-08-26 03:31 639233110066216193
1085 ms 219.121.225.2
10 2026-08-26 02:38 639233078065410564
513 ms 219.121.225.2
9 2026-08-26 02:20 639233067787457832
550 ms 219.121.225.2
8 2026-08-26 02:03 639233057501801162
517 ms 219.121.225.2
7 2026-08-26 01:46 639233047089431703
735 ms 219.121.225.2
6 2026-08-26 01:29 639233036754790688
256 ms 219.121.225.2
5 2026-08-26 01:12 639233026412602472
500 ms 219.121.225.2
4 2026-08-26 00:54 639233016064066127
502 ms 219.121.225.2
3 2026-08-26 00:37 639233005922655772
545 ms 219.121.225.2
2 2026-08-26 00:20 639232995672256907
534 ms 219.121.225.2
1 2026-08-26 00:03 639232985300872416
1086 ms 219.121.225.2