Site name: mahmoudshokry.netlify.app Custom domain:mahmoudshokry.com Error: ERR_CONNECTION_TIMED_OUT
My site has been completely unreachable from Egypt (Cairo) since June 23, 2026. Tested on Chrome, Brave, Safari, across home WiFi and multiple mobile data carriers. All fail with the same timeout.
Already ruled out:
Domain is active on Namecheap (valid until Apr 2027)
No Firewall Traffic Rules, no Rate Limiting, no WAF configured
Last deploy was Apr 20, no changes made recently
Key finding: Site loads instantly when connected to a VPN (Europe/US server). This confirms the site is up and DNS is correct — the issue is specifically with Netlify’s CDN routing to Egypt.
Please investigate CDN/edge node routing for Egypt (EG) / MENA region for this domain.
Here’s what we’ve confirmed so far. Your sites themselves are healthy, and DNS is resolving correctly from Egypt so this isn’t a problem with your projects or configuration. The Netlify dashboard and main site remain reachable from Egypt, so it isn’t a Netlify-wide outage.
That being said, since your DNS configuration is currently active for Netlify DNS, it appears that you have not properly configured DNS, as indicated by troubleshooting with the curl command.
dig +noall +answer mahmoudshokry.com NS +trace | tail -n 6
;; Received 547 bytes from 192.42.93.30#53(g.gtld-servers.net) in 132 ms
mahmoudshokry.com. 1800 IN NS dns1.registrar-servers.com.
mahmoudshokry.com. 1800 IN NS dns2.registrar-servers.com.
;; Received 102 bytes from 156.154.132.200#53(dns1.registrar-servers.com) in 121 ms
To properly configure Netlify’s DNS, switch your domain’s name servers to those provided by Netlify. Here’s how you can do that:
In the Netlify UI, go to your Netlify name servers.
Copy the four Netlify name servers provided.
Go to your domain registrar’s (where you purchased your domain) dashboard and update the name servers (NS records) to match the Netlify Name Servers from Netlify.
You can check this Support Guide to help you with the DNS Configuration.
Once you’ve completed the necessary steps above, everything should be set up! Keep in mind that DNS changes may take up to 24 to 48 hours (sometimes less) to propagate globally. You can track your progress using this tool and check this Support Guide for more information on why DNS/SSL changes can take this long.
but my issue is different from what you described.
I don’t have a custom domain — my sites are hosted on *.netlify.app subdomains. The problem is that all *.netlify.app subdomains appear to be blocked in Egypt by local ISPs (Telecom Egypt, Vodafone, Orange, WE).
The sites are working perfectly fine globally and via VPN, but completely unreachable from Egypt without VPN. This seems to be affecting all Netlify users in Egypt, not just me.
Could you please:
Confirm if you’re aware of this blocking issue in Egypt
Let us know if Netlify is taking any steps to resolve it (e.g. contacting Egyptian ISPs)
Hi @Mohamed_Sarhan the information provided in my previous response applies. The issue you’re facing isn’t a Netlify-wide outage as the Netlify sub-domain of your site is working as expected on my end and other regions.
You will need to contact your internet service provider to determine if they are experiencing issues connecting to Netlify sites.
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.
We remain happy to review any additional findings that can help narrow down the source of the connectivity issue.