DNS response history for ns2.brandingangels.com

ns2.brandingangels.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 31 DNS check records, 31 successful responses, 0 failed responses, and 240 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.brandingangels.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

240 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

88.99.225.154

Most recently resolved hosting IP on selected date

Successful Responses

31

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.brandingangels.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
31 2026-08-25 11:07 639232524938080723
73 ms 88.99.225.154
30 2026-08-25 10:14 639232492740373468
37 ms 88.99.225.154
29 2026-08-25 09:56 639232482235303141
2016 ms 88.99.225.154
28 2026-08-25 09:39 639232471861770303
6 ms 88.99.225.154
27 2026-08-25 09:22 639232461630217327
31 ms 88.99.225.154
26 2026-08-25 09:05 639232451282965990
11 ms 88.99.225.154
25 2026-08-25 08:47 639232440814614938
4 ms 88.99.225.154
24 2026-08-25 08:30 639232430410720425
42 ms 88.99.225.154
23 2026-08-25 08:12 639232420003096185
36 ms 88.99.225.154
22 2026-08-25 07:55 639232409467287444
2008 ms 88.99.225.154
21 2026-08-25 07:38 639232399077195997
261 ms 88.99.225.154
20 2026-08-25 07:20 639232388731528337
74 ms 88.99.225.154
19 2026-08-25 07:03 639232378288598612
47 ms 88.99.225.154
18 2026-08-25 06:09 639232346196373643
50 ms 88.99.225.154
17 2026-08-25 05:53 639232336112370741
43 ms 88.99.225.154
16 2026-08-25 05:36 639232326146508970
37 ms 88.99.225.154
15 2026-08-25 05:19 639232316189381720
40 ms 88.99.225.154
14 2026-08-25 05:03 639232306217998913
38 ms 88.99.225.154
13 2026-08-25 04:46 639232296255744174
2022 ms 88.99.225.154
12 2026-08-25 04:29 639232286095760789
68 ms 88.99.225.154
11 2026-08-25 04:12 639232276086186273
37 ms 88.99.225.154
10 2026-08-25 03:56 639232265900986425
15 ms 88.99.225.154
9 2026-08-25 03:39 639232255723518075
89 ms 88.99.225.154
8 2026-08-25 03:22 639232245484452890
13 ms 88.99.225.154
7 2026-08-25 03:04 639232235157175331
67 ms 88.99.225.154
6 2026-08-25 02:11 639232203197189095
53 ms 88.99.225.154
5 2026-08-25 01:54 639232192844564298
42 ms 88.99.225.154
4 2026-08-25 01:37 639232182496008942
45 ms 88.99.225.154
3 2026-08-25 01:19 639232172197053132
60 ms 88.99.225.154
2 2026-08-25 00:26 639232140250307418
12 ms 88.99.225.154
1 2026-08-25 00:09 639232129927860324
49 ms 88.99.225.154