DNS response history for ns2.briskfx.com

ns2.briskfx.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 581 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.briskfx.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

581 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.163.227.170

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.briskfx.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:01 639232482235303141
317 ms 108.163.227.170
28 2026-08-25 09:43 639232471861770303
228 ms 108.163.227.170
27 2026-08-25 09:26 639232461630217327
564 ms 108.163.227.170
26 2026-08-25 09:09 639232451282965990
550 ms 108.163.227.170
25 2026-08-25 08:51 639232440814614938
2225 ms 108.163.227.170
24 2026-08-25 08:34 639232430410720425
577 ms 108.163.227.170
23 2026-08-25 08:17 639232420003096185
2370 ms 108.163.227.170
22 2026-08-25 07:59 639232409467287444
221 ms 108.163.227.170
21 2026-08-25 07:42 639232399077195997
570 ms 108.163.227.170
20 2026-08-25 07:25 639232388731528337
232 ms 108.163.227.170
19 2026-08-25 07:07 639232378288598612
223 ms 108.163.227.170
18 2026-08-25 06:14 639232346196373643
4 ms 108.163.227.170
17 2026-08-25 05:57 639232336112370741
5 ms 108.163.227.170
16 2026-08-25 05:40 639232326146508970
239 ms 108.163.227.170
15 2026-08-25 05:23 639232316189381720
222 ms 108.163.227.170
14 2026-08-25 05:07 639232306217998913
225 ms 108.163.227.170
13 2026-08-25 04:50 639232296255744174
564 ms 108.163.227.170
12 2026-08-25 04:33 639232286095760789
223 ms 108.163.227.170
11 2026-08-25 04:16 639232276086186273
225 ms 108.163.227.170
10 2026-08-25 04:00 639232265900986425
566 ms 108.163.227.170
9 2026-08-25 03:43 639232255723518075
564 ms 108.163.227.170
8 2026-08-25 03:26 639232245484452890
567 ms 108.163.227.170
7 2026-08-25 03:09 639232235157175331
224 ms 108.163.227.170
6 2026-08-25 02:15 639232203197189095
222 ms 108.163.227.170
5 2026-08-25 01:58 639232192844564298
221 ms 108.163.227.170
4 2026-08-25 01:41 639232182496008942
227 ms 108.163.227.170
3 2026-08-25 01:24 639232172197053132
4026 ms 108.163.227.170
2 2026-08-25 00:30 639232140250307418
228 ms 108.163.227.170
1 2026-08-25 00:13 639232129927860324
227 ms 108.163.227.170