Shadowrocket URL Test answers “is this probe URL fast right now?” It does not promise the same path for a catalog or a call. Use the provider’s probe address, then verify with Safari.
Green numbers relax people at 21:00 while the video CDN sits elsewhere. You are maintaining a policy group, not tapping flags on a consumer VPN.
Put a real probe URL in
Empty or random http targets lie. generate_204-style URLs from your provider are the baseline. If rules REJECT that host, every node looks dead.
Scoreboard
| Probe | Page | Do |
|---|---|---|
| Good | Loads | Pin it |
| Good | Fails | Rules/DNS articles |
| Bad | Loads | Fix the probe URL |
| Bad | Fails | Change node or refresh the sub |
On the subway the radio jitters; URL Test will paint the whole list red. Pause auto-switch and pin what worked this morning. If the subscription will not fetch, testing is theatre—see update failures. Import: import guide. Download, FAQ, guides.
Field questions tied to this guide
- 40 ms and Safari still spins. Probe path ≠ site path. Change the test URL or browse for real.
- Every test times out. The probe host is blocked, REJECT-matched, or the node is actually dead. Distinguish with global browsing.
- Interval of 10 seconds? That burns battery and annoys providers. Commuting is fine at 10–15 minutes.
- Auto always picks a far country. It picks the fastest probe, not geography. Pin a group.
Change one control, then retest
While working through “Shadowrocket URL Test: a 40 ms probe is not your video CDN”, 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 Shadowrocket 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 rocket-url-test-latency 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 “Shadowrocket URL Test: a 40 ms probe is not your video CDN”: 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 Shadowrocket.
Extra pass for “Shadowrocket URL Test: a 40 ms probe is not your video CDN”: 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 Shadowrocket.
Extra pass for “Shadowrocket URL Test: a 40 ms probe is not your video CDN”: 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 Shadowrocket.
Extra pass for “Shadowrocket URL Test: a 40 ms probe is not your video CDN”: 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 Shadowrocket.
Extra pass for “Shadowrocket URL Test: a 40 ms probe is not your video CDN”: 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 Shadowrocket.