QuickQ smart routing is the daily default so domestic apps stay put. When the site you care about fails, global for three minutes. Global works → splitter miss. Global fails → node, TAP, or network.
One-tap clients hide the splitter. Confirm a real tunnel via first connect.
The three minutes
- Note the current mode.
- Global, open the failing site.
- Works: back to smart, pull that app/domain into the tunnel.
- Fails: Auto node, or drops.
Work mail that allow-lists office IPs wants Direct. Games want the opposite: games. Kill Switch will blip during mode changes. 2.5.0: download. FAQ, guides.
Field questions tied to this guide
- Daily default? Smart for commute browsing. Global to debug meetings, catalogs, games. Switch back after.
- Bank got pulled into the tunnel? Direct that app. Do not shut the whole VPN for one tenant.
- Is global 'less safe'? Your exit changes; risk engines may step up MFA. Know what you are submitting.
- Same as per-app? Smart is often geo/domain; per-app is process. Phones may have both—do not exclude Chrome twice.
Change one control, then retest
While working through “QuickQ smart routing vs global: a three-minute fork”, write the download-page version, mode, protocol, and node name on the first line of a note. After each toggle, run one check only: 1.1.1.1/help or the exact page that failed. Changing Kill Switch, split rules, and nodes together makes the next failure un-debuggable. Get QuickQ packages only from the download page; permissions and device limits live in the FAQ and guides.
On office or hotel networks, finish captive portals and clear leftover PAC entries before you decide this article’s failure mode applies. A cellular A/B exposes router DNS and parental filters quickly. Avoid hammering login on a second device during the test so session kickouts are not mistaken for radio drops.
Pin the combination that works—SSID, node, protocol—and reuse it on that network instead of starting from Auto every time. Keeping slug qqv-smart-vs-global as your note title makes the write-up searchable later.
When to stop and change layers
After five identical failures, stop. Recheck the documented build, confirm a single tunnel client, ensure Kill Switch was not blocking a portal, and verify the browser is not Direct in a split list. Stopping is how you escape the wrong layer.
When you ask for help, include time, SSID, mode, protocol, node names, and steps already tried. After recovery, verify egress in a clean browser so cache does not fake success, then write the split list or favorites back into your notes before the next reinstall.
Extra pass for “QuickQ smart routing vs global: a three-minute fork”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.
Extra pass for “QuickQ smart routing vs global: a three-minute fork”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.
Extra pass for “QuickQ smart routing vs global: a three-minute fork”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.
Extra pass for “QuickQ smart routing vs global: a three-minute fork”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.
Extra pass for “QuickQ smart routing vs global: a three-minute fork”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.
Extra pass for “QuickQ smart routing vs global: a three-minute fork”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging QuickQ.