DNS response history for ns2.british-waterways.org

ns2.british-waterways.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 389 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.british-waterways.org.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

389 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.254.140.156

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.british-waterways.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:21 639232492740373468
369 ms 192.254.140.156
29 2026-08-25 10:04 639232482235303141
174 ms 192.254.140.156
28 2026-08-25 09:46 639232471861770303
545 ms 192.254.140.156
27 2026-08-25 09:29 639232461630217327
196 ms 192.254.140.156
26 2026-08-25 09:12 639232451282965990
174 ms 192.254.140.156
25 2026-08-25 08:54 639232440814614938
590 ms 192.254.140.156
24 2026-08-25 08:37 639232430410720425
440 ms 192.254.140.156
23 2026-08-25 08:20 639232420003096185
356 ms 192.254.140.156
22 2026-08-25 08:02 639232409467287444
370 ms 192.254.140.156
21 2026-08-25 07:45 639232399077195997
9 ms 192.254.140.156
20 2026-08-25 07:27 639232388731528337
354 ms 192.254.140.156
19 2026-08-25 07:10 639232378288598612
371 ms 192.254.140.156
18 2026-08-25 06:16 639232346196373643
363 ms 192.254.140.156
17 2026-08-25 06:00 639232336112370741
353 ms 192.254.140.156
16 2026-08-25 05:43 639232326146508970
2166 ms 192.254.140.156
15 2026-08-25 05:26 639232316189381720
179 ms 192.254.140.156
14 2026-08-25 05:10 639232306217998913
350 ms 192.254.140.156
13 2026-08-25 04:53 639232296255744174
354 ms 192.254.140.156
12 2026-08-25 04:36 639232286095760789
355 ms 192.254.140.156
11 2026-08-25 04:19 639232276086186273
352 ms 192.254.140.156
10 2026-08-25 04:03 639232265900986425
172 ms 192.254.140.156
9 2026-08-25 03:46 639232255723518075
178 ms 192.254.140.156
8 2026-08-25 03:29 639232245484452890
355 ms 192.254.140.156
7 2026-08-25 03:12 639232235157175331
349 ms 192.254.140.156
6 2026-08-25 02:18 639232203197189095
346 ms 192.254.140.156
5 2026-08-25 02:01 639232192844564298
323 ms 192.254.140.156
4 2026-08-25 01:44 639232182496008942
459 ms 192.254.140.156
3 2026-08-25 01:27 639232172197053132
355 ms 192.254.140.156
2 2026-08-25 00:33 639232140250307418
355 ms 192.254.140.156
1 2026-08-25 00:16 639232129927860324
352 ms 192.254.140.156