DNS response history for ns2.yachtcharterbase.com

ns2.yachtcharterbase.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 31 DNS check records, 30 successful responses, 1 failed responses, and 202 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.yachtcharterbase.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

202 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.139.5.159

Most recently resolved hosting IP on selected date

Successful Responses

30

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.yachtcharterbase.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
31 2026-08-25 11:05 639232524938080723
52 ms 185.139.5.159
30 2026-08-25 10:11 639232492740373468
78 ms 185.139.5.159
29 2026-08-25 09:54 639232482235303141
98 ms 185.139.5.159
28 2026-08-25 09:36 639232471861770303
76 ms 185.139.5.159
27 2026-08-25 09:19 639232461630217327
10 ms 185.139.5.159
26 2026-08-25 09:02 639232451282965990
117 ms 185.139.5.159
25 2026-08-25 08:44 639232440814614938
100 ms 185.139.5.159
24 2026-08-25 08:27 639232430410720425
72 ms 185.139.5.159
23 2026-08-25 08:10 639232420003096185
88 ms 185.139.5.159
22 2026-08-25 07:52 639232409467287444
2049 ms 185.139.5.159
21 2026-08-25 07:35 639232399077195997
75 ms 185.139.5.159
20 2026-08-25 07:18 639232388731528337
24 ms 185.139.5.159
19 2026-08-25 07:00 639232378288598612
122 ms 185.139.5.159
18 2026-08-25 06:07 639232346196373643
87 ms 185.139.5.159
17 2026-08-25 05:50 639232336112370741
40 ms 185.139.5.159
16 2026-08-25 05:33 639232326146508970
24 ms 185.139.5.159
15 2026-08-25 05:17 639232316189381720
4 ms 185.139.5.159
14 2026-08-25 05:00 639232306217998913
102 ms 185.139.5.159
13 2026-08-25 04:44 639232296255744174
76 ms 185.139.5.159
12 2026-08-25 04:27 639232286095760789
85 ms 185.139.5.159
11 2026-08-25 04:10 639232276086186273
2054 ms 185.139.5.159
10 2026-08-25 03:53 639232265900986425
10 ms 185.139.5.159
9 2026-08-25 03:36 639232255723518075
67 ms 185.139.5.159
8 2026-08-25 03:19 639232245484452890
87 ms 185.139.5.159
7 2026-08-25 03:02 639232235157175331
76 ms 185.139.5.159
6 2026-08-25 02:08 639232203197189095
43 ms 185.139.5.159
5 2026-08-25 01:51 639232192844564298
107 ms 185.139.5.159
4 2026-08-25 01:34 639232182496008942
80 ms 185.139.5.159
3 2026-08-25 01:17 639232172197053132
78 ms 185.139.5.159
2 2026-08-25 00:24 639232140250307418
-
1 2026-08-25 00:06 639232129927860324
89 ms 185.139.5.159