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.
I am writing to report a persistent, reproducible network issue affecting access to websites hosted on the Netlify platform (*.netlify.app and customer domains served by Netlify’s edge) from the Telecom Egypt network.
Observed behaviour
Requests to Netlify-hosted sites over HTTPS hang indefinitely and never complete. The connection does not return an error, a timeout page, or an HTTP status code — it simply never responds.
This is distinct from a normal site outage, which would return an error quickly. The absence of any response is consistent with traffic being dropped in transit rather than rejected by the destination.
Evidence that the issue is path-related, not destination-related
The same URL, from the same device, at the same time, loads normally when routed through a commercial VPN. Only the network path changes between the failing and succeeding cases — the destination server, DNS records, and client configuration are identical.
The same content is also served correctly from a different hosting provider, confirming that the origin content and its configuration are not at fault.
Scope
This is not isolated to my connection. Netlify’s official community forum has an active thread from multiple Egyptian customers reporting the same behaviour on TE:
Business impact
Our organisation operates an office in Cairo and relies on Netlify-hosted properties for both client-facing websites and internal tooling. Staff currently cannot access these resources without routing through a VPN, which is not an acceptable long-term workaround for business operations.
Request
Please escalate to the NOC or IP peering team and investigate:
Routing and peering paths from the TE network toward Netlify’s edge infrastructure
Whether any traffic filtering, DPI, or blackholing is being applied to these destinations
Whether the issue is limited to specific TE regions, POPs, or subscriber pools
I am happy to provide traceroute output, MTR reports, packet captures, or to run any diagnostics your engineering team requires. Please advise on a reference number for this case.