DNS response history for ns3.duetdisplay.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

209 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.10.92

Most recently resolved hosting IP on selected date

Successful Responses

33

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.duetdisplay.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
33 2026-08-26 10:34 639233370841350248
5 ms 162.159.10.92
32 2026-08-26 10:17 639233360361507238
11 ms 162.159.10.92
31 2026-08-26 10:00 639233350067824371
6 ms 162.159.10.92
30 2026-08-26 09:42 639233339545274518
34 ms 162.159.10.92
29 2026-08-26 09:25 639233329214918079
6 ms 162.159.10.92
28 2026-08-26 09:08 639233318749762337
24 ms 162.159.10.92
27 2026-08-26 08:50 639233308387917838
7 ms 162.159.10.92
26 2026-08-26 08:33 639233297961740122
7 ms 162.159.10.92
25 2026-08-26 08:15 639233287487159094
16 ms 162.159.10.92
24 2026-08-26 07:58 639233276995531707
13 ms 162.159.10.92
23 2026-08-26 07:40 639233266521568229
34 ms 162.159.10.92
22 2026-08-26 07:23 639233256081047431
76 ms 162.159.10.92
21 2026-08-26 06:29 639233223620132921
109 ms 162.159.10.92
20 2026-08-26 06:12 639233213287814244
37 ms 162.159.10.92
19 2026-08-26 05:55 639233202925983161
33 ms 162.159.10.92
18 2026-08-26 05:37 639233192644780696
39 ms 162.159.10.92
17 2026-08-26 05:20 639233182401183833
41 ms 162.159.10.92
16 2026-08-26 05:03 639233172074181051
6 ms 162.159.10.92
15 2026-08-26 04:46 639233161808421455
22 ms 162.159.10.92
14 2026-08-26 04:29 639233151357344052
2066 ms 162.159.10.92
13 2026-08-26 04:11 639233141034116946
42 ms 162.159.10.92
12 2026-08-26 03:54 639233130828334142
15 ms 162.159.10.92
11 2026-08-26 03:37 639233120373450007
3 ms 162.159.10.92
10 2026-08-26 03:20 639233110066216193
2019 ms 162.159.10.92
9 2026-08-26 02:26 639233078065410564
2044 ms 162.159.10.92
8 2026-08-26 02:09 639233067787457832
4 ms 162.159.10.92
7 2026-08-26 01:52 639233057501801162
6 ms 162.159.10.92
6 2026-08-26 01:35 639233047089431703
41 ms 162.159.10.92
5 2026-08-26 01:18 639233036754790688
43 ms 162.159.10.92
4 2026-08-26 01:00 639233026412602472
35 ms 162.159.10.92
3 2026-08-26 00:43 639233016064066127
5 ms 162.159.10.92
2 2026-08-26 00:26 639233005922655772
35 ms 162.159.10.92
1 2026-08-26 00:09 639232995672256907
11 ms 162.159.10.92