DNS response history for ns2.brand-in-one.com

ns2.brand-in-one.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 34 DNS check records, 34 successful responses, 0 failed responses, and 335 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.brand-in-one.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

335 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.222.12.216

Most recently resolved hosting IP on selected date

Successful Responses

34

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.brand-in-one.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
34 2026-08-25 12:02 639232556111768563
216 ms 51.222.12.216
33 2026-08-25 11:45 639232545839529039
223 ms 51.222.12.216
32 2026-08-25 11:28 639232535349285207
219 ms 51.222.12.216
31 2026-08-25 11:10 639232524938080723
10 ms 51.222.12.216
30 2026-08-25 10:17 639232492740373468
147 ms 51.222.12.216
29 2026-08-25 10:00 639232482235303141
13 ms 51.222.12.216
28 2026-08-25 09:42 639232471861770303
222 ms 51.222.12.216
27 2026-08-25 09:25 639232461630217327
7 ms 51.222.12.216
26 2026-08-25 09:08 639232451282965990
209 ms 51.222.12.216
25 2026-08-25 08:50 639232440814614938
141 ms 51.222.12.216
24 2026-08-25 08:33 639232430410720425
113 ms 51.222.12.216
23 2026-08-25 08:16 639232420003096185
224 ms 51.222.12.216
22 2026-08-25 07:58 639232409467287444
221 ms 51.222.12.216
21 2026-08-25 07:41 639232399077195997
108 ms 51.222.12.216
20 2026-08-25 07:23 639232388731528337
109 ms 51.222.12.216
19 2026-08-25 07:06 639232378288598612
221 ms 51.222.12.216
18 2026-08-25 06:13 639232346196373643
114 ms 51.222.12.216
17 2026-08-25 05:56 639232336112370741
109 ms 51.222.12.216
16 2026-08-25 05:39 639232326146508970
218 ms 51.222.12.216
15 2026-08-25 05:22 639232316189381720
3 ms 51.222.12.216
14 2026-08-25 05:06 639232306217998913
132 ms 51.222.12.216
13 2026-08-25 04:49 639232296255744174
222 ms 51.222.12.216
12 2026-08-25 04:32 639232286095760789
111 ms 51.222.12.216
11 2026-08-25 04:15 639232276086186273
2107 ms 51.222.12.216
10 2026-08-25 03:59 639232265900986425
222 ms 51.222.12.216
9 2026-08-25 03:42 639232255723518075
221 ms 51.222.12.216
8 2026-08-25 03:25 639232245484452890
2114 ms 51.222.12.216
7 2026-08-25 03:08 639232235157175331
216 ms 51.222.12.216
6 2026-08-25 02:14 639232203197189095
2110 ms 51.222.12.216
5 2026-08-25 01:57 639232192844564298
213 ms 51.222.12.216
4 2026-08-25 01:40 639232182496008942
221 ms 51.222.12.216
3 2026-08-25 01:23 639232172197053132
221 ms 51.222.12.216
2 2026-08-25 00:29 639232140250307418
221 ms 51.222.12.216
1 2026-08-25 00:12 639232129927860324
214 ms 51.222.12.216