Hello Vercel team,
I would appreciate help investigating an IP-specific connectivity incident affecting my portfolio, https://jorconde.com (Hobby plan), on 30 October 2026. The site has recovered after changing its apex A record, but I would like to understand the cause and reduce recurrence.
Observed symptoms
- I could not reach the domain using Claro in Argentina. The exact incident start and geographic scope are unknown.
- Diagnostic tests around 15:49–16:26 UTC showed connection timeouts to 216.198.79.1.
- Requests to the same hostname directed to 64.29.17.1 returned HTTP 200 with certificate validation enabled. 76.76.21.21 also returned 200.
- These curl tests were performed from an assistant diagnostic environment whose ISP was not independently established, so they should not be treated as traces originating on Claro.
Configuration and recovery
- The domain remained verified. Vercel's domain configuration API reported misconfigured:false and no conflicts, with both 216.198.79.1 and 64.29.17.1 in the rank-1 recommended IPv4 values.
- DNS is hosted at Spaceship. We changed the apex A from 216.198.79.1 to 64.29.17.1, then reduced TTL from 1800 to 300 seconds. No code change or new deployment was needed.
- By approximately 16:19 UTC, normal DNS/HTTPS requests and browser rendering worked, and I independently confirmed recovery. The old IP still timed out in a comparison around 16:26 UTC.
- www retains the recommended CNAME 5af022cf179d4e85.vercel-dns-017.com and redirects to the apex.
Reproduction used during the incident
date/time: 30 October 2026, approximately 16:26 UTC
curl -I --connect-timeout 6 --max-time 10 --resolve jorconde.com:443:216.198.79.1 https://jorconde.com/en
Result: curl (28), connection timed out after approximately 6 seconds.
curl -I --connect-timeout 6 --max-time 10 --resolve jorconde.com:443:64.29.17.1 https://jorconde.com/en Result: HTTP 200 OK, Server: Vercel.
Questions
- Was there a known connectivity, routing or filtering event affecting 216.198.79.1 in this time window? Could Vercel staff or the network team review this evidence?
- Is retaining 64.29.17.1 with TTL 300 the supported long-term configuration for this domain? The Vercel Help assistant said it was valid, but did not establish a root cause.
- What additional diagnostics from the affected network would help distinguish an upstream/ISP issue from a Vercel-side issue, and what measures would reduce recurrence for visitors to the existing domain links?
Vercel Help directed us here because the Hobby case form does not provide dedicated CDN / Edge Network support. We have not collected traceroutes from the Claro device yet, and are not assigning responsibility or claiming a global outage. Thank you.