Site not accessible when connected via StarLink

[camoj]

Over the last couple of months, this site will not load when I'm connected to starlink - any thoughts?

[anonjohn]

Can you access other porn sites? - there might be a porn blocker.
Does this happen using other browsers?

[camoj]

Only this site, does not matter what device - no blockers and can access everything else I've tried - it's very strange.

[admin]

One possibility is that StarLink assigned you an IP address that has been blocked by us for previously abusing our network.

[camoj]

That's the only thing I can think of too. But it just times out, I don't get a blocked message or anything.

[admin]

If the site is being blocked at the firewall level, that is what I would expect to happen.

[anonjohn]

If your IP address is being blocked for previous misuse then you can find your public IP address from a site like whatismyipaddress.com
(NB might be best to PM the Admin with the result, rather than disclose your real location by posting the output here)

At a command line/terminal enter the text in bold below:

ping oneclickchicks.com
do you get a Reply or a timeout?


nslookup oneclickchicks.com
should return something like
Name: oneclickchicks.com
Address: 35.196.131.64

what happens if you enter this IP address into the address bar of your browser
35.196.131.64

this command will show the hops made to a website
tracert oneclickchicks.com
does it get to 35.196.131.64
NB: I would avoid pasting the full output of tracert here (send a PM to Admin instead), you may reveal too much about your location

[camoj]

## Root Cause Analysis: forum.oneclickchicks.com inaccessible on Starlink

### The Problem

The website `forum.oneclickchicks.com` (hosted at IP `35.196.131.64` on Google Cloud Platform) is being __blocked at the network/IP level by Starlink's infrastructure__. This is NOT a DNS issue.

### Evidence Found:

1. __DNS works fine__ — The domain resolves correctly to `35.196.131.64` across Starlink DNS, Google DNS (8.8.8.8), and Cloudflare DNS (1.1.1.1). Changing your DNS server will NOT fix this.

2. __Traceroute dies at Starlink's edge__ — Packets travel through your router (192.168.68.1) → Starlink CGNAT (100.64.0.1) → Starlink internal network → Starlink edge router (206.224.73.252) and then __completely drop__. The packets never leave Starlink's network.

3. __IP-level blocking, not domain-level__ — Connecting directly to the raw IP `35.196.131.64` (bypassing DNS entirely) also times out, confirming the block is at the IP/routing level.

4. __Multiple GCP IP ranges affected__ — Testing showed that several Google Cloud IP ranges (35.192.x.x, 35.196.x.x, 35.200.x.x, 35.208.x.x) are unreachable through Starlink, while other GCP ranges (35.190.x.x, 35.199.x.x, 34.120.x.x) work fine. This pattern suggests __Starlink has a routing/peering issue with certain Google Cloud data center regions__ (likely GCP `us-east1` where 35.196.x.x is hosted), or is intentionally null-routing traffic to these ranges.

### Most Likely Explanation:

This is either:

- __A BGP routing/peering issue__ between Starlink (AS14593) and Google Cloud's specific regional endpoints — certain GCP regions are unreachable because Starlink doesn't have proper routes to them, OR
- __Intentional IP range blocking__ by Starlink, possibly related to abuse complaints associated with these IP ranges.

### Workarounds:

1. __Use a VPN__ — This is the most reliable fix. Any VPN will tunnel your traffic outside Starlink's network before it reaches the GCP IP, bypassing the block entirely.
2. __Use a web proxy__ — Services like a SOCKS5 proxy or web-based proxy can route around the block.
3. __Contact Starlink support__ — Report that GCP IP range 35.196.0.0/16 is unreachable from their network and ask them to investigate their routing tables. Reference the traceroute dying at `206.224.73.252`.
4. __Tor Browser__ — Will route traffic through the Tor network, bypassing Starlink's routing entirely.