DNS response history for ns2.brilliantmediacorp.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

222 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.215.131.191

Most recently resolved hosting IP on selected date

Successful Responses

33

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.brilliantmediacorp.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
33 2026-08-25 11:44 639232545839529039
119 ms 162.215.131.191
32 2026-08-25 11:27 639232535349285207
243 ms 162.215.131.191
31 2026-08-25 11:09 639232524938080723
255 ms 162.215.131.191
30 2026-08-25 10:16 639232492740373468
223 ms 162.215.131.191
29 2026-08-25 09:59 639232482235303141
119 ms 162.215.131.191
28 2026-08-25 09:41 639232471861770303
15 ms 162.215.131.191
27 2026-08-25 09:24 639232461630217327
129 ms 162.215.131.191
26 2026-08-25 09:07 639232451282965990
7 ms 162.215.131.191
25 2026-08-25 08:49 639232440814614938
119 ms 162.215.131.191
24 2026-08-25 08:32 639232430410720425
248 ms 162.215.131.191
23 2026-08-25 08:15 639232420003096185
239 ms 162.215.131.191
22 2026-08-25 07:57 639232409467287444
7 ms 162.215.131.191
21 2026-08-25 07:40 639232399077195997
138 ms 162.215.131.191
20 2026-08-25 07:22 639232388731528337
239 ms 162.215.131.191
19 2026-08-25 07:05 639232378288598612
13 ms 162.215.131.191
18 2026-08-25 06:12 639232346196373643
240 ms 162.215.131.191
17 2026-08-25 05:55 639232336112370741
241 ms 162.215.131.191
16 2026-08-25 05:38 639232326146508970
123 ms 162.215.131.191
15 2026-08-25 05:21 639232316189381720
117 ms 162.215.131.191
14 2026-08-25 05:05 639232306217998913
244 ms 162.215.131.191
13 2026-08-25 04:48 639232296255744174
125 ms 162.215.131.191
12 2026-08-25 04:31 639232286095760789
117 ms 162.215.131.191
11 2026-08-25 04:14 639232276086186273
256 ms 162.215.131.191
10 2026-08-25 03:58 639232265900986425
22 ms 162.215.131.191
9 2026-08-25 03:41 639232255723518075
126 ms 162.215.131.191
8 2026-08-25 03:24 639232245484452890
134 ms 162.215.131.191
7 2026-08-25 03:07 639232235157175331
2031 ms 162.215.131.191
6 2026-08-25 02:13 639232203197189095
256 ms 162.215.131.191
5 2026-08-25 01:56 639232192844564298
226 ms 162.215.131.191
4 2026-08-25 01:39 639232182496008942
243 ms 162.215.131.191
3 2026-08-25 01:22 639232172197053132
240 ms 162.215.131.191
2 2026-08-25 00:28 639232140250307418
238 ms 162.215.131.191
1 2026-08-25 00:11 639232129927860324
240 ms 162.215.131.191