How to Tell If Your ISP Is Throttling or Blocking You

A slow connection does not automatically mean your internet service provider (ISP) is deliberately restricting traffic. Poor Wi-Fi, evening congestion, a faulty NBN connection, overloaded websites, and problems inside a streaming platform can produce similar symptoms. A few repeatable checks can help you determine if your ISP is throttling or blocking with a simple test, without installing specialist monitoring software.

The key is to compare like with like. Test the same device, connection, website, and time of day, then repeat the check through a different network. Blocking usually prevents a domain, IP address, or service from loading at all. Throttling tends to produce a pattern of reduced performance, often affecting particular activities or appearing at busy times.

Understand The Difference Between Blocking And Throttling

Blocking is an access restriction. Your browser may show a DNS error, connection timeout, reset connection, or an ISP warning page when you try to open a particular domain. In Australia, access to some websites can also be restricted through court orders, regulatory processes, or provider filtering policies. A failure to load does not prove that your ISP is responsible, since the website itself may be offline.

Throttling is a speed restriction applied to traffic or a service. Video may repeatedly drop to a lower quality, downloads from one platform may be slow while another runs normally, or online games may experience unusual latency. Some Australian broadband plans use shaped speeds after a monthly allowance, and mobile plans may reduce performance after a data threshold. Check your plan details before treating reduced speed as suspicious.

Traffic management can be selective or temporary. An ISP might prioritise network stability during peak periods, while a content provider may limit a particular account, region, or server. The purpose of testing is to identify a consistent pattern, rather than to label a single slow result as censorship.

Establish A Clean Baseline

Start with a wired connection if possible. Connect a laptop directly to the router using Ethernet, pause cloud backups, stop large downloads, and ask other household members to avoid streaming for a few minutes. If you must use Wi-Fi, stand near the router and use the 5 GHz network where available. Record the time, download speed, upload speed, and latency shown by a reputable speed test.

Run the same test three times, with a short gap between attempts. A single result from a busy server can be misleading, particularly in apartments in Sydney or Melbourne where nearby wireless networks compete for the same channels. Repeat the measurements in the morning, during the evening peak, and later at night. Australian NBN users should also note whether the issue affects all services or just one website.

Write down the plan’s advertised speed and any shaping policy. A 50 Mbps plan should not be judged against a 100 Mbps expectation, and an NBN Fixed Wireless or Satellite service can behave differently from fibre or fibre-to-the-node connections. The baseline gives you a reference for later comparisons.

Compare Services And Devices

Test several unrelated activities: a general speed test, a large file from a well-known host, a video on YouTube, a video on another streaming service, and an ordinary news website. If every service is slow, congestion, Wi-Fi interference, router problems, or a line fault is more likely than content-specific throttling. If one category performs badly while others remain normal, investigate that category more closely.

Use a second device on the same home network. A browser extension, antivirus filter, old laptop, or background update can create a false impression of ISP interference. If the same video loads poorly on a phone, tablet, and laptop, the result carries more weight. Try both standard and high-definition playback, and observe whether quality changes automatically after several minutes.

A useful local comparison is to test during the evening when households in Brisbane, Perth, Adelaide, and other cities place heavier demand on broadband networks. A speed reduction that appears across all websites at roughly the same time may reflect shared network congestion. A reduction limited to one application, repeated over several days, deserves further checking.

Check Whether A Website Is Blocked

Choose a harmless, publicly available website that fails to load and test a few unrelated sites immediately afterwards. Note the exact browser message. “Server IP address could not be found” points towards a DNS resolution problem, while “connection timed out” may indicate routing, server failure, or filtering farther along the path. An ISP-branded block page is stronger evidence of deliberate intervention, though it still does not identify the legal or technical basis.

Check the domain from a different connection, such as a phone using mobile data rather than home Wi-Fi. If the page works on mobile but fails repeatedly on your fixed-line connection, the problem may be local to the home ISP or router. Ask someone in another household using a different provider to test the same address, because a website can be unavailable to one region or provider while functioning elsewhere.

Avoid treating search results as proof that a site is online. Search indexes can be old, and the website may restrict Australian visitors. You can also review the Net Neutrality Monitor for country-specific censorship observations and indicative reports covering domains, addresses, DNS responses, and probes.

Examine DNS Responses Simply

DNS is the system that translates a domain name into an IP address. If an ISP’s DNS resolver returns an incorrect address, refuses to answer, or redirects a request, the website may appear blocked even though the destination server is operating normally. Changing DNS resolvers can reveal this kind of interference, but a different result does not automatically prove malicious censorship.

For a straightforward walkthrough, follow this DNS censorship test. Compare the normal ISP connection with a reputable independent DNS service, while keeping the device and website unchanged. Clear the browser cache between attempts and record whether the error changes from “address not found” to a successful page load.

DNS differences can arise for ordinary reasons, including stale records, parental controls, malware protection, or an incorrectly configured router. Some providers use filtering systems required by law or enabled as an optional safety feature. Treat the result as evidence of DNS-level filtering, then compare it with direct connection tests and reports from other networks.

Use A Second Network As A Control

The simplest control is mobile data. Turn off Wi-Fi on a phone, open the same address or service, and compare the result. This test is especially useful in Australia because a Telstra, Optus, or Vodafone mobile connection may use a different route and DNS resolver from a household NBN service. Keep in mind that mobile networks can have their own filtering, congestion, and content restrictions.

A virtual private network can provide another comparison because it changes the apparent destination and often uses a different DNS path. However, VPN performance varies by server location and encryption overhead. A website working through a VPN suggests that routing, DNS, or provider filtering may be involved; it does not establish that your ISP is throttling the original service. Do not rely on one VPN result as definitive evidence.

For suspected throttling, compare the same service with and without the alternate connection at similar times. If a video platform is slow only on the home ISP while other services are fast, repeat the test over several days. A genuine pattern should survive changes in device, browser, and local Wi-Fi conditions.

Interpret The Evidence Carefully

Keep a short log with the date, time, connection type, test server, result, error message, and affected domain. Screenshots can preserve block pages and speed readings. Include whether the problem occurred on Ethernet, Wi-Fi, mobile data, or another household connection. This record is more useful than a general statement that “the internet feels slow.”

The strongest indication of blocking is a repeatable failure on one ISP, a successful connection through an unrelated network, and matching DNS or block-page evidence. The strongest indication of throttling is a sustained, service-specific performance drop that repeats at similar times and remains after Wi-Fi, device, and local congestion issues have been excluded. Neither pattern is conclusive without provider-side information.

Observation	More likely explanation	Useful follow-up
Every website and speed test is slow	Wi-Fi, congestion, line fault, or plan limit	Test by Ethernet and check the plan
One domain fails with a DNS error	DNS filtering, stale record, or domain outage	Compare another DNS resolver and mobile data
An ISP warning page appears	Provider or mandated content block	Save the page and record the exact address
Streaming is slow while downloads are normal	Service-specific congestion or traffic management	Compare another streaming platform and time
Home broadband fails but mobile data works	ISP route, DNS, or fixed-network filtering	Repeat on another fixed provider
Performance falls after a data allowance	Plan shaping	Review the account’s fair-use conditions
Results vary only on Wi-Fi	Local wireless interference or router issue	Test near the router and by Ethernet

If you need to report a suspected issue, provide the evidence rather than assuming intent. The contact page can be used to share relevant observations for monitoring, while your ISP’s support team can check line statistics, account shaping, outages, and network faults. Public monitoring data is indicative research, so it should be compared with your own repeated measurements.

The main lesson is to separate access failure from slow performance, control the test conditions, and compare an ISP connection with a genuinely independent network. One odd speed result proves little; the same domain-specific or service-specific pattern across several days, devices, and connections is the evidence worth remembering.