Multiple Vercel Deployments Unreachable from Rwanda — Possible Regional Routing Issue Category - Help

Hello Vercel team and community,

I am experiencing a regional connectivity issue from Rwanda affecting multiple Vercel deployments.

Affected deployments:

https://togetherwerise.vercel.app/

togetherwerise.vercel.app

TOGETHER WE RISE ASSOCIATION

A comprehensive SaaS platform for cooperative societies and associations, managing roles, savings, loans, penalties, fees, and generating reports.

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.

Update — August 28, 2026

I have completed additional testing from the same Rwanda network.

An important finding is that Vercel itself is reachable normally:

curl -Iv --connect-timeout 15 https://vercel.com

Vercel

Agentic Infrastructure - Vercel

The autonomous stack for every app and agent.

returns HTTP/1.1 200 OK and successfully completes the TLS connection.

However, all three affected *.vercel.app deployments still time out before the TLS handshake:

The affected deployments resolve to the following edge IP ranges:

64.29.17.0/24 216.198.79.0/24

For example:

togetherwerise.vercel.app → 64.29.17.67 → 216.198.79.67

HTTPS connection: → Connection timed out after 15 seconds

This strongly suggests that the issue is specific to connectivity/routing to the Vercel deployment edge IP ranges rather than a deployment or application problem.

I would appreciate it if a Vercel engineer could investigate whether traffic from Rwanda or our upstream ISP is currently having a routing/BGP/transit issue reaching these edge ranges.

I am also happy to provide the complete nslookup, tracert and curl diagnostics.

Thank you.

I also contacted Vercel Support using the email address associated with my Vercel account, but I received an automated response stating that the inbox is no longer monitored and that requests sent there will not be processed.

I am therefore following up here because this is not an account recovery issue.

My Vercel account is accessible. The problem is regional network connectivity from Rwanda to multiple Vercel deployments.

DNS resolution works correctly, but TCP/443 connections to the assigned Vercel edge IPs time out before TLS:

togetherwerise.vercel.app

64.29.17.67 216.198.79.67

From the same Rwanda network, https://vercel.com works normally and returns HTTP 200.

Vercel

Agentic Infrastructure - Vercel

The autonomous stack for every app and agent.

The same issue affects multiple independent deployments:

togetherwerise.vercel.app smartlessonplan.vercel.app gsgatict.vercel.app

Could a Vercel staff member please review this as a possible regional routing/peering/Anycast issue affecting Rwanda?

I can provide the complete DNS, traceroute and curl diagnostics.

Still unresolved — Requesting help from Vercel Staff / Network Experts

Hi everyone,

I’m following up on this issue because it is still persistent and has not been resolved.

I’m currently using the Vercel Hobby plan, and I understand that some support options may be limited on this plan. However, this does not appear to be a project-specific or application-code issue.

The problem is that multiple independent Vercel deployments are unreachable from Rwanda, while Vercel’s main website (vercel.com) remains accessible from the same network.

I have tested several different deployments, and they consistently fail with connection timeouts. The behavior occurs before the application can establish a normal HTTPS/TLS connection, which makes me suspect a possible network routing, peering, transit, Anycast, or Vercel edge connectivity issue affecting traffic from Rwanda.

What makes this particularly concerning is that the issue has persisted for several days and affects more than one of my projects.

I would really appreciate help from:

A Vercel staff member / Network Engineer
Anyone with experience investigating Vercel edge connectivity or regional routing
Other Vercel users in Rwanda or East Africa who may be experiencing the same problem
Network engineers who can help determine whether this is related to ISP routing/peering or Vercel edge infrastructure

If someone from Vercel could take a quick look at the affected IP ranges, routing path, or edge connectivity from Rwanda, that would be extremely helpful.

I’m happy to provide additional diagnostics such as:

curl -4 -v output
traceroute / MTR
DNS resolution results
Source ISP / ASN information
Affected Vercel deployment URLs
Timestamps of failed connection attempts
Results from different networks if needed

I’m not necessarily asking for a plan upgrade or account-level support. I’m mainly trying to determine whether this is a known regional network issue and, if possible, get guidance on how to resolve or work around it.

If anyone has encountered a similar Vercel connectivity problem in Rwanda, Morocco, Nigeria, Brazil, or another region and knows how it was resolved, I would also really appreciate hearing from you.

This issue is currently blocking access to my deployed applications from Rwanda, so any technical guidance or investigation would be greatly appreciated.

Thank you to anyone who can take a look or point me toward the right person/team.

Update — Vercel Support Agent confirmed this should be investigated as a regional connectivity issue

I contacted the Vercel Support Agent regarding this persistent connectivity problem.

The Agent confirmed that the issue involves regional routing/network-level connectivity and recommended that I provide network diagnostics through the Vercel Community. However, because I am currently on the Hobby plan, a Support Case cannot be opened directly for this inquiry.

I am therefore posting the issue here and asking for help from Vercel staff, network engineers, or experienced community members.

The problem is still ongoing:

Multiple independent Vercel deployments are unreachable from Rwanda.
The same deployments consistently time out from the affected network.
vercel.com itself remains reachable.
The failure occurs at the network connection level, before a normal HTTPS/TLS connection can be established.
This is not limited to one application or one deployment.
The issue has persisted for several days and is currently blocking access to my deployed applications from Rwanda.

I will also provide the results from the Vercel Network Debug tool as recommended by Vercel Support.

If anyone from Vercel can review the diagnostic report and determine whether this is related to Vercel Edge routing, Anycast, upstream transit, peering, or ISP connectivity affecting Rwanda, I would greatly appreciate it.

I would especially appreciate it if a Vercel engineer could confirm whether this behavior is known or whether there is any active investigation into connectivity from Rwanda/East Africa.

I am happy to provide any additional network diagnostics required.

The main question I would like help answering is: Is there currently a network path/connectivity problem between networks in Rwanda and Vercel's Edge infrastructure?

Thank you to everyone who can help investigate this.

The support team is aware and investigating. Thank you for reporting it