A home connection that drops two packets and costs a trade
Posted: Sat Oct 31, 2026 8:46 pm
The strategy was fine, the broker was fine, and the VPS was in the right data center. The loss happened because of a home router.
Remote desktop sessions to a VPS depend on the home connection for display and clicks. A little packet loss on the home end doesn't affect the VPS's connection to the broker, but it does delay the clicks. A close order typed during a fast move arrives two seconds later than intended.
Another scenario: the platform runs locally, and the home internet hiccups for three seconds. The terminal disconnects, reconnects, and quotes resume. In between, a stop-loss that lives on the server would have worked, but one managed by a local script didn't.
Wired Ethernet beats Wi-Fi for jitter, even when speed tests look the same. Speed is bandwidth, while scalping cares about consistency and delay variation. A 100 Mbps line with spikes is worse than a 20 Mbps line that stays steady.
A cheap mobile hotspot as a backup connection costs very little and has rescued more than one open position.
A few cheap diagnostics are worth running before blaming the broker. Open a command prompt and run a continuous ping to the broker's server with a one second interval for ten minutes, then scan for dropped replies. Do it again while someone else in the house is on a video call. Compare.
Another quick check is the router's own log, which often shows brief disconnections that never appear in the platform. A router that reconnects every few hours to refresh its connection will cause trouble at the worst possible time. Setting a scheduled reboot at a quiet hour, such as late Saturday, turns an unpredictable hiccup into a predictable one.
Which matters more in practice: a fast connection or a stable one?
Remote desktop sessions to a VPS depend on the home connection for display and clicks. A little packet loss on the home end doesn't affect the VPS's connection to the broker, but it does delay the clicks. A close order typed during a fast move arrives two seconds later than intended.
Another scenario: the platform runs locally, and the home internet hiccups for three seconds. The terminal disconnects, reconnects, and quotes resume. In between, a stop-loss that lives on the server would have worked, but one managed by a local script didn't.
Wired Ethernet beats Wi-Fi for jitter, even when speed tests look the same. Speed is bandwidth, while scalping cares about consistency and delay variation. A 100 Mbps line with spikes is worse than a 20 Mbps line that stays steady.
A cheap mobile hotspot as a backup connection costs very little and has rescued more than one open position.
A few cheap diagnostics are worth running before blaming the broker. Open a command prompt and run a continuous ping to the broker's server with a one second interval for ten minutes, then scan for dropped replies. Do it again while someone else in the house is on a video call. Compare.
Another quick check is the router's own log, which often shows brief disconnections that never appear in the platform. A router that reconnects every few hours to refresh its connection will cause trouble at the worst possible time. Setting a scheduled reboot at a quiet hour, such as late Saturday, turns an unpredictable hiccup into a predictable one.
Which matters more in practice: a fast connection or a stable one?