Hello Vercel team and community,
I am experiencing a regional connectivity issue from Rwanda affecting multiple Vercel deployments.
Affected deployments:
All deployments build and deploy successfully on Vercel.
The important part is that Vercel itself is reachable from the same network.
For example:
curl -Iv --connect-timeout 15 https://vercel.com
This successfully establishes a TLS connection and returns:
HTTP/1.1 200 OK Server: Vercel
However, connecting to the affected deployment fails:
curl -Iv --connect-timeout 15 https://togetherwerise.vercel.app/
Result:
Connection timed out after 15009 milliseconds curl: (28) Connection timed out
DNS resolution is successful:
togetherwerise.vercel.app → 64.29.17.67 → 216.198.79.67
smartlessonplan.vercel.app → 64.29.17.3 → 216.198.79.3
gsgatict.vercel.app → 216.198.79.3 → 64.29.17.3
Traceroute from Rwanda reaches the local ISP network but then stops responding before reaching the Vercel destination.
This appears to be different from a deployment/build/application problem because:
- DNS resolves correctly.
- The deployments are successfully deployed.
- Vercel.com itself is reachable from the same network.
- Multiple independent Vercel deployments are affected.
- HTTPS connections to the deployment edge IPs time out.
Could Vercel engineers please investigate whether there is a regional routing, BGP, transit, firewall, or Vercel edge connectivity issue affecting traffic from Rwanda to these deployment IP ranges?
If possible, I would also appreciate this being escalated to the Vercel Network/Infrastructure team rather than treated as an individual deployment issue.
I can provide the complete nslookup, tracert, and curl diagnostics if needed.
Thank you.
