DNS response history for ns3.baywinds.org

ns3.baywinds.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 27 DNS check records, 27 successful responses, 0 failed responses, and 257 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.baywinds.org.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

257 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

54.243.134.236

Most recently resolved hosting IP on selected date

Successful Responses

27

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.baywinds.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
27 2026-08-26 08:43 639233297961740122
3 ms 54.243.134.236
26 2026-08-26 08:26 639233287487159094
174 ms 54.243.134.236
25 2026-08-26 08:08 639233276995531707
90 ms 54.87.243.144
24 2026-08-26 07:51 639233266521568229
91 ms 54.87.243.144
23 2026-08-26 07:33 639233256081047431
93 ms 54.87.243.144
22 2026-08-26 06:39 639233223620132921
3 ms 54.87.243.144
21 2026-08-26 06:22 639233213287814244
90 ms 54.87.243.144
20 2026-08-26 06:05 639233202925983161
175 ms 54.243.134.236
19 2026-08-26 05:48 639233192644780696
91 ms 54.87.243.144
18 2026-08-26 05:30 639233182401183833
91 ms 54.87.243.144
17 2026-08-26 05:13 639233172074181051
171 ms 54.243.134.236
16 2026-08-26 04:56 639233161808421455
89 ms 54.87.243.144
15 2026-08-26 04:39 639233151357344052
3 ms 54.243.134.236
14 2026-08-26 04:22 639233141034116946
174 ms 54.243.134.236
13 2026-08-26 04:04 639233130828334142
90 ms 54.87.243.144
12 2026-08-26 03:47 639233120373450007
90 ms 54.87.243.144
11 2026-08-26 03:30 639233110066216193
179 ms 54.243.134.236
10 2026-08-26 02:37 639233078065410564
89 ms 54.87.243.144
9 2026-08-26 02:20 639233067787457832
90 ms 54.87.243.144
8 2026-08-26 02:02 639233057501801162
174 ms 54.87.243.144
7 2026-08-26 01:45 639233047089431703
174 ms 54.87.243.144
6 2026-08-26 01:28 639233036754790688
89 ms 54.87.243.144
5 2026-08-26 01:11 639233026412602472
2173 ms 54.87.243.144
4 2026-08-26 00:53 639233016064066127
1817 ms 54.87.243.144
3 2026-08-26 00:36 639233005922655772
468 ms 54.87.243.144
2 2026-08-26 00:19 639232995672256907
90 ms 54.87.243.144
1 2026-08-26 00:02 639232985300872416
91 ms 54.87.243.144