GitHub Pages site times out on Econet Zimbabwe mobile network but works through WARP

[emergingpointconstruction]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Pages

Body

Hello,

I am having a connectivity problem with my GitHub Pages website:

https://emergingpointconstruction.github.io/EmergingPoint-Construction/

The site consistently returns:

ERR_CONNECTION_TIMED_OUT

when I access it using Econet Zimbabwe mobile data on a Samsung Galaxy M13.

Important details:

• github.com opens normally on the same phone and mobile connection.
• emergingpointconstruction.github.io times out.
• The project Pages URL also times out.
• The website loads immediately when I enable Cloudflare WARP/VPN.
• With WARP/VPN disabled, it consistently times out.
• DNS resolution for the Pages domain works correctly.
• I reset the phone's mobile network settings and checked the APN.
• The GitHub Pages deployment has completed successfully.
• Econet Zimbabwe has checked their side and says there is no issue on their network.

Could someone please advise whether there is a GitHub Pages routing or connectivity issue affecting this Pages site or its edge path?

Thank you.

[dellagattamichela]

This almost certainly isn't something wrong with your site or deployment. It looks like a routing problem between Econet and the network GitHub Pages is served from.

github.com and GitHub Pages don't share infrastructure. github.com resolves to GitHub's own IPs (140.82.x.x), while *.github.io is served through Fastly's CDN on these addresses:

185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153

So github.com loading fine doesn't tell you much about Pages. And since DNS resolves correctly but the connection times out, the TCP connection to those 185.199.x.x addresses is being dropped somewhere along the way. WARP working fits that picture: it tunnels your traffic out through Cloudflare, which bypasses whatever path Econet is taking to Fastly.

A few things will help narrow it down and give Econet something concrete:

1. Try another github.io site on mobile data, any random project page. If those time out too, the problem affects all of GitHub Pages on Econet and isn't specific to your site. raw.githubusercontent.com is worth testing as well, since it sits on the same 185.199.108.0/22 range.

2. Get a traceroute. Termux (pkg install traceroute) or an app like PingTools can run it from the phone:

   traceroute 185.199.108.153
   

   Run it once on mobile data and once on Wi-Fi or WARP. Where the hops stop on Econet is the most useful thing you can send them.

3. Check IPv6. Pages also has AAAA records (2606:50c0:8000::153 etc.). If Econet hands out IPv6 and that path is broken, the browser can hang on it. Testing https://test-ipv6.com on mobile data will show whether IPv6 is working properly.

When you go back to Econet, "the site doesn't load" usually gets you a "no issue on our side" answer. Be specific instead: tell them connections to 185.199.108.0/22 (Fastly, AS54113) time out on their mobile network, and include the traceroute. That's much harder to wave off. Their mobile data may also route differently from their fixed-line network, so ask them to check the mobile path specifically.

It's also worth opening a ticket at https://support.github.com. Community discussions aren't really monitored by GitHub staff for this kind of thing, and they can raise it with Fastly if needed.

In the meantime, if you need the site reachable for visitors on Econet right now, there are two workarounds:

• Use a custom domain proxied through Cloudflare. Point it at your Pages site with the orange cloud enabled. Visitors then connect to Cloudflare, which you already know works from that network, and Cloudflare fetches from GitHub.
• Host a mirror on Cloudflare Pages or Netlify, both of which deploy straight from the same repo.

Hope that helps. Post the traceroute results here if you get stuck and I can take a look.

[emergingpointconstruction]

You are right and i have tested all those, it opens on other networks doesnt open on econet only