DNS response history for ns2.vercel.app

ns2.vercel.app 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 37 DNS check records, 36 successful responses, 1 failed responses, and 246 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.vercel.app.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

246 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 06:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.198.79.131

Most recently resolved hosting IP on selected date

Successful Responses

36

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.vercel.app

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
37 2026-08-25 06:57 639232378288598612
2115 ms 216.198.79.131
36 2026-08-25 06:57 639232378288598612
2115 ms 64.29.17.131
35 2026-08-25 06:03 639232346196373643
27 ms 64.29.17.3
34 2026-08-25 06:03 639232346196373643
27 ms 216.198.79.3
33 2026-08-25 05:47 639232336112370741
4 ms 216.198.79.67
32 2026-08-25 05:47 639232336112370741
4 ms 64.29.17.67
31 2026-08-25 05:30 639232326146508970
2016 ms 216.198.79.131
30 2026-08-25 05:30 639232326146508970
2016 ms 64.29.17.131
29 2026-08-25 05:13 639232316189381720
5 ms 216.198.79.67
28 2026-08-25 05:13 639232316189381720
5 ms 64.29.17.67
27 2026-08-25 04:57 639232306217998913
6 ms 64.29.17.195
26 2026-08-25 04:57 639232306217998913
6 ms 216.198.79.195
25 2026-08-25 04:40 639232296255744174
22 ms 64.29.17.131
24 2026-08-25 04:40 639232296255744174
22 ms 216.198.79.131
23 2026-08-25 04:23 639232286095760789
53 ms 216.198.79.195
22 2026-08-25 04:23 639232286095760789
53 ms 64.29.17.195
21 2026-08-25 04:06 639232276086186273
15 ms 64.29.17.67
20 2026-08-25 04:06 639232276086186273
15 ms 216.198.79.67
19 2026-08-25 03:50 639232265900986425
4 ms 64.29.17.3
18 2026-08-25 03:50 639232265900986425
4 ms 216.198.79.3
17 2026-08-25 03:33 639232255723518075
35 ms 216.198.79.195
16 2026-08-25 03:33 639232255723518075
35 ms 64.29.17.195
15 2026-08-25 03:15 639232245484452890
24 ms 64.29.17.67
14 2026-08-25 03:15 639232245484452890
24 ms 216.198.79.67
13 2026-08-25 02:58 639232235157175331
5 ms 64.29.17.195
12 2026-08-25 02:58 639232235157175331
5 ms 216.198.79.195
11 2026-08-25 02:05 639232203197189095
-
10 2026-08-25 01:48 639232192844564298
15 ms 216.198.79.195
9 2026-08-25 01:48 639232192844564298
15 ms 64.29.17.195
8 2026-08-25 01:30 639232182496008942
5 ms 216.198.79.3
7 2026-08-25 01:30 639232182496008942
5 ms 64.29.17.3
6 2026-08-25 01:13 639232172197053132
12 ms 64.29.17.195
5 2026-08-25 01:13 639232172197053132
12 ms 216.198.79.195
4 2026-08-25 00:20 639232140250307418
44 ms 64.29.17.3
3 2026-08-25 00:20 639232140250307418
44 ms 216.198.79.3
2 2026-08-25 00:03 639232129927860324
20 ms 216.198.79.67
1 2026-08-25 00:03 639232129927860324
20 ms 64.29.17.67