🚨 Multiple Vercel Domains Fail on Orange Morocco ISP but Work via Germany & Spain VPN

Help
, ,
1

:police_car_light: All Vercel Custom Domains Only Work Through VPN (Germany/Spain) – Possible ISP Routing or DNS Issue

Hello Vercel Community :waving_hand:,

I’m experiencing a very unusual issue affecting all of my Vercel-hosted custom domains.

:clipboard: Environment

  • Hosting: Vercel

  • Framework: Next.js

  • Deployment Status: :white_check_mark: Successful

  • Domain Status: :white_check_mark: Valid Configuration

  • SSL: :white_check_mark: Active

  • ISP: Orange

:white_check_mark: What Works

  • :white_check_mark: All deployments complete successfully.

  • :white_check_mark: Every .vercel.app deployment URL works perfectly.

  • :white_check_mark: Vercel Dashboard shows Valid Configuration for every custom domain.

  • :white_check_mark: Domains are correctly attached to their respective projects.

  • :white_check_mark: When connected to a VPN (Germany or Spain), every custom domain loads instantly.

:cross_mark: What Doesn’t Work

On my normal Orange internet connection:

  • :cross_mark: None of my custom domains load.

  • :cross_mark: The issue affects multiple Vercel domains simultaneously.

  • :cross_mark: The browser eventually times out or cannot reach the website.

:magnifying_glass_tilted_left: Troubleshooting Already Performed

I have already tried all of the following:

  • :white_check_mark: Restarted my router

  • :white_check_mark: Forgot and reconnected to Wi-Fi

  • :white_check_mark: Flushed local DNS (ipconfig /flushdns)

  • :white_check_mark: Restarted the computer

  • :white_check_mark: Tested different browsers

  • :white_check_mark: Verified the Vercel configuration

  • :white_check_mark: Confirmed deployments are healthy

  • :white_check_mark: Confirmed .vercel.app URLs work

  • :white_check_mark: Tested with VPN

:globe_showing_europe_africa: Important Finding

As soon as I connect through a VPN:

  • :germany: Germany → :white_check_mark: Works

  • :spain: Spain (Server 1) → :white_check_mark: Works

  • :spain: Spain (Server 2) → :white_check_mark: Works

Disconnecting the VPN immediately causes all custom domains to stop working again.

This strongly suggests the websites themselves are online and reachable.

:thinking: My Current Conclusion

Because:

  • All domains fail simultaneously

  • .vercel.app works

  • VPN works immediately

  • Vercel reports Valid Configuration

I suspect this may be related to:

  • :globe_with_meridians: ISP routing

  • :globe_with_meridians: DNS propagation/caching

  • :globe_with_meridians: Peering between Orange and the Vercel Edge Network

rather than a deployment or application issue.

:red_question_mark:Questions

Has anyone experienced something similar?

Could a Vercel team member please verify whether there are any routing, DNS, or edge network issues affecting connectivity from certain ISPs?

If there are any additional diagnostic commands or logs that would help, I’m happy to provide them.

Thank you very much for your time and assistance! :folded_hands:

2

The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points.

3

Hello, I’m experiencing the exact same issue unfortunately

Environment:

  • Project: mre-agadir (mre-agadir-jade.vercel.app)
  • Custom domains: mre-a-agadir.ma and www.mre-a-agadir.ma
  • Apex A record: 216.198.79.1 (same IP reported in this thread)
  • Framework: Next.js, deployed successfully, domains show “Valid Configuration”
  • Plan: Hobby

What works:

  • mre-agadir-jade.vercel.app loads instantly, no issue
  • The custom domain loads perfectly when using a VPN (tested via Germany)

What doesn’t work:

  • Both mre-a-agadir.ma and www.mre-a-agadir.ma consistently time out when accessed
    directly from Morocco
  • Confirmed across multiple ISPs (home Wi-Fi, inwi mobile data, other operators)
    and multiple devices (phones + computers)
  • Confirmed even after manually setting Google Public DNS (8.8.8.8) on a mobile
    device — same timeout, which rules out local ISP DNS resolver caching as the
    cause

This looks like a routing/peering issue between Vercel’s edge network and
Moroccan ISPs (Orange, Meditelecom, inwi), affecting the 216.198.79.1 apex IP
specifically, rather than a DNS or application configuration problem.

Could someone from the Vercel networking team look into this? Happy to provide
additional diagnostics (traceroute/mtr from within Morocco) if useful.

Thank you!

4

Hi Hassan,

Thank you for checking this.

Unfortunately, the problem is still happening, and I want to clarify one important point: this is not limited to one Orange Wi-Fi router or one local network.

I tested the domains through multiple different Orange connections:

  • Orange Wi-Fi network #1 → :cross_mark: Not working

  • A completely different Orange Wi-Fi network → :cross_mark: Not working

  • Orange 4G/mobile data from my phone → :cross_mark: Not working

  • Germany VPN → :white_check_mark: Working

  • Spain VPN → :white_check_mark: Working

  • Other VPN connections → :white_check_mark: Working

And the problem affects all 4 of my .com domains hosted on Vercel.

The Vercel deployments are healthy, the domains show Valid Configuration, SSL is active, and the .vercel.app URLs work normally.

The most significant observation is:

Any connection using Orange Morocco → custom Vercel domains do not load.
When the connection is routed through a VPN outside Orange → the exact same domains load immediately.

Since I tested both different Orange fixed-line networks and Orange 4G, I think we can rule out a single router, Wi-Fi network, or local DNS cache.

This makes me think the issue may be somewhere at the Orange Morocco ↔ Vercel network/routing/peering/DNS/connectivity level, rather than with my individual connection or Vercel projects.

Could you please check whether there is any known issue affecting Vercel domains from Orange Morocco, or whether Vercel can investigate the connectivity/routing from Orange ASNs toward the Vercel Edge Network?

I can provide nslookup, tracert, curl, DNS resolver results, destination IPs, timestamps, and any other diagnostics needed.

The issue is still completely blocking access to all 4 domains from Orange Morocco, while they remain accessible through VPN and other networks.

Thank you :folded_hands:

5

Orange Poland similar problems. Anyone in contact with Orange?

6

Thanks Pawdd for sharing this. and I’ve already contacted Orange Morocco about it, but unfortunately I haven’t received any response so far.

What makes the issue particularly clear in my case is that all of my Vercel custom domains fail on my normal Orange connection, while they work immediately when I connect through VPN servers in Germany or Spain.

I’ve also confirmed that the deployments, SSL, and Vercel domain configurations are all valid, and the .vercel.app URLs continue to work normally.

At this point, it really looks like an Orange/Vercel routing, peering, or DNS connectivity issue rather than a problem with the projects themselves.

Hopefully someone from Vercel can investigate whether there’s an issue affecting Orange Morocco users.

7

Hi, they did fix it for me. From what I understand they are actually filtering domains if they classify them as malware. That process might be automated. My case it was false positive. I had to contact Orange CERT Poland. It took them like 48 hours or less, so check your code, scan your website and contact them. Vercel is not to blame. Good luck!

8

It likes like an ISP may have blocked some of Vercel’s IP ranges. That the *.vercel.app address works while the custom domain doesn’t makes me more sure of that since they typically use different IPs.

I shared your reports with our team so they can investigate further. Thanks for letting us know :person_bowing:

9

Some people found that the general-purpose IP address helped as a temporary workaround

10

In my case I did try to change DNS records like CNAME or IP values as suggested by community posts. Nothing worked. Even moved from my trusted 3rd party DNS to Vercel own DNS, still no happy days. What actually happened and all tests confirmed they were filtering at Orange mine specific domain name (!sic) so that their resolver did not work for mine *.com, but *.vercal.app was fine all the time. That was pretty hard and crazy to find as Orange users had NXDOMAIN, and mine logs were empty. I had to find Orange network to test this, also made a special website for nontechnical users to provide some diagnostics. Only by coincidence and one users persistence I tracked the issues origin.

11

We’re seeing a connectivity issue affecting users on Orange Morocco when accessing domains hosted on Vercel.

Our domain resolves correctly via DNS, but connections to Vercel edge IPs are timing out on port 443.

Example from an Orange Morocco connection:

Host soqi.app:443 was resolved.
IPv6: (none)
IPv4: 64.29.17.65, 64.29.17.1

Trying 64.29.17.65:443...
IPv4 connect timeout

Trying 64.29.17.1:443...
IPv4 connect timeout

Failed to connect to soqi.app port 443: Timeout was reached

From other networks, the same domain works normally and returns a valid Vercel response.

We also verified:

  • Vercel nameservers are configured correctly.

  • The domain and wildcard *.soqi.app are correctly attached to the Vercel project.

  • The wildcard SSL certificate is valid.

  • The application itself responds normally when accessed from other networks.

This looks like a routing/reachability issue between Orange Morocco and Vercel edge ranges, particularly 64.29.17.0/24 and possibly 216.198.79.0/24.

Is the Vercel team aware of any ongoing routing issue affecting Orange Morocco / AS36925?

Domain affected: soqi.app and its subdomains.

12

Thanks Pawdd — this is very useful information.

I’ll definitely check the domains/code and contact Orange Morocco CERT as well.

In my case, though, the behavior seems slightly different from your Orange Poland case. Our domains resolve correctly through DNS, but connections to the Vercel edge IPs time out on port 443. The .vercel.app URLs continue to work normally, while the custom domains fail from Orange Morocco and work immediately through Germany/Spain VPN.

I’m seeing this across multiple Vercel custom domains, including different projects, so it doesn’t appear to be isolated to a single website.

Amy Egan — your observation about ISP blocking of Vercel IP ranges seems especially relevant here. I’ve shared the affected IP ranges and diagnostics above so the Vercel team can investigate the Orange Morocco / AS36925 path.

I’ll also contact Orange Morocco CERT and ask them specifically to check whether the affected domains or Vercel IP ranges are being filtered.

Thanks again for sharing your experience — hopefully this helps narrow down the cause. :+1:

13

Quick update: the temporary workaround worked for me on Orange Morocco.

The issue was affecting both the apex domain and wildcard subdomains. DNS was resolving correctly, but connections to the newer Vercel edge IPs were timing out on port 443 from Orange.

I changed the DNS records temporarily to:

@     A       76.76.21.21
*     A       76.76.21.21
www   CNAME   cname.vercel-dns-0.com.

After propagation, both the root domain and wildcard subdomains started working normally again from Orange Morocco.

Before the change, the domains were resolving to IPs in ranges such as:

64.29.17.0/24
216.198.79.0/24

and TCP connections on port 443 were timing out.

I also tested 76.76.21.21 directly with curl --resolve before changing DNS, and both the apex domain and wildcard subdomain connected successfully with valid TLS and normal Vercel responses.

So this workaround is working for me as a temporary solution while the Orange Morocco / Vercel routing issue is being investigated.