DNS response history for ns.inujirushi.com.tw

ns.inujirushi.com.tw 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 592 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 ns.inujirushi.com.tw.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

592 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

124.150.132.75

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 ns.inujirushi.com.tw

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:58 639233414056832719
650 ms 124.150.132.75
35 2026-08-26 11:40 639233403515141099
618 ms 124.150.132.75
34 2026-08-26 10:45 639233370841350248
740 ms 124.150.132.75
33 2026-08-26 10:28 639233360361507238
907 ms 124.150.132.75
32 2026-08-26 10:11 639233350067824371
777 ms 124.150.132.75
31 2026-08-26 09:53 639233339545274518
612 ms 124.150.132.75
30 2026-08-26 09:36 639233329214918079
589 ms 124.150.132.75
29 2026-08-26 09:19 639233318749762337
606 ms 124.150.132.75
28 2026-08-26 09:01 639233308387917838
620 ms 124.150.132.75
27 2026-08-26 08:44 639233297961740122
805 ms 124.150.132.75
26 2026-08-26 08:27 639233287487159094
618 ms 124.150.132.75
25 2026-08-26 08:09 639233276995531707
807 ms 124.150.132.75
24 2026-08-26 07:52 639233266521568229
602 ms 124.150.132.75
23 2026-08-26 07:34 639233256081047431
893 ms 124.150.132.75
22 2026-08-26 06:40 639233223620132921
600 ms 124.150.132.75
21 2026-08-26 06:23 639233213287814244
4 ms 124.150.132.75
20 2026-08-26 06:05 639233202925983161
594 ms 124.150.132.75
19 2026-08-26 05:48 639233192644780696
4 ms 124.150.132.75
18 2026-08-26 05:31 639233182401183833
753 ms 124.150.132.75
17 2026-08-26 05:14 639233172074181051
4 ms 124.150.132.75
16 2026-08-26 04:57 639233161808421455
765 ms 124.150.132.75
15 2026-08-26 04:40 639233151357344052
8 ms 124.150.132.75
14 2026-08-26 04:22 639233141034116946
753 ms 124.150.132.75
13 2026-08-26 04:05 639233130828334142
6 ms 124.150.132.75
12 2026-08-26 03:48 639233120373450007
742 ms 124.150.132.75
11 2026-08-26 03:31 639233110066216193
730 ms 124.150.132.75
10 2026-08-26 02:37 639233078065410564
305 ms 124.150.132.75
9 2026-08-26 02:20 639233067787457832
615 ms 124.150.132.75
8 2026-08-26 02:03 639233057501801162
621 ms 124.150.132.75
7 2026-08-26 01:46 639233047089431703
757 ms 124.150.132.75
6 2026-08-26 01:29 639233036754790688
843 ms 124.150.132.75
5 2026-08-26 01:11 639233026412602472
754 ms 124.150.132.75
4 2026-08-26 00:54 639233016064066127
607 ms 124.150.132.75
3 2026-08-26 00:37 639233005922655772
768 ms 124.150.132.75
2 2026-08-26 00:20 639232995672256907
767 ms 124.150.132.75
1 2026-08-26 00:03 639232985300872416
463 ms 124.150.132.75