DNS response history for ns1.dual-connect.com

ns1.dual-connect.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 235 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.dual-connect.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

235 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.161.41.176

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 ns1.dual-connect.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:51 639233414056832719
34 ms 51.161.41.176
34 2026-08-26 11:34 639233403515141099
166 ms 51.161.41.176
33 2026-08-26 10:39 639233370841350248
218 ms 51.161.41.176
32 2026-08-26 10:22 639233360361507238
218 ms 51.161.41.176
31 2026-08-26 10:05 639233350067824371
236 ms 51.161.41.176
30 2026-08-26 09:47 639233339545274518
220 ms 51.161.41.176
29 2026-08-26 09:30 639233329214918079
224 ms 51.161.41.176
28 2026-08-26 09:13 639233318749762337
223 ms 51.161.41.176
27 2026-08-26 08:55 639233308387917838
220 ms 51.161.41.176
26 2026-08-26 08:38 639233297961740122
220 ms 51.161.41.176
25 2026-08-26 08:21 639233287487159094
14 ms 51.161.41.176
24 2026-08-26 08:03 639233276995531707
224 ms 51.161.41.176
23 2026-08-26 07:45 639233266521568229
232 ms 51.161.41.176
22 2026-08-26 07:28 639233256081047431
221 ms 51.161.41.176
21 2026-08-26 06:34 639233223620132921
7 ms 51.161.41.176
20 2026-08-26 06:17 639233213287814244
220 ms 51.161.41.176
19 2026-08-26 05:59 639233202925983161
142 ms 51.161.41.176
18 2026-08-26 05:42 639233192644780696
2128 ms 51.161.41.176
17 2026-08-26 05:25 639233182401183833
220 ms 51.161.41.176
16 2026-08-26 05:08 639233172074181051
217 ms 51.161.41.176
15 2026-08-26 04:51 639233161808421455
213 ms 51.161.41.176
14 2026-08-26 04:34 639233151357344052
219 ms 51.161.41.176
13 2026-08-26 04:16 639233141034116946
225 ms 51.161.41.176
12 2026-08-26 03:59 639233130828334142
216 ms 51.161.41.176
11 2026-08-26 03:42 639233120373450007
17 ms 51.161.41.176
10 2026-08-26 03:25 639233110066216193
126 ms 51.161.41.176
9 2026-08-26 02:31 639233078065410564
216 ms 51.161.41.176
8 2026-08-26 02:14 639233067787457832
218 ms 51.161.41.176
7 2026-08-26 01:57 639233057501801162
105 ms 51.161.41.176
6 2026-08-26 01:40 639233047089431703
217 ms 51.161.41.176
5 2026-08-26 01:23 639233036754790688
169 ms 51.161.41.176
4 2026-08-26 01:05 639233026412602472
227 ms 51.161.41.176
3 2026-08-26 00:48 639233016064066127
220 ms 51.161.41.176
2 2026-08-26 00:31 639233005922655772
214 ms 51.161.41.176
1 2026-08-26 00:14 639232995672256907
7 ms 51.161.41.176