Traffic continued after I stopped a project
OverRider ends its browser processes when you stop a project, so traffic stops within moments. It has no cloud component and no queue, so once the application is closed or the computer is off, no traffic is possible. Continuing traffic is coming from somewhere else — most often a scheduled project on another machine.
What stopping actually does
Pressing Stop cancels the project’s work and ends the browser processes belonging to it. It does not wait for long stay times to elapse. A visit already mid-navigation may take a few seconds to wind down; beyond that, nothing continues.
There is nothing left running elsewhere
OverRider is entirely local. It contacts overrider.io once, to verify your license, and never again. There is no cloud service, no task queue, no retry buffer and no server-side scheduler. Nothing about your campaigns is stored on our side, so there is nothing for us to stop remotely.
This means:
- Closing the application stops all traffic.
- Switching the computer off makes traffic impossible.
- Deleting a project removes it permanently.
- Proxies only relay traffic your computer sends — they never generate any themselves.
So where is it coming from?
Work through these in order.
1. A scheduled project on another machine
This is the most common answer by a wide margin.
Scheduled projects start on their own whenever OverRider is running. If it is installed on a second computer with a schedule set, it will begin running there at the scheduled time without anyone touching it.
Check every machine that has OverRider installed. On each one, confirm whether any project has scheduled days configured — stopping a project once does not clear its schedule.
2. Analytics processing delay
GA4 can take 24 to 48 hours to fully process data. Traffic you generated yesterday may still be appearing in reports today. Check Realtime instead — if that is empty with your machines off, nothing is currently arriving.
3. Genuine visitors and crawlers
Every public site receives bot traffic: search crawlers, SEO scanners, uptime monitors, scrapers. If your site was quiet before, this traffic may simply be newly visible against a low baseline.
Identify the source in GA4
With every machine off, open Reports → Acquisition → Traffic acquisition and compare the ongoing traffic against what you had configured:
| Check | What it tells you |
|---|---|
| Session source / medium | If it does not match your configured traffic sources, it is not OverRider |
| Country | Compare with the countries your proxies exit in |
| Device and browser | Compare with your device profile filters |
| Landing page | Traffic to pages that were never targets is from elsewhere |
| Realtime, right now | With all machines off, anything here is unrelated to OverRider |
Make sure a project cannot restart
To stop a project permanently rather than for one run:
- Press Stop.
- Clear its scheduled days, or delete the project entirely.
- Repeat on every machine with OverRider installed.
- Close the application.
Step 2 is the one that is usually missed.
Still unexplained?
Send support@overrider.io a screenshot of your Traffic acquisition report covering the period in question, and we will help you work out what the source is. Include whether any other machine has OverRider installed.
Last updated: