Subject: Netlify sites (*.netlify.app) are blocked in Egypt Hi Netlify Support, All websites ending with *.netlify.app are completely blocked in Egypt and won't open unless we use a VPN. The deployment is successful, DNS is fine, and the sites open ins

Support
1

Subject: Netlify sites (*.netlify.app) are blocked in Egypt

Hi Netlify Support,

All websites ending with *.netlify.app are completely blocked in Egypt and won’t open unless we use a VPN.

The deployment is successful, DNS is fine, and the sites open instantly with a UK VPN. Also, the main netlify.com dashboard works normally without a VPN.

This is a general issue affecting all users in Egypt.

Thanks!

2

Same issue, we have business critical projects completely blocked right now

3

Same issue, we have multiple projects that timeout too

4

Can confirm this as well. Switching to a VPN or a public DNS like 1.1.1.1 fixes the issue on my side, but the sites still don’t work for other users.

5

same here , full platform down since 12 hours , every settings okay abd was stable.now total failure and working withvpn.please help asap.

6

Same issue here. All *.netlify.app sites are unreachable in Egypt

7

Same issue here. All .netlify.app sites are blocked in Egypt unless I use a vpn.

8

Hi, based on our investigation, we have not identified any issues within our infrastructure that would explain the behavior being reported.

When access problems are limited to users in a specific region or on specific networks, the cause is sometimes related to external factors such as ISP routing, regional network conditions, or local connectivity restrictions. In these situations, the affected users’ internet providers are often in the best position to determine where along the network path the connection is being interrupted.

For that reason, we recommend that any users experiencing the issue reach out to their ISP and report the problem. If the ISP is able to provide diagnostic information, such as traceroute results or details about the network path, we can use that information to assist with further investigation.

You can also implement the suggestion from @maherpoula13.

a public DNS like 1.1.1.1 fixes the issue on my side, but the sites still don’t work for other users.

We remain happy to review any additional findings that can help narrow down the source of the connectivity issue.

9

if u have domain use it and if its still not work move it to cloudflare dns manger and active the proxy there its gonna work well my projects are still work perfect so i just know the reason now

10

DNS didn’t work , VPN working good

11

hey @clarnx i just got off the final call with the major ISP in Egypt (WE Telecom). for the past 8 days i have been in contact with them regarding this issue and they are responsive.

they are acknowledging that the issue exists, but they claim that the issue is not from Egypt’s end but from netlify’s due to multiple different big ISPs (orange, vodafone, etisalat) also not able to reach your servers. WE Telecom reasoning was: “if you can access the website through mobile data from other providers, means it is a problem on our side. If you can’t means it is on the site’s end”, take this as you will.

I honestly can’t tell where the issue is originating from and i mainly care about it being solved. DNS change is not a valid solution as this is not being blocked on a DNS level.

Since i care about this issue being solved, the following are detailed tests from my end. Please let me know if you would like me to request something from the ISP’s end and see if they are going to be helpful.

DNS resolution through dig on default router settings with default ISP DNS server (always successful even after flushing DNS cache):

❯ dig spcr.netlify.com

; <<>> DiG 9.20.24 <<>> spcr.netlify.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55788
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;spcr.netlify.com.              IN      A

;; ANSWER SECTION:
spcr.netlify.com.       103     IN      A       63.176.8.218
spcr.netlify.com.       103     IN      A       35.157.26.135

;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Mon Jul 13 17:03:41 EEST 2026
;; MSG SIZE  rcvd: 77

traceroute:

❯ traceroute spcr.netlify.com
traceroute to spcr.netlify.com (35.157.26.135), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.754 ms  0.676 ms  0.803 ms
 2  156.194.0.1 (156.194.0.1)  6.483 ms  7.118 ms  6.383 ms
 3  10.45.3.144 (10.45.3.144)  7.003 ms  6.509 ms 10.45.1.5 (10.45.1.5)  6.884 ms
 4  10.36.4.22 (10.36.4.22)  8.613 ms 10.36.11.30 (10.36.11.30)  6.936 ms 10.36.4.22 (10.36.4.22)  7.230 ms
 5  10.45.28.77 (10.45.28.77)  8.468 ms  10.579 ms  8.257 ms
 6  TELECOM-EGY.edge4.Marseille1.Level3.net (212.133.4.230)  8.101 ms  7.306 ms  7.218 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

traceroute TCP port 443 (same as port 80):

❯ sudo traceroute -T -p 443 spcr.netlify.com
[sudo] password for hazem: 
traceroute to spcr.netlify.com (63.176.8.218), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  1.247 ms *  1.121 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * TELECOM-EGY.edge4.Marseille1.Level3.net (212.133.4.230)  6.652 ms  6.292 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

(the domain spcr.netlify.com comes from using dig on www.protondb.com which is how i first discovered this issue and now affecting astro.build)