DNS response history for ns3.duosoluciones.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

325 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.89.13.120

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 ns3.duosoluciones.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
35 2026-08-26 11:46 639233414056832719
2084 ms 212.89.13.120
34 2026-08-26 11:29 639233403515141099
64 ms 212.89.13.120
33 2026-08-26 10:34 639233370841350248
76 ms 212.89.13.120
32 2026-08-26 10:17 639233360361507238
172 ms 212.89.13.120
31 2026-08-26 10:00 639233350067824371
2066 ms 212.89.13.120
30 2026-08-26 09:42 639233339545274518
83 ms 212.89.13.120
29 2026-08-26 09:25 639233329214918079
117 ms 212.89.13.120
28 2026-08-26 09:08 639233318749762337
74 ms 212.89.13.120
27 2026-08-26 08:50 639233308387917838
97 ms 212.89.13.120
26 2026-08-26 08:33 639233297961740122
99 ms 212.89.13.120
25 2026-08-26 08:16 639233287487159094
94 ms 212.89.13.120
24 2026-08-26 07:58 639233276995531707
47 ms 212.89.13.120
23 2026-08-26 07:41 639233266521568229
2055 ms 212.89.13.120
22 2026-08-26 07:23 639233256081047431
193 ms 212.89.13.120
21 2026-08-26 06:29 639233223620132921
155 ms 212.89.13.120
20 2026-08-26 06:12 639233213287814244
75 ms 212.89.13.120
19 2026-08-26 05:55 639233202925983161
2177 ms 212.89.13.120
18 2026-08-26 05:37 639233192644780696
82 ms 212.89.13.120
17 2026-08-26 05:20 639233182401183833
105 ms 212.89.13.120
16 2026-08-26 05:03 639233172074181051
74 ms 212.89.13.120
15 2026-08-26 04:46 639233161808421455
73 ms 212.89.13.120
14 2026-08-26 04:29 639233151357344052
77 ms 212.89.13.120
13 2026-08-26 04:11 639233141034116946
164 ms 212.89.13.120
12 2026-08-26 03:54 639233130828334142
98 ms 212.89.13.120
11 2026-08-26 03:37 639233120373450007
109 ms 212.89.13.120
10 2026-08-26 03:20 639233110066216193
132 ms 212.89.13.120
9 2026-08-26 02:26 639233078065410564
81 ms 212.89.13.120
8 2026-08-26 02:09 639233067787457832
84 ms 212.89.13.120
7 2026-08-26 01:52 639233057501801162
74 ms 212.89.13.120
6 2026-08-26 01:35 639233047089431703
71 ms 212.89.13.120
5 2026-08-26 01:18 639233036754790688
79 ms 212.89.13.120
4 2026-08-26 01:00 639233026412602472
95 ms 212.89.13.120
3 2026-08-26 00:43 639233016064066127
82 ms 212.89.13.120
2 2026-08-26 00:26 639233005922655772
100 ms 212.89.13.120
1 2026-08-26 00:09 639232995672256907
80 ms 212.89.13.120