DNS response history for ns2.bozobus.net

ns2.bozobus.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 37 DNS check records, 35 successful responses, 2 failed responses, and 320 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.bozobus.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

320 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.140.229.43

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.bozobus.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
37 2026-08-25 12:55 639232587225721862
-
36 2026-08-25 12:38 639232576780683689
6 ms 165.140.229.43
35 2026-08-25 12:20 639232566381512620
310 ms 165.140.229.43
34 2026-08-25 12:03 639232556111768563
304 ms 165.140.229.43
33 2026-08-25 11:46 639232545839529039
-
32 2026-08-25 11:29 639232535349285207
2195 ms 165.140.229.43
31 2026-08-25 11:11 639232524938080723
324 ms 165.140.229.43
30 2026-08-25 10:17 639232492740373468
308 ms 165.140.229.43
29 2026-08-25 10:00 639232482235303141
302 ms 165.140.229.43
28 2026-08-25 09:42 639232471861770303
153 ms 165.140.229.43
27 2026-08-25 09:25 639232461630217327
300 ms 165.140.229.43
26 2026-08-25 09:08 639232451282965990
300 ms 165.140.229.43
25 2026-08-25 08:51 639232440814614938
8 ms 165.140.229.43
24 2026-08-25 08:33 639232430410720425
301 ms 165.140.229.43
23 2026-08-25 08:16 639232420003096185
157 ms 165.140.229.43
22 2026-08-25 07:59 639232409467287444
2031 ms 165.140.229.43
21 2026-08-25 07:41 639232399077195997
9 ms 165.140.229.43
20 2026-08-25 07:24 639232388731528337
151 ms 165.140.229.43
19 2026-08-25 07:07 639232378288598612
138 ms 165.140.229.43
18 2026-08-25 06:13 639232346196373643
313 ms 165.140.229.43
17 2026-08-25 05:56 639232336112370741
151 ms 165.140.229.43
16 2026-08-25 05:40 639232326146508970
307 ms 165.140.229.43
15 2026-08-25 05:23 639232316189381720
198 ms 165.140.229.43
14 2026-08-25 05:06 639232306217998913
153 ms 165.140.229.43
13 2026-08-25 04:50 639232296255744174
314 ms 165.140.229.43
12 2026-08-25 04:33 639232286095760789
2 ms 165.140.229.43
11 2026-08-25 04:16 639232276086186273
297 ms 165.140.229.43
10 2026-08-25 03:59 639232265900986425
303 ms 165.140.229.43
9 2026-08-25 03:42 639232255723518075
158 ms 165.140.229.43
8 2026-08-25 03:25 639232245484452890
303 ms 165.140.229.43
7 2026-08-25 03:08 639232235157175331
151 ms 165.140.229.43
6 2026-08-25 02:15 639232203197189095
296 ms 165.140.229.43
5 2026-08-25 01:58 639232192844564298
21 ms 165.140.229.43
4 2026-08-25 01:40 639232182496008942
150 ms 165.140.229.43
3 2026-08-25 01:23 639232172197053132
153 ms 165.140.229.43
2 2026-08-25 00:30 639232140250307418
315 ms 165.140.229.43
1 2026-08-25 00:13 639232129927860324
301 ms 165.140.229.43