The symptom is confusing because it contradicts itself: the internet is obviously working, other pages load, messages send, yet one app spins and gives up.

When everything fails, the cause is clear. What's awkward is when almost everything succeeds.

And precisely because only one thing fails, speed is almost never the cause. Different apps take different routes, and one of those routes is broken.

The first check that saves everything

Before touching any setting: try the same app over mobile data, with Wi-Fi switched off.

  • Works on mobile, fails on Wi-Fi: the cause is your network. Read on.
  • Fails on both: the service is having trouble, or access has been shut off nationally so every provider blocks it. Neither can be fixed at home, and time spent on the router is wasted.

This one minute splits the problem in half, and half of it isn't yours.

Four suspects

If it really is your network, the cause is nearly always one of these four, and each fails distinctively.

1. DNS, the name can't be translated

Apps reach their servers by name, and that name must become a number first. If translation fails for one particular name, only that app goes down.

How it looks: instant failure, no waiting. The message usually mentions a server not being found.

The test: change the device's DNS to a public one and try again, see the guide to changing DNS. How it works is in the guide to DNS, and if DNS itself is struggling, the guide to DNS not responding goes deeper.

A note for users in Indonesia: this test can mislead. Since 2015, home and mobile providers here have been required to redirect ordinary DNS traffic (port 53) for blocking purposes. Typing 8.8.8.8 or 1.1.1.1 into your settings doesn't guarantee your query actually goes there. If nothing changes, try the secure DNS (DNS over HTTPS) option in your browser's privacy settings. If the app works with secure DNS, the provider's DNS is the cause. Some providers also block encrypted DNS, so "still fails" doesn't prove DNS is innocent.

2. Blocking

The service is deliberately closed off, by the provider, by a router setting, or by network-level filtering.

How it looks: consistent failure, every time, from every device on that network, but normal on other networks.

How blocking works and how to tell the types apart is in the guide to how site blocking works. If the block is coming from your own house, check the guide to parental controls on a router, these are often on without anyone realising, especially on ISP-supplied equipment.

In Indonesia, national blocking has three faces worth recognising:

  • Komdigi's TrustPositif list. Sites on this list are closed off by every provider. You can check yourself: open trustpositif.komdigi.go.id, type the domain, and search. The same site has a normalisation request route for site owners who believe they were blocked by mistake.
  • Cut-offs along the way. For HTTPS sites, the national filter doesn't show a warning page. It sends forged reset signals so the connection drops at once. In Chrome this usually shows up as an error like ERR_CONNECTION_RESET, instantly, and is often mistaken for a router fault. Plain HTTP sites redirect you to a block page.
  • Services not registered as PSE. In late July 2022, after the registration deadline for private-scope Electronic System Operators passed, several big services such as Steam, PayPal, and Epic Games suddenly became unreachable. Steam and Yahoo were unblocked from 2 August 2022. The signature of such cases: the service vanishes on every provider at once and the news is full of it. No router setting will help.

All three also explain why the "try mobile data" test sometimes fails on both routes. Mobile operators follow the same rules.

3. A closed port

Some apps don't use the same door as a browser. Online games, voice calls, security cameras, and work applications often use their own port numbers, and some networks close everything but the common ones.

How it looks: the app opens and menus load, but the main function fails. A game reaches the lobby but can't join; a calling app rings but no audio arrives.

This is most common on office, boarding-house, and public networks. At home, the cause may be CGNAT, see the guide to NAT and CGNAT, and if a port genuinely needs opening, the guide to port forwarding covers it.

4. MTU, packets too large to pass

The least known cause, with the most distinctive symptom.

Data travels in pieces, and there's a size limit for pieces crossing any given path. If the limit set on your equipment exceeds the real limit along the way, large pieces get stuck while small ones pass freely.

How it looks: pages open but images never appear. Apps log in but video won't play. Text arrives, files don't.

The test: lower the MTU in the router's WAN settings, from 1500 to 1492, then to 1400 if needed. This shows up most often on PPPoE connections.

The 1492 figure isn't arbitrary. PPPoE, the login method used by many home fibre connections including IndiHome, adds 8 bytes to every packet, leaving 1492 of Ethernet's 1500. Trouble usually starts when you put your own router behind the ONT and leave its MTU at 1500.

You can measure it instead of guessing. On Windows, open Command Prompt and type ping -f -l 1464 8.8.8.8. The -f option forbids splitting the packet, -l sets the payload size. 1464 plus 28 bytes of headers equals 1492. If replies come back normally, your path fits 1492. If you get a message saying the packet needs to be fragmented, lower the number a little at a time until replies appear, then add 28 to get a safe MTU.

Cases you're likely to meet

SituationMain suspectHow to confirm
One site instantly shows ERR_CONNECTION_RESET on home Wi-Fi and on mobile data tooNational blockingCheck the domain on TrustPositif
A mobile game reaches the lobby but can't find a match, only on boarding-house (kos) Wi-FiPort closed by the operatorTry mobile data, then ask the owner whether anything is restricted
After adding your own router behind the ONT, a banking app logs in but the transaction page hangsMTURun ping -f -l 1464, then set the router's MTU to 1492
A news site opens on the laptop but fails only on a child's phoneParental controls or a filtering app on that phoneCompare with another phone on the same Wi-Fi
A WhatsApp video call rings but the picture never connects on café Wi-FiUDP ports closedCompare with mobile data, then accept it: that's the venue's policy

The pattern worth remembering: if the failure follows you to another network, the cause isn't in your home. If it stays on one network, look in that network's settings.

The order to check

Ordered by how quickly each is answered, not by how common it is:

  1. Try mobile data. Splits the problem in two.
  2. Try another device on the same Wi-Fi. If only one device is affected, jump to the guide to single-device problems.
  3. Change DNS and retry, switching on secure DNS in the browser if needed. Five minutes, and it closes one possibility entirely.
  4. Note the shape of the failure. Instant failure points at DNS or blocking; a long wait then giving up points at ports; partly working with missing images points at MTU.
  5. Turn off VPN and ad filtering, if present. Both frequently block one service while leaving the rest alone, see the guide to VPNs.
  6. Lower the MTU, if the symptoms match.

Two cases with their own explanation

Everything fails after joining a new Wi-Fi. That isn't a per-app problem, see the guide to Wi-Fi connected but no internet.

An app fails on café or hotel Wi-Fi. Many public networks close most doors except those a browser uses. Voice calls and online games are the usual casualties, and that's deliberate on the operator's part, not a fault. What to watch for on such networks is in the guide to using public Wi-Fi safely.

What won't help

  • Restarting the router repeatedly. If once doesn't fix it, ten times won't either. A problem affecting a single app isn't one a restart clears.
  • Upgrading your internet plan. Speed is unrelated, everything else works at the same speed.
  • Reinstalling the app repeatedly, before testing on mobile data. If the service is down, reinstalling changes nothing.

When everything works except one thing, speed isn't the cause. Four routes can fail independently: name translation, blocking, a closed door, and packet size.

The shape of the failure points to which. Instant failure means DNS or blocking; a long wait then giving up means ports; partly loading with missing images and video is nearly always MTU.

And before any of it: try mobile data. Half of these cases end there, with the conclusion that nothing needs fixing at all.

Read also: Chrome Error Codes Explained and How to Fix Them and Email Arrives but Won't Send on Certain Wi-Fi Networks and Phone Notifications Arrive Late When Connected to Wi-Fi.

Frequently asked questions

I've switched DNS to 8.8.8.8, so why does a blocked site still not open?

In Indonesia, providers are required to redirect ordinary DNS requests on port 53, so the DNS set on your device may not be the one used. On top of that, blocking of HTTPS sites is now also done by cutting the connection along the way, not only through DNS. If the site really is on the TrustPositif list, changing DNS won't change the outcome.

How can I tell whether a site is blocked by Komdigi or just down?

Type its domain into trustpositif.komdigi.go.id. If it's listed, it's blocked nationally and will fail on every provider. If it isn't listed but still fails on every network, the service itself is most likely having trouble.