DNS response history for ns3.mydyndns.org

ns3.mydyndns.org 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 530 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.mydyndns.org.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

530 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.59.170.201

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.mydyndns.org

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:36 639233370841350248
1593 ms 108.59.170.201
32 2026-08-26 10:18 639233360361507238
351 ms 108.59.170.201
31 2026-08-26 10:01 639233350067824371
104 ms 108.59.170.201
30 2026-08-26 09:44 639233339545274518
74 ms 108.59.170.201
29 2026-08-26 09:26 639233329214918079
205 ms 108.59.170.201
28 2026-08-26 09:09 639233318749762337
9 ms 108.59.170.201
27 2026-08-26 08:52 639233308387917838
391 ms 108.59.170.201
26 2026-08-26 08:34 639233297961740122
2049 ms 108.59.170.201
25 2026-08-26 08:17 639233287487159094
75 ms 108.59.170.201
24 2026-08-26 07:59 639233276995531707
2020 ms 108.59.170.201
23 2026-08-26 07:42 639233266521568229
113 ms 108.59.170.201
22 2026-08-26 07:25 639233256081047431
221 ms 108.59.170.201
21 2026-08-26 06:30 639233223620132921
28 ms 108.59.170.201
20 2026-08-26 06:13 639233213287814244
2029 ms 108.59.170.201
19 2026-08-26 05:56 639233202925983161
39 ms 108.59.170.201
18 2026-08-26 05:39 639233192644780696
75 ms 108.59.170.201
17 2026-08-26 05:22 639233182401183833
470 ms 108.59.170.201
16 2026-08-26 05:05 639233172074181051
42 ms 108.59.170.201
15 2026-08-26 04:47 639233161808421455
74 ms 108.59.170.201
14 2026-08-26 04:30 639233151357344052
2107 ms 108.59.170.201
13 2026-08-26 04:13 639233141034116946
2010 ms 108.59.170.201
12 2026-08-26 03:56 639233130828334142
331 ms 108.59.170.201
11 2026-08-26 03:38 639233120373450007
283 ms 108.59.170.201
10 2026-08-26 03:21 639233110066216193
9 ms 108.59.170.201
9 2026-08-26 02:28 639233078065410564
2023 ms 108.59.170.201
8 2026-08-26 02:11 639233067787457832
8 ms 108.59.170.201
7 2026-08-26 01:54 639233057501801162
77 ms 108.59.170.201
6 2026-08-26 01:36 639233047089431703
83 ms 108.59.170.201
5 2026-08-26 01:19 639233036754790688
14 ms 108.59.170.201
4 2026-08-26 01:02 639233026412602472
36 ms 108.59.170.201
3 2026-08-26 00:44 639233016064066127
23 ms 108.59.170.201
2 2026-08-26 00:27 639233005922655772
320 ms 108.59.170.201
1 2026-08-26 00:10 639232995672256907
202 ms 108.59.170.201