DNS response history for ns2.brivadib.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

388 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.97.168.150

Most recently resolved hosting IP on selected date

Successful Responses

29

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.brivadib.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
29 2026-08-25 10:00 639232482235303141
290 ms 31.97.168.150
28 2026-08-25 09:43 639232471861770303
280 ms 31.97.168.150
27 2026-08-25 09:26 639232461630217327
285 ms 31.97.168.150
26 2026-08-25 09:09 639232451282965990
296 ms 31.97.168.150
25 2026-08-25 08:51 639232440814614938
288 ms 31.97.168.150
24 2026-08-25 08:34 639232430410720425
2310 ms 31.97.168.150
23 2026-08-25 08:17 639232420003096185
9 ms 31.97.168.150
22 2026-08-25 07:59 639232409467287444
287 ms 31.97.168.150
21 2026-08-25 07:42 639232399077195997
236 ms 31.97.168.150
20 2026-08-25 07:24 639232388731528337
288 ms 31.97.168.150
19 2026-08-25 07:07 639232378288598612
288 ms 31.97.168.150
18 2026-08-25 06:13 639232346196373643
282 ms 31.97.168.150
17 2026-08-25 05:56 639232336112370741
283 ms 31.97.168.150
16 2026-08-25 05:40 639232326146508970
292 ms 31.97.168.150
15 2026-08-25 05:23 639232316189381720
8 ms 31.97.168.150
14 2026-08-25 05:07 639232306217998913
10 ms 31.97.168.150
13 2026-08-25 04:50 639232296255744174
282 ms 31.97.168.150
12 2026-08-25 04:33 639232286095760789
285 ms 31.97.168.150
11 2026-08-25 04:16 639232276086186273
281 ms 31.97.168.150
10 2026-08-25 04:00 639232265900986425
296 ms 31.97.168.150
9 2026-08-25 03:43 639232255723518075
209 ms 31.97.168.150
8 2026-08-25 03:25 639232245484452890
295 ms 31.97.168.150
7 2026-08-25 03:08 639232235157175331
2231 ms 31.97.168.150
6 2026-08-25 02:15 639232203197189095
205 ms 31.97.168.150
5 2026-08-25 01:58 639232192844564298
279 ms 31.97.168.150
4 2026-08-25 01:41 639232182496008942
281 ms 31.97.168.150
3 2026-08-25 01:23 639232172197053132
297 ms 31.97.168.150
2 2026-08-25 00:30 639232140250307418
287 ms 31.97.168.150
1 2026-08-25 00:13 639232129927860324
281 ms 31.97.168.150