DNS response history for ns2.bozoom.es

ns2.bozoom.es 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 35 DNS check records, 34 successful responses, 1 failed responses, and 148 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.bozoom.es.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

148 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.203.125.31

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.bozoom.es

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
35 2026-08-25 12:12 639232566381512620
67 ms 116.203.125.31
34 2026-08-25 11:55 639232556111768563
45 ms 116.203.125.31
33 2026-08-25 11:38 639232545839529039
6 ms 116.203.125.31
32 2026-08-25 11:20 639232535349285207
2019 ms 116.203.125.31
31 2026-08-25 11:03 639232524938080723
44 ms 116.203.125.31
30 2026-08-25 10:09 639232492740373468
32 ms 116.203.125.31
29 2026-08-25 09:52 639232482235303141
5 ms 116.203.125.31
28 2026-08-25 09:35 639232471861770303
7 ms 116.203.125.31
27 2026-08-25 09:18 639232461630217327
-
26 2026-08-25 09:00 639232451282965990
69 ms 116.203.125.31
25 2026-08-25 08:43 639232440814614938
41 ms 116.203.125.31
24 2026-08-25 08:25 639232430410720425
2030 ms 116.203.125.31
23 2026-08-25 08:08 639232420003096185
29 ms 116.203.125.31
22 2026-08-25 07:51 639232409467287444
41 ms 116.203.125.31
21 2026-08-25 07:33 639232399077195997
47 ms 116.203.125.31
20 2026-08-25 07:16 639232388731528337
5 ms 116.203.125.31
19 2026-08-25 06:59 639232378288598612
10 ms 116.203.125.31
18 2026-08-25 06:05 639232346196373643
12 ms 116.203.125.31
17 2026-08-25 05:48 639232336112370741
55 ms 116.203.125.31
16 2026-08-25 05:32 639232326146508970
7 ms 116.203.125.31
15 2026-08-25 05:15 639232316189381720
2 ms 116.203.125.31
14 2026-08-25 04:58 639232306217998913
67 ms 116.203.125.31
13 2026-08-25 04:42 639232296255744174
9 ms 116.203.125.31
12 2026-08-25 04:25 639232286095760789
65 ms 116.203.125.31
11 2026-08-25 04:08 639232276086186273
7 ms 116.203.125.31
10 2026-08-25 03:51 639232265900986425
24 ms 116.203.125.31
9 2026-08-25 03:34 639232255723518075
12 ms 116.203.125.31
8 2026-08-25 03:17 639232245484452890
24 ms 116.203.125.31
7 2026-08-25 03:00 639232235157175331
56 ms 116.203.125.31
6 2026-08-25 02:07 639232203197189095
13 ms 116.203.125.31
5 2026-08-25 01:50 639232192844564298
45 ms 116.203.125.31
4 2026-08-25 01:32 639232182496008942
7 ms 116.203.125.31
3 2026-08-25 01:15 639232172197053132
87 ms 116.203.125.31
2 2026-08-25 00:22 639232140250307418
27 ms 116.203.125.31
1 2026-08-25 00:05 639232129927860324
24 ms 116.203.125.31