DNS response history for ns1.duepons.com

ns1.duepons.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 38 DNS check records, 38 successful responses, 0 failed responses, and 485 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.duepons.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

485 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

174.68.32.124

Most recently resolved hosting IP on selected date

Successful Responses

38

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.duepons.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
38 2026-08-26 12:30 639233434974187439
2010 ms 174.68.32.124
37 2026-08-26 12:12 639233424567558554
191 ms 174.68.32.124
36 2026-08-26 11:55 639233414056832719
354 ms 174.68.32.124
35 2026-08-26 11:37 639233403515141099
365 ms 174.68.32.124
34 2026-08-26 10:43 639233370841350248
185 ms 174.68.32.124
33 2026-08-26 10:26 639233360361507238
361 ms 174.68.32.124
32 2026-08-26 10:08 639233350067824371
358 ms 174.68.32.124
31 2026-08-26 09:51 639233339545274518
359 ms 174.68.32.124
30 2026-08-26 09:33 639233329214918079
357 ms 174.68.32.124
29 2026-08-26 09:16 639233318749762337
355 ms 174.68.32.124
28 2026-08-26 08:59 639233308387917838
368 ms 174.68.32.124
27 2026-08-26 08:42 639233297961740122
360 ms 174.68.32.124
26 2026-08-26 08:24 639233287487159094
344 ms 174.68.32.124
25 2026-08-26 08:07 639233276995531707
199 ms 174.68.32.124
24 2026-08-26 07:49 639233266521568229
360 ms 174.68.32.124
23 2026-08-26 07:32 639233256081047431
357 ms 174.68.32.124
22 2026-08-26 06:38 639233223620132921
4844 ms 174.68.32.124
21 2026-08-26 06:20 639233213287814244
355 ms 174.68.32.124
20 2026-08-26 06:03 639233202925983161
362 ms 174.68.32.124
19 2026-08-26 05:46 639233192644780696
370 ms 174.68.32.124
18 2026-08-26 05:29 639233182401183833
579 ms 174.68.32.124
17 2026-08-26 05:12 639233172074181051
194 ms 174.68.32.124
16 2026-08-26 04:54 639233161808421455
364 ms 174.68.32.124
15 2026-08-26 04:37 639233151357344052
348 ms 174.68.32.124
14 2026-08-26 04:20 639233141034116946
3 ms 174.68.32.124
13 2026-08-26 04:03 639233130828334142
4 ms 174.68.32.124
12 2026-08-26 03:46 639233120373450007
359 ms 174.68.32.124
11 2026-08-26 03:28 639233110066216193
353 ms 174.68.32.124
10 2026-08-26 02:35 639233078065410564
355 ms 174.68.32.124
9 2026-08-26 02:18 639233067787457832
353 ms 174.68.32.124
8 2026-08-26 02:01 639233057501801162
254 ms 174.68.32.124
7 2026-08-26 01:44 639233047089431703
343 ms 174.68.32.124
6 2026-08-26 01:26 639233036754790688
343 ms 174.68.32.124
5 2026-08-26 01:09 639233026412602472
351 ms 174.68.32.124
4 2026-08-26 00:52 639233016064066127
347 ms 174.68.32.124
3 2026-08-26 00:35 639233005922655772
353 ms 174.68.32.124
2 2026-08-26 00:18 639232995672256907
348 ms 174.68.32.124
1 2026-08-26 00:00 639232985300872416
362 ms 174.68.32.124