Understanding Selective Connectivity Failures
When you experience internet connectivity issues with only certain sites after switching Internet Service Providers (ISPs), the problem is rarely a total outage. Instead, it indicates that your device can reach some destinations but fails to establish stable connections with others. This behavior is common in Australia where multiple major ISPs exist, each with different peering agreements and routing infrastructures. The issue usually manifests as timeouts, slow loading pages, or complete refusal to connect for specific domains while general browsing remains functional.
This phenomenon often occurs because the new ISP’s default DNS servers may not resolve certain domain names correctly, or their routing tables have suboptimal paths to specific Content Delivery Networks (CDNs). For instance, if you are trying to access streaming services or large file downloads, the path through the new ISP might be congested or misconfigured compared to the previous provider. It is important to note that this is distinct from intermittent disconnections which affect all traffic equally.
Distinguishing Between DNS and Routing Issues
The first step in diagnosing selective connectivity problems is determining whether the failure lies in name resolution or actual data transport. If a website fails to load entirely with no error message other than "no connection," it is likely a DNS issue. However, if the site loads slowly or drops packets intermittently, it is more likely a routing or MTU (Maximum Transmission Unit) problem. Tracing the route reveals no apparent patterns suggests that the underlying network path is variable, which is typical when ISPs change their upstream partners.
Another critical factor is IPv6 compatibility. Some Australian ISPs have rolled out IPv6 support unevenly, leading to situations where websites preferring IPv6 addresses fail to connect if your router or modem does not handle dual-stack transitions properly. This can result in a hybrid state where HTTP requests time out waiting for an IPv6 response that never arrives.
Testing and Diagnosing the Root Cause
To accurately identify the source of the problem, you must perform systematic tests using command-line tools available on most operating systems. Start by pinging a known problematic site and comparing it to a reliable site like Google or Cloudflare. Use the ping command to check for packet loss and latency spikes. If you see 100% packet loss to one site but successful replies to another, the issue is likely isolated to that destination’s IP range or protocol preference.
ping -t problematic-site.com
ping 8.8.8.8Next, use the tracert (Windows) or traceroute (macOS/Linux) command to map the path your data takes to the problematic site. Compare this trace against a working site. Look for hops where the new ISP’s network ends or where significant latency increases occur. If the trace stops at a gateway belonging to the new ISP, it indicates a peering issue between them and the target server’s provider. You can also use nslookup or dig to compare DNS resolutions. Check if both sites resolve to IPv4 and IPv6 addresses, and verify that the IPs returned are valid and reachable.
If you suspect DNS issues, try flushing your local DNS cache and switching to a public DNS resolver such as Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1). This bypasses the ISP’s potentially sluggish or incorrect DNS servers. On Windows, run ipconfig /flushdns; on macOS, use dscacheutil -flushcache. Changing your network adapter settings to use these public resolvers can instantly restore access to sites blocked or misrouted by the ISP’s default DNS.
Adjusting MTU Settings for Stability
One of the most common causes of selective connectivity failure, especially with large media files or video streaming, is an incorrect Maximum Transmission Unit (MTU) size. Different ISPs have different overheads depending on their connection technology (FTTN, FTTC, NBN Fiber, etc.). If your MTU is set too high, packets get fragmented or dropped by intermediate routers, causing timeouts for specific types of traffic.
To test if MTU is the culprit, perform a ping test with the -f (do not fragment) flag and decrease the packet size until it succeeds. For example:
ping -f -l 1472 8.8.8.8If this works, gradually increase the size by 1 byte until you find the maximum size that doesn’t drop packets. Add 28 bytes (for IP and ICMP headers) to this number to determine your optimal MTU. Configure this value in your router’s WAN settings or your computer’s network adapter properties. This adjustment ensures that packets fit within the constraints of the new ISP’s infrastructure, preventing silent drops that affect specific large-content sites.
Checking for IPv6 Configuration Errors
In many cases, the root cause is improper IPv6 handling. Modern websites increasingly prefer IPv6 addresses. If your new ISP provides IPv6 connectivity but your equipment or configuration does not support it seamlessly, browsers may hang while attempting to connect via IPv6 before falling back to IPv4, resulting in perceived downtime.
You can temporarily disable IPv6 on your computer or router to force all traffic over IPv4. On Windows, go to Network Connections, select your adapter, click Properties, and uncheck "Internet Protocol Version 6 (TCP/IPv6)." On macOS, navigate to System Preferences > Network, select your interface, click Advanced, and go to the TCP/IP tab to set Configure IPv6 to "Off." If this resolves the issue, you know the problem lies in IPv6 negotiation. You should then update your router firmware or contact your ISP to ensure proper IPv6 prefix delegation and router advertisement settings are enabled.
Considering Alternative Network Paths
If standard troubleshooting steps fail, the issue may be inherent to the new ISP’s routing policies for specific content providers. In such cases, using a Virtual Private Network (VPN) can provide a workaround by tunneling your traffic through a different network path. However, this adds latency and reduces speed. A more sustainable solution might involve checking if your ISP offers alternative routing options or business-grade plans with better peering agreements. Additionally, monitoring forums for other users in your area experiencing similar issues can confirm if it is a widespread infrastructure problem rather than a local configuration error.
Frequently Asked Questions
Why do only some websites fail to load after switching ISPs?
This happens because different websites rely on different servers, CDNs, and routing paths. Your new ISP may have poor peering agreements with specific content providers or inefficient routes to certain geographic regions, causing timeouts only for those destinations.
How can I tell if my DNS is causing the problem?
If you can access a website by typing its IP address directly but not by its domain name, your DNS is failing. Use nslookup to check if the domain resolves correctly, and try switching to public DNS servers like 8.8.8.8 to see if connectivity improves.
What is MTU fragmentation and how does it affect me?
MTU fragmentation occurs when data packets are larger than what the network path can handle, causing them to be dropped. This leads to slow loading or failed connections for large files and videos, even though small text-based pages might work fine.
Should I disable IPv6 to fix connectivity issues?
Disabling IPv6 is a useful diagnostic step. If turning it off restores access to problematic sites, it confirms that your equipment or ISP has misconfigured IPv6 routing. You should then update your router firmware rather than leaving IPv6 disabled permanently.
Can a VPN solve selective connectivity problems?
A VPN can bypass ISP-specific routing issues by sending your traffic through a different network path. While effective for accessing blocked or poorly routed sites, it may introduce additional latency and reduce overall download speeds.