DNS response history for ns1.taro-in.com

ns1.taro-in.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 31 DNS check records, 31 successful responses, 0 failed responses, and 93 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 ns1.taro-in.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

93 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

83.166.240.118

Most recently resolved hosting IP on selected date

Successful Responses

31

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 ns1.taro-in.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
31 2026-08-26 09:55 639233339545274518
96 ms 83.166.240.118
30 2026-08-26 09:37 639233329214918079
120 ms 83.166.240.118
29 2026-08-26 09:20 639233318749762337
3 ms 83.166.240.118
28 2026-08-26 09:02 639233308387917838
130 ms 83.166.240.118
27 2026-08-26 08:45 639233297961740122
47 ms 83.166.240.118
26 2026-08-26 08:28 639233287487159094
62 ms 83.166.240.118
25 2026-08-26 08:10 639233276995531707
123 ms 83.166.240.118
24 2026-08-26 07:53 639233266521568229
126 ms 83.166.240.118
23 2026-08-26 07:35 639233256081047431
94 ms 83.166.240.118
22 2026-08-26 06:41 639233223620132921
134 ms 83.166.240.118
21 2026-08-26 06:24 639233213287814244
121 ms 83.166.240.118
20 2026-08-26 06:07 639233202925983161
123 ms 83.166.240.118
19 2026-08-26 05:49 639233192644780696
159 ms 83.166.240.118
18 2026-08-26 05:32 639233182401183833
90 ms 83.166.240.118
17 2026-08-26 05:15 639233172074181051
93 ms 83.166.240.118
16 2026-08-26 04:58 639233161808421455
93 ms 83.166.240.118
15 2026-08-26 04:41 639233151357344052
114 ms 83.166.240.118
14 2026-08-26 04:23 639233141034116946
46 ms 83.166.240.118
13 2026-08-26 04:06 639233130828334142
50 ms 83.166.240.118
12 2026-08-26 03:49 639233120373450007
122 ms 83.166.240.118
11 2026-08-26 03:32 639233110066216193
53 ms 83.166.240.118
10 2026-08-26 02:38 639233078065410564
123 ms 83.166.240.118
9 2026-08-26 02:21 639233067787457832
66 ms 83.166.240.118
8 2026-08-26 02:04 639233057501801162
119 ms 83.166.240.118
7 2026-08-26 01:47 639233047089431703
60 ms 83.166.240.118
6 2026-08-26 01:30 639233036754790688
50 ms 83.166.240.118
5 2026-08-26 01:12 639233026412602472
60 ms 83.166.240.118
4 2026-08-26 00:55 639233016064066127
99 ms 83.166.240.118
3 2026-08-26 00:38 639233005922655772
57 ms 83.166.240.118
2 2026-08-26 00:21 639232995672256907
118 ms 83.166.240.118
1 2026-08-26 00:04 639232985300872416
123 ms 83.166.240.118