Forum Discussion

tstuart's avatar
tstuart
Neighbour
22 days ago

TELUS Business Internet — selective IPv4 destinations unreachable while others work

Seeing what looks like a selective upstream routing/blackhole issue on TELUS Business Internet in the Spruce Grove/Edmonton area tonight.

The circuit is up. Static IPv4 /30; TELUS gateway is reachable with essentially no loss. However, some Internet destinations are completely unreachable while others work normally.

Directly from OPNsense: 1.1.1.1, 8.8.8.8 and 9.9.9.9 all have 100% loss. Google IP 74.125.195.102 also has 100% loss and TCP/443 times out, while Google IP 142.250.69.174 has 0% loss and TCP/443 succeeds normally. Both Google IPs use the same WAN interface, default route and TELUS gateway.

I also captured traffic on the physical Proxmox NIC connected to the TELUS handoff. Traffic to 74.125.195.102 physically leaves the WAN NIC toward the TELUS next-hop MAC, but nothing returns. Traffic to 142.250.69.174 leaves through the same NIC/next-hop and immediately receives ICMP replies and TCP SYN/ACKs.

Local causes have been checked: OPNsense routing/default gateway is correct, CrowdSec is not blocking the affected IPs, Proxmox nftables/iptables/ebtables/tc are clear, and the physical NIC has zero RX/TX errors or discards. The issue also reproduces directly from OPNsense.

DNS was collateral damage. Unbound normally forwards over DoT to Cloudflare 1.1.1.2/1.0.0.2, which also became unreachable. Disabling those forwarders and using recursive DNS restored most service, but selective IPv4 reachability remains.

And just to top it off, the password I have recorded for my TELUS ONT no longer works. I tried resetting it and using the default credentials afterward, but still cannot access the ONT management interface.

Anyone else on TELUS, particularly Business Internet in Alberta, seeing selective destination/prefix reachability tonight?

1 Reply

  • TELUS_Support's avatar
    TELUS_Support
    Icon for Official Support Team rankOfficial Support Team

    Admittedly this is outside of our wheelhouse at the forum support level. Did the unreachable destination issues spring up recently or has it been on-going?