Why Accounts Get Breached: 6 Real Cases From Dolvero's Enforcement Log

Accounts are almost never breached by a spectacular loss. They are breached by a small number crossing a fixed line, usually by a few dollars, and often while the account is still in profit overall. In Dolvero's enforcement log, 1,138 accounts have had at least one breach since launch, and 75.4% of them failed on the daily loss limit, not on the maximum drawdown. This article opens six real cases from that log, anonymised, with the exact figure that decided each one, the rule behind it and the habit that would have prevented it.

Accounts with a breach

1,138all accounts since launch

Daily loss limit

75.4%share of breached accounts

Busiest hour

13:00 UTCabout 21% of breach events

US data block

36%12:00 to 14:00 UTC combined

Most frequent instrument

XAUUSDappears most often in breach records

Written review

Every breachdisputed cases published

What actually breaks accounts

The table is the share of breached accounts by rule, from all Dolvero accounts since launch, on 10 September 2026. One account can appear under several rules, so the column does not add to 100%.

The top rule is a sizing rule, not a market-view rule: it punishes how much was on the table, not whether the direction was right. The rules traders worry about when they buy a challenge sit at the bottom, and two of the classics are absent entirely: Dolvero has no consistency rule and no inactivity rule on the 2-Step and 1-Step, and no time limit on any phase.

Six cases from the enforcement log

These are real enforcement records, paraphrased and anonymised, from the first ten days of September 2026. Every figure is the one the engine acted on.

Case 1: breached while $446 in profit

A $5,000 Instant Funding account with a 3% daily limit started the trading day at $5,607 in equity, so the allowance of $150 put the day's floor at $5,457. A single XAUUSD position ran against the trader and live equity touched $5,446: a loss of $161 against $150 allowed. The position was liquidated and the account failed while still $446 above its starting balance.

The number that decided it: $11. What would have prevented it: sizing the trade from the daily allowance rather than from the account. A $150 allowance with a stop worth $75 leaves room for two full losses in a day. The dashboard showed the $5,457 floor as a live dollar distance throughout; the trade simply had no stop inside it.

Case 2: nine small trades, $4 over

The same day, a second $5,000 account never had a large position open. Nine XAUUSD trades of 0.05 to 0.08 lots were opened and closed through the session, each a modest loss. Together they summed to minus $154 against the same $150 allowance.

The number that decided it: $4. What would have prevented it: a daily stop that counts the running total rather than the current ticket. No individual trade in this record looks reckless, and that is the point: the daily limit is a session budget, and the ninth trade went out with roughly $10 of it left. A hard line at 60% to 70% of the allowance ends the day before the last trade in a sequence like this is ever placed.

Case 3: three metals tickets, one idea, $9 over

A $25,000 2-Step account carried two XAUUSD sells, 0.95 and 0.74 lots, and one XAGUSD buy. Combined, the three lost $1,259 against the 5% daily limit of $1,250.

The number that decided it: $9. What would have prevented it: treating correlated metals positions as one exposure. At 100 ounces per lot, 1.69 lots of gold moves $169 for every dollar the metal moves, so the whole day's allowance was worth about a $7.40 move. Dolvero caps risk at 2% of balance per trade idea on CFD evaluations, $500 on this account, and the cap is defined per idea rather than per ticket, so splitting one view across three orders creates no extra room. Traders with a tested larger-size method take the No Risk Limit add-on and keep the daily and maximum limits as guardrails.

Case 4: a close at 12:30 UTC, exactly on the release

On 4 September a trader closed an XAUUSD position at 12:30 UTC, the exact minute of the Canadian Employment Change release. Dolvero's rule prohibits opening and closing within 30 minutes before and after every high-impact event in the Dolvero economic calendar, so the blackout ran from 12:00 to 13:00 UTC. The review showed the cause: the release time had been read in local calendar time and compared against a trade time recorded in UTC.

The number that decided it: 12:30 UTC, zero minutes of margin. What would have prevented it: one clock. The calendar on the Dolvero site runs in the same reference as the account record, and the MT5 server runs on Europe/Bucharest time, UTC+3 in September, so 12:30 UTC was 15:30 on the platform clock. Traders who hold through releases take the News Trading add-on, which removes the window on CFD accounts for 15% on the fee; crypto evaluations on Bybit have no news restriction at any time.

News windows have the widest spread of any rule in the industry: FTMO uses two minutes and only on funded accounts, FundedNext and FundingPips five, Funded Trading Plus states no restriction at all. Dolvero applies the widest window on evaluation and funded alike, because the seconds around a high-impact print are where spread and slippage turn a stop into a far larger loss than the trader chose, and it is the one restriction sold with an outright release rather than a profit deduction.

Case 5: Friday 15:14 to Monday 01:07

An XAUUSD position was opened on Friday at 15:14 and closed on Monday at 01:07. Dolvero requires all positions closed before the Friday market close, with nothing open at any point on Saturday or Sunday. The account was breached at the weekend boundary, and the result of the trade was irrelevant to the outcome.

The number that decided it: the Friday close, missed by one session. What would have prevented it: a Friday checklist at a fixed time, or the Weekend Holding add-on, which lifts the rule for 15% on the fee and is the standard choice for swing traders. The rule exists because a weekend gap is the one risk no stop can manage. It also covers CFD crypto pairs that quote at the weekend; crypto evaluations on Bybit run 24/7 and are unaffected.

Case 6: two tickets, 0.01 lots each, opposite directions

On 9 September an account held a 0.01-lot XAUUSD buy and a 0.01-lot XAUUSD sell open at the same time. That is hedging on the same instrument, prohibited at Dolvero on one account and across accounts, including correlated instruments such as long EURUSD against short USDCHF.

The number that decided it: none. Position size does not enter the test. What would have prevented it: closing instead of offsetting. Two opposite tickets net to zero exposure while both count as trades, which is the simplest way to manufacture trading days and to shift risk between accounts, so the rule looks at structure rather than amount. If the intention is to be flat, being flat is allowed and free.

The six cases at a glance

Three of the six were decided by $24 in total across three accounts. That is the practical case for reading the live distance to the limit instead of doing the arithmetic in your head at the end of a session.

The breach that needs no trade at all

On 2 September an Instant Funding account was closed for inactivity: nothing from 19 August at 08:45 to 2 September at 22:43, fourteen days against a seven-day rule. Inactivity is measured as 7 by 24 hours from the exact time of the last activity, and any activity resets it, including closing a position rather than opening one. It applies to Instant Funding only, which is funded from day one and carries live exposure. The 2-Step and 1-Step have no inactivity rule, so an evaluation can be paused for as long as a trader needs.

When breaches happen: the clock

Breach events are not spread evenly across the day. The concentration below is from the same enforcement data, in UTC.

One hour in twenty-four carries a fifth of all breaches, so the cheapest risk control available to most traders is a size rule between 12:00 and 14:00 UTC, not a new strategy. And the daily limit will not rescue the day by resetting: Dolvero's MT5 server runs on Europe/Bucharest time, UTC+3 in summer and UTC+2 in winter, so the trading day begins at 21:00 UTC in summer and 22:00 UTC in winter, which is 23:00 in Prague and 17:00 in New York all year round. A breach at 13:00 UTC lands sixteen hours into the session, with the full day already counted against the allowance.

How a breach is reviewed at Dolvero

A breach is a mechanical event, but the record of it is not left to the engine alone. Every case follows the same five steps, and the trader can challenge any of them.

1. The engine detects the crossing. Limits are evaluated on live equity, so the breach is timestamped at the moment equity crossed the line, not at the close of the trade. Where the rule requires it, the open position is liquidated.
2. The account state changes and the trader is notified. The dashboard states which rule was hit, at what time and at what equity. There is no waiting period in which the account sits in an undefined state.
3. A written review is produced. It sets out the rule as published, the threshold in dollars, the equity or timestamp that crossed it and the trades involved, written to be read by the trader rather than filed.
4. The trader can dispute it. A dispute is answered against the same record: the rule text in force on the day the account started, the account configuration and the data behind the equity curve.
5. Disputed cases are published. Dolvero publishes breach reviews so the reasoning is public and consistent across accounts, next to the public payout ledger and the rules changelog.

Rules are locked for existing accounts from the day they start and every change is published in the rules changelog. That is what makes step four meaningful: a dispute is settled against a version of the rules that cannot have moved after the fact.

Where Dolvero stands out

Live distance to limits

In dollarsevery account page, live equity

Breach reviews

Writtenevery case, disputed ones published

Rules after signup

Lockedchanges only via public changelog

Consistency rule

Noneon 2-Step and 1-Step

Inactivity rule

Noneon 2-Step and 1-Step, 7 days on Instant

Restrictions that lift

Add-onsnews, weekend, per-trade cap

Frequently asked questions

Why do prop firm accounts get breached most often?

The daily loss limit. In Dolvero's enforcement data, 75.4% of breached accounts hit it, against 10.0% for maximum drawdown and 5.7% for trailing drawdown. It is a sizing failure rather than a directional one: the limit is measured on equity from the start of the trading day, so open positions count in full while they run.

Can my account be breached while I am in profit?

Yes. The daily limit runs from the equity at the start of the trading day, and a trailing maximum drawdown follows your best result upward. In case one above, a $5,000 account was still $446 above its starting balance when it crossed the day's floor at $5,446. More on the three limits in daily, maximum and trailing drawdown explained.

What happens immediately after a breach, and can I dispute it?

The breach is timestamped at the moment equity crossed the line, the position is liquidated where the rule requires it, and the dashboard states which rule was hit and at what level. Every case gets a written review with the threshold, the crossing figure and the trades involved; the trader can dispute it against the rules as they stood on the day the account started, and disputed cases are published.

Does a close inside the news window count as a breach?

Yes. The rule covers opening and closing within 30 minutes before and after every high-impact event in the Dolvero economic calendar, on evaluation and funded accounts alike. The News Trading add-on removes the window on CFD accounts, and crypto evaluations on Bybit have no news restriction.

What time of day do most breaches happen?

13:00 UTC is the busiest single hour with about 21% of all breach events, and 12:00 to 14:00 UTC together carry about 36%: the US session open and the 12:30 and 13:30 UTC releases. The trading day itself begins at 21:00 UTC on the MT5 server, so a 13:00 UTC breach arrives late in the session with the day's losses already counted.