DNS response history for ns3.animedaisuke.com

ns3.animedaisuke.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 29 DNS check records, 29 successful responses, 0 failed responses, and 260 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 ns3.animedaisuke.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

260 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.65.19.117

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns3.animedaisuke.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
29 2026-08-26 09:19 639233318749762337
269 ms 69.65.19.117
28 2026-08-26 09:01 639233308387917838
131 ms 69.65.19.117
27 2026-08-26 08:44 639233297961740122
4 ms 69.65.19.117
26 2026-08-26 08:26 639233287487159094
256 ms 69.65.19.117
25 2026-08-26 08:09 639233276995531707
3 ms 69.65.19.117
24 2026-08-26 07:51 639233266521568229
366 ms 69.65.19.117
23 2026-08-26 07:34 639233256081047431
267 ms 69.65.19.117
22 2026-08-26 06:40 639233223620132921
145 ms 69.65.19.117
21 2026-08-26 06:23 639233213287814244
133 ms 69.65.19.117
20 2026-08-26 06:05 639233202925983161
130 ms 69.65.19.117
19 2026-08-26 05:48 639233192644780696
255 ms 69.65.19.117
18 2026-08-26 05:31 639233182401183833
133 ms 69.65.19.117
17 2026-08-26 05:14 639233172074181051
127 ms 69.65.19.117
16 2026-08-26 04:57 639233161808421455
257 ms 69.65.19.117
15 2026-08-26 04:40 639233151357344052
128 ms 69.65.19.117
14 2026-08-26 04:22 639233141034116946
263 ms 69.65.19.117
13 2026-08-26 04:05 639233130828334142
2221 ms 69.65.19.117
12 2026-08-26 03:48 639233120373450007
128 ms 69.65.19.117
11 2026-08-26 03:30 639233110066216193
129 ms 69.65.19.117
10 2026-08-26 02:37 639233078065410564
131 ms 69.65.19.117
9 2026-08-26 02:20 639233067787457832
134 ms 69.65.19.117
8 2026-08-26 02:03 639233057501801162
128 ms 69.65.19.117
7 2026-08-26 01:46 639233047089431703
258 ms 69.65.19.117
6 2026-08-26 01:28 639233036754790688
127 ms 69.65.19.117
5 2026-08-26 01:11 639233026412602472
127 ms 69.65.19.117
4 2026-08-26 00:54 639233016064066127
632 ms 69.65.19.117
3 2026-08-26 00:37 639233005922655772
132 ms 69.65.19.117
2 2026-08-26 00:20 639232995672256907
260 ms 69.65.19.117
1 2026-08-26 00:03 639232985300872416
259 ms 69.65.19.117