DNS response history for ns2.brimsbg.org

ns2.brimsbg.org 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 30 DNS check records, 30 successful responses, 0 failed responses, and 171 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.brimsbg.org.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

171 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.134.223.248

Most recently resolved hosting IP on selected date

Successful Responses

30

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.brimsbg.org

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
30 2026-08-25 10:09 639232492740373468
48 ms 91.134.223.248
29 2026-08-25 09:52 639232482235303141
161 ms 91.134.223.248
28 2026-08-25 09:34 639232471861770303
53 ms 91.134.223.248
27 2026-08-25 09:17 639232461630217327
170 ms 91.134.223.248
26 2026-08-25 09:00 639232451282965990
172 ms 91.134.223.248
25 2026-08-25 08:43 639232440814614938
81 ms 91.134.223.248
24 2026-08-25 08:25 639232430410720425
45 ms 91.134.223.248
23 2026-08-25 08:08 639232420003096185
45 ms 91.134.223.248
22 2026-08-25 07:50 639232409467287444
183 ms 91.134.223.248
21 2026-08-25 07:33 639232399077195997
46 ms 91.134.223.248
20 2026-08-25 07:16 639232388731528337
384 ms 91.134.223.248
19 2026-08-25 06:59 639232378288598612
63 ms 91.134.223.248
18 2026-08-25 06:05 639232346196373643
102 ms 91.134.223.248
17 2026-08-25 05:48 639232336112370741
47 ms 91.134.223.248
16 2026-08-25 05:32 639232326146508970
159 ms 91.134.223.248
15 2026-08-25 05:15 639232316189381720
50 ms 91.134.223.248
14 2026-08-25 04:58 639232306217998913
292 ms 91.134.223.248
13 2026-08-25 04:42 639232296255744174
38 ms 91.134.223.248
12 2026-08-25 04:25 639232286095760789
47 ms 91.134.223.248
11 2026-08-25 04:08 639232276086186273
17 ms 91.134.223.248
10 2026-08-25 03:51 639232265900986425
41 ms 91.134.223.248
9 2026-08-25 03:34 639232255723518075
60 ms 91.134.223.248
8 2026-08-25 03:17 639232245484452890
41 ms 91.134.223.248
7 2026-08-25 03:00 639232235157175331
2159 ms 91.134.223.248
6 2026-08-25 02:07 639232203197189095
44 ms 91.134.223.248
5 2026-08-25 01:49 639232192844564298
42 ms 91.134.223.248
4 2026-08-25 01:32 639232182496008942
59 ms 91.134.223.248
3 2026-08-25 01:15 639232172197053132
273 ms 91.134.223.248
2 2026-08-25 00:22 639232140250307418
49 ms 91.134.223.248
1 2026-08-25 00:05 639232129927860324
157 ms 91.134.223.248