Stock Scalping Community

Home ISP dies during a winner that turns into a gift for the street. Rehearse once. Preferably when it isn't expensive.

I lost more sleep to "what if the cable dies" than to actual outages — until I timed a failover on a Sunday and found my 2FA path assumed home Wi-Fi email. That was an educational fifteen minutes.

### Drill script

1. After close or weekend.
2. Platform up with a **tiny** paper or inactive session.
3. Unplug modem / kill SSID.
4. Start the timer.
5. Fail over to phone hotspot, backup SIM router, or phone-only flatten.
6. Get to cancel + flatten capability.
7. Log time-to-safe.

### Pass criteria

Time-to-safe **under 3 minutes** for the flatten path. Credentials work offline (password manager on the phone). You know whether the broker even allows mobile trading for your account type.

### Prep list I keep honest
If the drill feels dramatic, good. Outages are drama. Better Saturday comedy than Tuesday tragedy.

What's your measured time-to-safe on the last drill?
Hotspot, dual-WAN router, or phone-only — what are you actually running?
2FA that survives an ISP death — how do you handle it?
VPS folks: can you RDP/console over phone network when home WAN is dead?

On ISP Outage Drill — 15 Minutes That Saves a Month, the desk standard stays practical. An ISP outage during RTH is not an anecdote. It is a forced flatten event that many desks discover for the first time while size is on. A fifteen-minute drill once a quarter saves a month of "I thought I had failover" stories.

Replying in-thread with operable constraints — not forum combat. If these rails disagree with your framing, treat it as a checklist offer.

Infrastructure is risk management. ISP, VPS, NTP, flatten hotkeys, and update quarantine only count when drilled and dated.

Rails that stay on the sheet
- Outage is forced flatten event.
- Unread backup plans fail under adrenaline.
- Quarterly 15-minute drill.

What the drill must prove
1. You can detect loss of primary connectivity fast — not after three missed cancels.
2. You know the path to flatten: backup phone app, backup connection, broker ticket, or VPS path — practiced, not theoretical.
3. Working orders are handled on purpose: cancel/flatten policy written before the outage.
4. You do not invent new entries on the backup path while adrenaline is high.
5. Time-to-flat is measured and logged. "I would have figured it out" is not a metric.

Worked example — ISP dies mid-position
Primary ISP drops 10:12 while long QQQ. No phone hotspot drill, no VPS flatten path practiced. Position unmanaged two minutes. Drill: 15-minute quarterly outage rehearsal with timed flatten via backup path; log isp_drill_dated.

I keep examples in cents and clock time so Sunday review can tag the behavior — not rewrite it as a mood.

Failure modes
- Ignoring the rails above on ISP Outage Drill — 15 Minutes That Saves a Month and substituting confidence.
- Adding size after adverse selection because the story still feels right.
- Paying open microstructure tax that midday memory never modeled.

When to skip
Skipping is a first-class decision — even when the chart still looks persuasive:
- Checklist incomplete at 09:20 ET — observe or one pre-written A+ only.
- Live spread outside max for that symbol and session bucket.
- Index violently disagrees with a single-name thesis and no reduced-size RS plan is on the sheet.
- Platform, hotkeys, locate, or flatten path unverified after reconnect/update.
- Daily loss, PDT slot, or prop buffer tripwire already touched.
- News/FOMC/CPI window where the size-cut card says stand down.

Closing
For ISP Outage Drill — 15 Minutes That Saves a Month, keep operable boredom: written rails, measured cents, index context when relevant, and a skip that needs no apology. Process quality beats ticket volume.