DNS response history for ns2.vibe.to

ns2.vibe.to 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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 263 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.vibe.to.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

263 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 06:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.150.16.129

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.vibe.to

Showing DNS history for 2026-08-24 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-24 06:48 639231508078650885
28 ms 216.150.16.129
33 2026-08-24 06:48 639231508078650885
28 ms 216.150.16.193
32 2026-08-24 06:32 639231498210697093
49 ms 216.150.16.65
31 2026-08-24 06:32 639231498210697093
49 ms 216.150.1.129
30 2026-08-24 06:15 639231488109699360
28 ms 216.150.16.193
29 2026-08-24 06:15 639231488109699360
28 ms 216.150.1.193
28 2026-08-24 05:23 639231456772510692
17 ms 216.150.1.193
27 2026-08-24 05:23 639231456772510692
17 ms 216.150.1.65
26 2026-08-24 05:06 639231447084631185
22 ms 216.150.1.193
25 2026-08-24 05:06 639231447084631185
22 ms 216.150.1.65
24 2026-08-24 04:50 639231437208519473
33 ms 216.150.1.1
23 2026-08-24 04:50 639231437208519473
33 ms 216.150.1.65
22 2026-08-24 04:33 639231427209627490
37 ms 216.150.16.1
21 2026-08-24 04:33 639231427209627490
37 ms 216.150.1.65
20 2026-08-24 03:41 639231395791246644
2085 ms 216.150.16.193
19 2026-08-24 03:41 639231395791246644
2085 ms 216.150.1.129
18 2026-08-24 03:25 639231386075551458
3 ms 216.150.16.193
17 2026-08-24 03:25 639231386075551458
3 ms 216.150.16.1
16 2026-08-24 03:08 639231376208713791
11 ms 216.150.16.1
15 2026-08-24 03:08 639231376208713791
11 ms 216.150.16.193
14 2026-08-24 02:52 639231366170589276
33 ms 216.150.16.129
13 2026-08-24 02:52 639231366170589276
33 ms 216.150.16.65
12 2026-08-24 01:59 639231334732159368
16 ms 216.150.1.1
11 2026-08-24 01:59 639231334732159368
16 ms 216.150.1.193
10 2026-08-24 01:43 639231325035670078
2035 ms 216.150.1.1
9 2026-08-24 01:43 639231325035670078
2035 ms 216.150.1.193
8 2026-08-24 01:27 639231315132253837
13 ms 216.150.16.193
7 2026-08-24 01:27 639231315132253837
13 ms 216.150.16.65
6 2026-08-24 01:10 639231305014280808
40 ms 216.150.16.1
5 2026-08-24 01:10 639231305014280808
40 ms 216.150.1.1
4 2026-08-24 00:18 639231273779380675
17 ms 216.150.16.129
3 2026-08-24 00:18 639231273779380675
17 ms 216.150.16.193
2 2026-08-24 00:02 639231264180839154
12 ms 216.150.1.193
1 2026-08-24 00:02 639231264180839154
12 ms 216.150.16.129