Summary: My custom domain www.ecomvenom.com (site: ecom-venom / ecom-venom.netlify.app) returns ERR_CONNECTION_TIMED_OUT from Egypt/EU, while the deploy is Published and the site is reachable from other regions.
Root cause I found: ecom-venom.netlify.app resolves - globally (confirmed via Google 8.8.8.8 and Cloudflare 1.1.1.1) - to 35.157.26.135 and 63.176.8.218 (AWS eu-central-1). Both REFUSE TCP/443 from Egypt/EU (connection times out). Your anycast load balancer apex-loadbalancer.netlify.com (75.2.60.5 / 99.83.231.61) IS reachable from here and serves the site correctly (HTTP 200, valid Let’s Encrypt cert for www.ecomvenom.com).
Netlify DNS does not help: I created a Netlify DNS zone for ecomvenom.com; it produced NETLIFY ALIAS records pointing to ecom-venom.netlify.app, which (querying dns1.p02.nsone.net directly) resolve to the same dead eu-central-1 IPs - for both apex and www. So the standard www to .netlify.app CNAME AND Netlify DNS both route EU/MEA visitors to unreachable IPs. (I deleted that test zone.)
Temporary mitigation: I pointed the www CNAME to apex-loadbalancer.netlify.com so the site is reachable again.
Request: Please investigate why ecom-venom.netlify.app / the site’s NETLIFY ALIAS returns unreachable eu-central-1 IPs (35.157.26.135 / 63.176.8.218) on port 443 for EU/MEA clients, and restore correct routing so the standard configuration works again.
Tested 2026-06-22 from Egypt (TEdata) plus public resolvers Google / Cloudflare / Quad9 / OpenDNS.