Advertisement IC Markets

Slippage on prop servers during NFP: sample logs

Discuss 1-minute to 15-minute price action setups, fading intraday momentum, key support/resistance zones, and proven short-term trading methodologies.
Post Reply
LondonScalper
Posts: 965
Joined: Sat Sep 05, 2026 7:54 am

Slippage on prop servers during NFP: sample logs

Post by LondonScalper »

NFP on a prop server taught me that "same strategy, different venue" is a fantasy without logs.

I kept a small sheet of fills around the release: intended price, fill, spread at click, and whether the firm platform showed a delay or soft reject. Personal raw account and prop path did not rhyme. The prop book was fine on quiet days and ugly in the minute that mattered.

What I record on NFP samples
  • Seconds relative to the print, not just "during news"
  • Order type (market vs stop) and size relative to my normal scalp
  • Whether I was flat by rule or still "just looking"
After a few prints I stopped treating prop slippage as a moral failure and started treating it as a venue filter: either cut size to noise, or hard-flat into the window.

Anyone else logging prop vs personal fills on the same NFP — and did the gap change how you use funded accounts around Tier-1?

I also note whether the prop platform queued the order or simply filled far from intent. Those are different problems. Queues argue for standing aside earlier; chronic far fills argue for smaller size or retiring that pair on the firm path entirely.
Recommended broker for automated trading & scalping IC Markets
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

Re: Slippage on prop servers during NFP: sample logs

Post by Fairman »

LondonScalper wrote: Personal raw account and prop path did not rhyme.
Worth knowing why they don't rhyme: at most retail prop firms the evaluation, and often the funded stage too, is a simulated account. The orders aren't going to a market at all. The platform fills them from the firm's own price feed and execution model, sometimes with slippage or delay settings that are deliberately tougher around news. So what you're measuring at NFP is the firm's fill rules, not liquidity. That's actually useful, because it means the gap is likely to be fairly stable for that firm, and it can be treated as a fixed cost of the venue rather than bad luck. It also means comparing two firms on the same print is mostly comparing their settings. And it's a good reason to read whether the terms let the firm adjust or remove trades taken during news, since some do.
It’s Fairman :geek:
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Slippage on prop servers during NFP: sample logs

Post by Shadow Trader »

Fairman's point on sim fill rules is useful. What I still measure is the gap in pips by order type, because market and stop orders did not behave the same on my prop path around NFP.

I logged 12 prop fills and 12 personal fills across a few prints, intended mid versus realised, with seconds relative to the release. The attached illustration is that sample.
img_12590_r1.png
img_12590_r1.png (61.08 KiB) Viewed 389 times
Personal mean slippage sat near 0.5 pips. Prop mean was about 2.0, with two fills over 3 pips inside the first 20 seconds.

Stop orders on the prop book were the ugly ones, while markets were merely wide. That pushed me to cancel working stops five minutes before the print and to refuse market entries until 90 seconds after, at quarter size if I take anything at all.

I also tag soft rejects separately from far fills. A reject that forces a reclick is a different problem from a fill 3 pips off intent, and mixing them in one average hides which rule to write.

Does your prop log split market versus stop, or do you keep one slippage number for the whole window? I need the split, or the average lies.
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Slippage on prop servers during NFP: sample logs

Post by Shadow Trader »

Fairman, I tested the idea that the gap is a stable venue cost, since it would make sizing much simpler. Across four NFP prints on the same firm, the prop minus personal gap ran 1.2, 2.9, 1.6 and 2.3 pips, so it was a range rather than a fixed number.

It did line up with the size of the surprise. The 2.9 pip print was the biggest miss of the four, which fits a fill model that scales slip with the move rather than adding a flat haircut.

The other thing in my sample was direction. None of the 12 prop fills had positive slip, while 3 of the 12 personal fills did, and that asymmetry is a cost even when the average looks tolerable.

Your point about the terms matters more than my log on some firms. If trades opened inside a news window can be removed, the slippage number is irrelevant because the whole ticket may vanish from the payout.

So I now read the news clause first and only log fills on firms where the ticket would stand. LondonScalper, did your prop sample ever show a positive fill near the print, or was it one directional like mine?
Shadow Trader
Posts: 5594
Joined: Wed Sep 09, 2026 5:19 pm

Re: Slippage on prop servers during NFP: sample logs

Post by Shadow Trader »

The journal tab in MetaTrader, and the logs in other platforms, contain a trail of events: connections, disconnections, order requests, server responses, errors. Most traders never look at it until something goes wrong. It's a better detective tool than most realise.

Useful clues: timestamps for order sending and confirmation, showing real latency. Messages about connection losses, with exact times, which can be matched against price gaps. Rejection reasons, such as off quotes, invalid price or market closed. Server change events. Authorization notices and warnings about outdated builds.

A routine review, say weekly, spotting patterns like repeated reconnections at the same time each day, can reveal network issues. Clusters of rejections at certain hours may point to broker-side problems.

Saving the logs matters, because platforms rotate or delete old ones. Copying them regularly into a dated folder creates a long-term record that supports any later dispute.

Some traders write small scripts to parse the logs and plot latency or error counts over time, turning raw text into a health dashboard.

A beginner-friendly project: copy the log into a spreadsheet at the end of each week, filter for lines containing "failed", "error", "rejected" and "off quotes", and count them by day. After a month, the pattern of problems, and the days when they cluster, is usually obvious.

Many brokers will also ask for log excerpts when a trading problem is reported, so having a ready archive speeds up the process.

What has the journal tab revealed, and which message deserves the closest attention?
Post Reply