DNS response history for ns2.breezedawn.net

ns2.breezedawn.net 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-25. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 233 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 ns2.breezedawn.net.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

233 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.81.68.230

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 ns2.breezedawn.net

Showing DNS history for 2026-08-25 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-25 13:12 639232597643611557
279 ms 74.81.68.230
37 2026-08-25 12:55 639232587225721862
6 ms 74.81.68.230
36 2026-08-25 12:37 639232576780683689
57 ms 74.81.68.230
35 2026-08-25 12:20 639232566381512620
5 ms 74.81.68.230
34 2026-08-25 12:03 639232556111768563
296 ms 74.81.68.230
33 2026-08-25 11:46 639232545839529039
296 ms 74.81.68.230
32 2026-08-25 11:28 639232535349285207
146 ms 74.81.68.230
31 2026-08-25 11:11 639232524938080723
528 ms 74.81.68.230
30 2026-08-25 10:17 639232492740373468
308 ms 74.81.68.230
29 2026-08-25 10:00 639232482235303141
294 ms 74.81.68.230
28 2026-08-25 09:42 639232471861770303
152 ms 74.81.68.230
27 2026-08-25 09:25 639232461630217327
4 ms 74.81.68.230
26 2026-08-25 09:08 639232451282965990
309 ms 74.81.68.230
25 2026-08-25 08:51 639232440814614938
302 ms 74.81.68.230
24 2026-08-25 08:33 639232430410720425
333 ms 74.81.68.230
23 2026-08-25 08:16 639232420003096185
271 ms 74.81.68.230
22 2026-08-25 07:59 639232409467287444
300 ms 74.81.68.230
21 2026-08-25 07:41 639232399077195997
283 ms 74.81.68.230
20 2026-08-25 07:24 639232388731528337
301 ms 74.81.68.230
19 2026-08-25 07:06 639232378288598612
300 ms 74.81.68.230
18 2026-08-25 06:13 639232346196373643
294 ms 74.81.68.230
17 2026-08-25 05:56 639232336112370741
297 ms 74.81.68.230
16 2026-08-25 05:39 639232326146508970
282 ms 74.81.68.230
15 2026-08-25 05:23 639232316189381720
3 ms 74.81.68.230
14 2026-08-25 05:06 639232306217998913
12 ms 74.81.68.230
13 2026-08-25 04:50 639232296255744174
277 ms 74.81.68.230
12 2026-08-25 04:33 639232286095760789
142 ms 74.81.68.230
11 2026-08-25 04:16 639232276086186273
10 ms 74.81.68.230
10 2026-08-25 03:59 639232265900986425
298 ms 74.81.68.230
9 2026-08-25 03:42 639232255723518075
275 ms 74.81.68.230
8 2026-08-25 03:25 639232245484452890
332 ms 74.81.68.230
7 2026-08-25 03:08 639232235157175331
302 ms 74.81.68.230
6 2026-08-25 02:15 639232203197189095
158 ms 74.81.68.230
5 2026-08-25 01:57 639232192844564298
304 ms 74.81.68.230
4 2026-08-25 01:40 639232182496008942
145 ms 74.81.68.230
3 2026-08-25 01:23 639232172197053132
296 ms 74.81.68.230
2 2026-08-25 00:30 639232140250307418
333 ms 74.81.68.230
1 2026-08-25 00:13 639232129927860324
309 ms 74.81.68.230