Hello Mariam, I haven’t found a solution yet, I’m waiting for a response from the support team to provide us with more information about the current problem and how to solve it.
Same issue here in Egypt. Multiple Netlify-hosted sites are inaccessible locally but work instantly through VPN. Looks like this may be affecting more than one user — hope the team can check for a routing/CDN issue.
i have the same issue too, I noticed that only the newly hosted websites are not working without VPN, but all the old -like couple of months old- websites are working fine,
If you can move your domains DNS records to cloud flare, you can proxy (orange cloud) your site until TE decides to fix this. Keep in mind that you might have ssl issues.
I sent them an email and they responded with that:
Good news on the important part: this isn’t a problem with your sites, your DNS, or your certificate. Your sites are healthy and DNS is resolving correctly from Egypt — which is consistent with the fact that access works over a VPN. The failure is in the network path between Egyptian consumer ISPs and the Netlify edge IPs your traffic is being geo-routed to. Requests are being dropped in transit before they reach us.
Our network trace shows the connections being dropped inside Telecom Egypt’s network (AS8452 / TE Data) — the backbone that most Egyptian ISPs (including TE Data, We Telecom, Orange Telecom, Link.NET, Vodafone Egypt, and Etisalat Misr) route their international traffic through. Because the break is on the ISP / transit side rather than ours, it would genuinely help to report this to your own ISP in parallel and ask them to escalate. You can share these specifics with them:
- HTTPS (port 443) connections to Netlify’s AWS edge IPs are timing out from their network
Our trace shows the traffic failing in transit through Telecom Egypt (AS8452) — please investigate the route and escalate to the upstream / Telecom Egypt if applicable
It works fine over a VPN, confirming the destination is reachable and the problem is in the local routing path
Could you reply with the name of your internet provider? That helps us correlate reports and push from our side.
We’ve escalated this to our infrastructure / network team to investigate routing options (re-routing Egyptian traffic off the affected edge path is one of the options being looked at). In the meantime, a VPN remains a reliable workaround, and we’ll follow up on this ticket as we learn more.
please all send them to notify them that this failure is a big problem help@support.netlify.com
It’s clear that it’s just TE being TE and randomly breaking domains without thinking about impact. Honestly it’s extremely frustrating the number of sites and services that just don’t work because of censorship or DPI.
