DNS response history for ns3.bluevalley.net

ns3.bluevalley.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 30 DNS check records, 30 successful responses, 0 failed responses, and 331 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.bluevalley.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

331 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

68.234.96.6

Most recently resolved hosting IP on selected date

Successful Responses

30

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.bluevalley.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
30 2026-08-25 10:17 639232492740373468
141 ms 68.234.96.6
29 2026-08-25 10:00 639232482235303141
134 ms 68.234.96.6
28 2026-08-25 09:42 639232471861770303
276 ms 68.234.96.6
27 2026-08-25 09:25 639232461630217327
279 ms 68.234.96.6
26 2026-08-25 09:08 639232451282965990
132 ms 68.234.96.6
25 2026-08-25 08:51 639232440814614938
135 ms 68.234.96.6
24 2026-08-25 08:33 639232430410720425
140 ms 68.234.96.6
23 2026-08-25 08:16 639232420003096185
275 ms 68.234.96.6
22 2026-08-25 07:59 639232409467287444
139 ms 68.234.96.6
21 2026-08-25 07:41 639232399077195997
283 ms 68.234.96.6
20 2026-08-25 07:24 639232388731528337
270 ms 68.234.96.6
19 2026-08-25 07:07 639232378288598612
273 ms 68.234.96.6
18 2026-08-25 06:13 639232346196373643
300 ms 68.234.96.6
17 2026-08-25 05:56 639232336112370741
2132 ms 68.234.96.6
16 2026-08-25 05:40 639232326146508970
269 ms 68.234.96.6
15 2026-08-25 05:23 639232316189381720
34 ms 68.234.96.6
14 2026-08-25 05:06 639232306217998913
137 ms 68.234.96.6
13 2026-08-25 04:50 639232296255744174
138 ms 68.234.96.6
12 2026-08-25 04:33 639232286095760789
272 ms 68.234.96.6
11 2026-08-25 04:16 639232276086186273
270 ms 68.234.96.6
10 2026-08-25 03:59 639232265900986425
137 ms 68.234.96.6
9 2026-08-25 03:42 639232255723518075
273 ms 68.234.96.6
8 2026-08-25 03:25 639232245484452890
267 ms 68.234.96.6
7 2026-08-25 03:08 639232235157175331
137 ms 68.234.96.6
6 2026-08-25 02:15 639232203197189095
135 ms 68.234.96.6
5 2026-08-25 01:58 639232192844564298
2134 ms 68.234.96.6
4 2026-08-25 01:40 639232182496008942
267 ms 68.234.96.6
3 2026-08-25 01:23 639232172197053132
276 ms 68.234.96.6
2 2026-08-25 00:30 639232140250307418
139 ms 68.234.96.6
1 2026-08-25 00:13 639232129927860324
136 ms 68.234.96.6