DNS response history for ns1.wireblaze.com

ns1.wireblaze.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-25. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 367 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.wireblaze.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

367 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.16.255.15

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 ns1.wireblaze.com

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
27 2026-08-25 09:28 639232461630217327
233 ms 69.16.255.15
26 2026-08-25 09:10 639232451282965990
237 ms 69.16.255.15
25 2026-08-25 08:53 639232440814614938
251 ms 69.16.255.15
24 2026-08-25 08:36 639232430410720425
260 ms 69.16.255.15
23 2026-08-25 08:19 639232420003096185
114 ms 69.16.255.15
22 2026-08-25 08:01 639232409467287444
245 ms 69.16.255.15
21 2026-08-25 07:44 639232399077195997
257 ms 69.16.255.15
20 2026-08-25 07:26 639232388731528337
254 ms 69.16.255.15
19 2026-08-25 07:09 639232378288598612
254 ms 69.16.255.15
18 2026-08-25 06:15 639232346196373643
230 ms 69.16.255.15
17 2026-08-25 05:58 639232336112370741
244 ms 69.16.255.15
16 2026-08-25 05:42 639232326146508970
231 ms 69.16.255.15
15 2026-08-25 05:25 639232316189381720
230 ms 69.16.255.15
14 2026-08-25 05:09 639232306217998913
234 ms 69.16.255.15
13 2026-08-25 04:52 639232296255744174
224 ms 69.16.255.15
12 2026-08-25 04:35 639232286095760789
139 ms 69.16.255.15
11 2026-08-25 04:18 639232276086186273
232 ms 69.16.255.15
10 2026-08-25 04:01 639232265900986425
110 ms 69.16.255.15
9 2026-08-25 03:45 639232255723518075
243 ms 69.16.255.15
8 2026-08-25 03:28 639232245484452890
4112 ms 69.16.255.15
7 2026-08-25 03:10 639232235157175331
243 ms 69.16.255.15
6 2026-08-25 02:17 639232203197189095
243 ms 69.16.255.15
5 2026-08-25 02:00 639232192844564298
125 ms 69.16.255.15
4 2026-08-25 01:43 639232182496008942
252 ms 69.16.255.15
3 2026-08-25 01:25 639232172197053132
231 ms 69.16.255.15
2 2026-08-25 00:32 639232140250307418
242 ms 69.16.255.15
1 2026-08-25 00:15 639232129927860324
250 ms 69.16.255.15