MobileRead is inaccessible over Starlink, but works immediately over mobile data

[elenderg]

MobileRead is inaccessible over Starlink, but works immediately over mobile data

I'm having a strange connectivity problem with MobileRead and I'm trying to determine whether the problem is on my side, Starlink's network, or the MobileRead/Hetzner side.

I'm in Brazil and access to MobileRead works normally when I use my mobile carrier's connection. However, when I use my Starlink connection, the site simply times out.

Here is what I've tested so far:

• DNS resolution works correctly:
  • www.mobileread.com → 162.55.243.172
    
• MobileRead does not appear to have an IPv6 address, so this does not seem to be an IPv6 connectivity issue.
  
• Ping: 100% packet loss when pinging 162.55.243.172.
  
• HTTPS connection:
  

  curl -4 -I -v https://www.mobileread.com/

  The connection gets as far as:
  
  

  Trying 162.55.243.172:443...

  and then eventually times out.
  
• I rebooted my Starlink connection and received a completely different public IPv4 address. The problem remained exactly the same, so it does not appear to be related to a single public IP address.
  
• My current Starlink public IPv4 belongs to AS14593 (Space Exploration Technologies Corp.).
  
• Traceroute: the route reaches the Hetzner network in Germany before eventually timing out:
  

  ...
  as24940.frankfurt.megaport.com [62.69.146.15]
  core22.fsn1.hetzner.com [213.239.224.13]
  ex9k2.dc18.fsn1.hetzner.com [213.133.117.177]
  ...

  After that, the remaining hops time out.
  
• Other Hetzner services work normally. For example:
  
  

  curl -4 -I -v https://www.hetzner.com/

  connects successfully from the same Starlink connection and returns HTTP 200.
  
• I also checked the IP with RIPE RDAP. 162.55.243.172 is part of the 162.55.0.0/16 network registered to Hetzner Online GmbH.

So the problem seems to be quite specific to reaching 162.55.243.172 from Starlink, rather than a general problem with either Starlink → Germany or Starlink → Hetzner connectivity.

Has anyone else experienced MobileRead being unreachable specifically from Starlink, particularly from Brazil or other countries?

I'm especially interested in knowing whether MobileRead has any firewall, anti-abuse, IP reputation, or ASN-based filtering that could affect Starlink (AS14593), or whether there could be a routing/peering problem between Starlink and this particular Hetzner IP.

Any suggestions for additional tests would also be appreciated.

[JSWolf]

What happens if you use a VPN? If you don't have a VPN, Firefox has a VPN you can use to try.