DNS response history for ns2.britishcolumbiagolf.org

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

34

Historical checks stored for this nameserver on selected date

Average Latency

425 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.199.201.113

Most recently resolved hosting IP on selected date

Successful Responses

34

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.britishcolumbiagolf.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
34 2026-08-25 11:50 639232545839529039
312 ms 192.199.201.113
33 2026-08-25 11:33 639232535349285207
595 ms 192.199.201.113
32 2026-08-25 11:15 639232524938080723
736 ms 192.199.201.113
31 2026-08-25 10:22 639232492740373468
155 ms 192.199.201.113
30 2026-08-25 10:04 639232482235303141
565 ms 192.199.201.113
29 2026-08-25 09:47 639232471861770303
557 ms 192.199.201.113
28 2026-08-25 09:30 639232461630217327
166 ms 192.199.201.113
27 2026-08-25 09:13 639232451282965990
355 ms 192.199.201.113
26 2026-08-25 08:55 639232440814614938
783 ms 192.199.201.113
25 2026-08-25 08:38 639232430410720425
736 ms 192.199.201.113
24 2026-08-25 08:21 639232420003096185
1478 ms 192.199.201.113
23 2026-08-25 08:03 639232409467287444
1754 ms 192.199.201.113
22 2026-08-25 07:46 639232399077195997
702 ms 192.199.201.113
21 2026-08-25 07:28 639232388731528337
152 ms 192.199.201.113
20 2026-08-25 07:11 639232378288598612
153 ms 192.199.201.113
19 2026-08-25 06:17 639232346196373643
168 ms 192.199.201.113
18 2026-08-25 06:00 639232336112370741
154 ms 192.199.201.113
17 2026-08-25 05:44 639232326146508970
153 ms 192.199.201.113
16 2026-08-25 05:27 639232316189381720
154 ms 192.199.201.113
15 2026-08-25 05:11 639232306217998913
277 ms 192.199.201.113
14 2026-08-25 04:54 639232296255744174
153 ms 192.199.201.113
13 2026-08-25 04:37 639232286095760789
156 ms 192.199.201.113
12 2026-08-25 04:20 639232276086186273
160 ms 192.199.201.113
11 2026-08-25 04:03 639232265900986425
153 ms 192.199.201.113
10 2026-08-25 03:47 639232255723518075
3 ms 192.199.201.113
9 2026-08-25 03:29 639232245484452890
153 ms 192.199.201.113
8 2026-08-25 03:12 639232235157175331
154 ms 192.199.201.113
7 2026-08-25 02:19 639232203197189095
574 ms 192.199.201.113
6 2026-08-25 02:02 639232192844564298
543 ms 192.199.201.113
5 2026-08-25 01:45 639232182496008942
322 ms 192.199.201.113
4 2026-08-25 01:27 639232172197053132
581 ms 192.199.201.113
3 2026-08-25 00:34 639232140250307418
313 ms 192.199.201.113
2 2026-08-25 00:17 639232129927860324
577 ms 192.199.201.113
1 2026-08-25 00:00 639232119551972438
492 ms 192.199.201.113