All my new and old development domains are not working

Help
,
1

Hello .. suddenly, all my projects with development domains that end with “.vercel.app” have been stopped and the DNS can’t find them. I tried to open the URLs from other devices but the same issue occurred. Even the old projects where I didn’t even edit anything on them have been failed.

All my usage stats are low so it is not a usage issue, I’m on the hobby free plan but I did buy some domains in the past and some are still active and they work fine, the issue is just for the development domains.

image
image841×616 9.7 KB

image
image920×756 48.1 KB

1 Like
2

Hi @mustafaalhasanat, welcome to the Vercel Community!

Sorry that you’re facing this issue. I tried accessing the .vercel.app domains linked to your account and they worked fine.

It can be an ISP issue on your end. If you have a VPN, I’d recommend using that to confirm if you can access the .vercel.app domains.

Can you share which country and ISP you are using?

1 Like
3

Hi .. thanks for the quick respond I really appreciate it :folded_hands:

I live in Jordan, I tried to open the Iphone vpn and open these pages but still facing the same issue. I also tried from different devices, on the Iphone Chrome, Safari, Windows Chrome, MacOs, but nothig works

4

Hi @mustafaalhasanat, thanks for sharing additional information.

Do you have an antivirus or firewall program setup on these devices?

5

No, none at all. I even sent the same url to one of my friends to see if it will work on someone else’s machine but the same issue occurred.

6

I’m testing on this url:

https://kaiser-leap-website.vercel.app/

It was working fine before but now it doesn’t, even though I didn’t change anything

7

Hi @mustafaalhasanat, i see. it is working okay for me.

I’ll talk to our CDN team to see what can be wrong but so far I feel it is an ISP issue.

Can you try opening this one: https://portfolio-sunshine-71.vercel.app?

8

I tried to open it but the same problem occurs

1 Like
9

I can open the site here also, only says: home page with big letter on the top right corner.. (https://kaiser-leap-website.vercel.app/)

1 Like
10

That is what I see:

IMG_2511
IMG_25111179×2556 127 KB

12

Maybe related to CDN of vercel. I heard that they were expanding and upgrading their CDN recently.

2 Likes
13

Can you also run this script and share us the output? GitHub - vercel-support/vercel-connect-debug: A one line script to help debug connection issues to Vercel hosting

2 Likes
14

mustafa@DESKTOP-I5GT5JI:~ $ curl -s https://raw.githubusercontent.com/vercel-support/vercel-connect-debug/main/vercel-debug.sh | bash | tee vercel-debug.txt
Domain to test (e.g. example.com):
kaiser-leap-website.vercel.app
┌───────────────────────────────────────
├─────── STARTING
│
│ Domain to test: kaiser-leap-website.vercel.app
│ Timestamp (UTC): Wed Apr 2 19:37:57 UTC 2025
| Timestamp (Local): Wed Apr 2 22:37:57 +03 2025
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── IP Information

{
“ip”: “91.186.240.169”,
“city”: “Amman”,
“region”: “Amman”,
“country”: “JO”,
“loc”: “31.9552,35.9450”,
“org”: “AS9038 Batelco Jordan”,
“timezone”: “Asia/Amman”,
“readme”: “IP Address data API - IPinfo.io”
}
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 76.76.21.21

PING 76.76.21.21 (76.76.21.21) 56(84) bytes of data.
64 bytes from 76.76.21.21: icmp_seq=1 ttl=235 time=123 ms
64 bytes from 76.76.21.21: icmp_seq=2 ttl=235 time=120 ms
64 bytes from 76.76.21.21: icmp_seq=3 ttl=235 time=122 ms
64 bytes from 76.76.21.21: icmp_seq=4 ttl=235 time=118 ms

— 76.76.21.21 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 117.530/120.597/123.465/2.221 ms

bash: line 56: traceroute: command not found
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 216.198.79.1

PING 216.198.79.1 (216.198.79.1) 56(84) bytes of data.
64 bytes from 216.198.79.1: icmp_seq=1 ttl=243 time=116 ms
64 bytes from 216.198.79.1: icmp_seq=2 ttl=243 time=141 ms
64 bytes from 216.198.79.1: icmp_seq=3 ttl=243 time=127 ms
64 bytes from 216.198.79.1: icmp_seq=4 ttl=243 time=119 ms

— 216.198.79.1 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 115.972/125.695/140.548/9.498 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 216.198.79.65

PING 216.198.79.65 (216.198.79.65) 56(84) bytes of data.
64 bytes from 216.198.79.65: icmp_seq=1 ttl=244 time=159 ms
64 bytes from 216.198.79.65: icmp_seq=2 ttl=244 time=142 ms
64 bytes from 216.198.79.65: icmp_seq=3 ttl=244 time=123 ms
64 bytes from 216.198.79.65: icmp_seq=4 ttl=244 time=132 ms

— 216.198.79.65 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 123.186/139.093/158.925/13.266 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 216.198.79.129

PING 216.198.79.129 (216.198.79.129) 56(84) bytes of data.
64 bytes from 216.198.79.129: icmp_seq=1 ttl=243 time=112 ms
64 bytes from 216.198.79.129: icmp_seq=2 ttl=243 time=133 ms
64 bytes from 216.198.79.129: icmp_seq=3 ttl=243 time=115 ms
64 bytes from 216.198.79.129: icmp_seq=4 ttl=243 time=147 ms

— 216.198.79.129 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 111.912/126.733/147.068/14.373 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 216.198.79.193

PING 216.198.79.193 (216.198.79.193) 56(84) bytes of data.
64 bytes from 216.198.79.193: icmp_seq=1 ttl=244 time=117 ms
64 bytes from 216.198.79.193: icmp_seq=2 ttl=244 time=206 ms
64 bytes from 216.198.79.193: icmp_seq=3 ttl=244 time=129 ms
64 bytes from 216.198.79.193: icmp_seq=4 ttl=244 time=122 ms

— 216.198.79.193 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 117.180/143.584/206.106/36.350 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 64.29.17.1

PING 64.29.17.1 (64.29.17.1) 56(84) bytes of data.
64 bytes from 64.29.17.1: icmp_seq=1 ttl=243 time=112 ms
64 bytes from 64.29.17.1: icmp_seq=2 ttl=243 time=125 ms
64 bytes from 64.29.17.1: icmp_seq=3 ttl=243 time=116 ms
64 bytes from 64.29.17.1: icmp_seq=4 ttl=243 time=141 ms

— 64.29.17.1 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 111.550/123.432/141.452/11.409 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 64.29.17.65

PING 64.29.17.65 (64.29.17.65) 56(84) bytes of data.
64 bytes from 64.29.17.65: icmp_seq=1 ttl=243 time=112 ms
64 bytes from 64.29.17.65: icmp_seq=2 ttl=243 time=136 ms
64 bytes from 64.29.17.65: icmp_seq=3 ttl=243 time=113 ms
64 bytes from 64.29.17.65: icmp_seq=4 ttl=243 time=111 ms

— 64.29.17.65 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 111.096/118.127/136.362/10.551 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 64.29.17.129

PING 64.29.17.129 (64.29.17.129) 56(84) bytes of data.
64 bytes from 64.29.17.129: icmp_seq=1 ttl=244 time=112 ms
64 bytes from 64.29.17.129: icmp_seq=2 ttl=244 time=119 ms
64 bytes from 64.29.17.129: icmp_seq=3 ttl=244 time=108 ms
64 bytes from 64.29.17.129: icmp_seq=4 ttl=244 time=131 ms

— 64.29.17.129 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 108.305/117.564/130.567/8.424 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Testing 64.29.17.193

PING 64.29.17.193 (64.29.17.193) 56(84) bytes of data.
64 bytes from 64.29.17.193: icmp_seq=1 ttl=236 time=140 ms
64 bytes from 64.29.17.193: icmp_seq=2 ttl=236 time=130 ms
64 bytes from 64.29.17.193: icmp_seq=3 ttl=236 time=118 ms
64 bytes from 64.29.17.193: icmp_seq=4 ttl=236 time=119 ms

— 64.29.17.193 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 118.408/126.717/139.573/8.731 ms
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig kaiser-leap-website.vercel.app

; <<>> DiG 9.18.30-0ubuntu0.22.04.2-Ubuntu <<>> kaiser-leap-website.vercel.app
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28307
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;kaiser-leap-website.vercel.app. IN A

;; AUTHORITY SECTION:
blacklist.umniah.local. 3600 IN SOA f5-a.umniah.com.blacklist.umniah.local. hostmaster.f5-a.umniah.com.blacklist.umniah.local. 2025032912 10800 3600 604800 86400

;; Query time: 10 msec
;; SERVER: 10.255.255.254#53(10.255.255.254) (UDP)
;; WHEN: Wed Apr 02 22:38:26 +03 2025
;; MSG SIZE rcvd: 144

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig kaiser-leap-website.vercel.app via 8.8.8.8

; <<>> DiG 9.18.30-0ubuntu0.22.04.2-Ubuntu <<>> kaiser-leap-website.vercel.app @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41712
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;kaiser-leap-website.vercel.app. IN A

;; ANSWER SECTION:
kaiser-leap-website.vercel.app. 300 IN A 216.198.79.1
kaiser-leap-website.vercel.app. 300 IN A 64.29.17.1

;; Query time: 89 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Wed Apr 02 22:38:26 +03 2025
;; MSG SIZE rcvd: 91

└───────────────────────────────────────

┌───────────────────────────────────────
├─────── dig kaiser-leap-website.vercel.app via trace

;; communications error to 10.255.255.254#53: timed out
;; communications error to 10.255.255.254#53: timed out
;; communications error to 10.255.255.254#53: timed out

; <<>> DiG 9.18.30-0ubuntu0.22.04.2-Ubuntu <<>> kaiser-leap-website.vercel.app +trace
;; global options: +cmd
;; no servers could be reached
└───────────────────────────────────────

┌───────────────────────────────────────
├─────── Output of kaiser-leap-website.vercel.app

  • Could not resolve host: kaiser-leap-website.vercel.app
  • Closing connection 0

└───────────────────────────────────────

┌───────────────────────────────────────
│ Time elapsed: 44 seconds
│
├─────── FINISHED
└───────────────────────────────────────

File can be found at /home/mustafa/vercel-debug.txt

15

Thanks!

Based on the debug logs you’ve shared, I can identify why kaiser-leap-website.vercel.app is inaccessible from your location. The issue is related to DNS resolution.

Key Findings

DNS Resolution Problem:

  1. Your local DNS server (10.255.255.254) returns NXDOMAIN (non-existent domain)
  2. The authority section shows blacklist.umniah.local, suggesting DNS filtering
  3. When using Google’s DNS (8.8.8.8), the domain resolves correctly to Vercel’s IPs

Network Connectivity:

All ping tests to Vercel’s infrastructure IPs are successful. This confirms your network can reach Vercel’s servers

ISP Filtering:

The logs show you’re using Batelco Jordan (AS9038) in Amman. The presence of blacklist.umniah.local in the DNS response suggests your ISP is blocking or filtering this domain

Solution

To access the website, you need to bypass your ISP’s DNS servers. Here are some options:

Change DNS Settings:

Configure your device to use Google DNS (8.8.8.8, 8.8.4.4) or Cloudflare DNS (1.1.1.1, 1.0.0.1). This should resolve the domain correctly as shown in your test with Google DNS

Use a VPN Service:

A VPN will route your traffic through different DNS server. This can bypass local DNS filtering

Contact Your ISP:

You can also request your ISP to remove it from their blacklist

The logs indicate this is likely an ISP-level restriction rather than an issue with the Vercel deployment itself .

2 Likes
16

Thanks a lot, It try these solutions and see what will happen. So the problem was from Umniah the ISP in my country, I don’t know why would they block theses sites!

1 Like
17

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.