What did 29,000 cold DMs teach us about the X DM limit?

We run the software that sent these DMs, so this is our data, not a survey. It is here because no page that ranks for the X DM limit publishes a number anyone measured.

What we measured, and how

The sample: 30 X accounts, 21 days, about 29,000 DMs sent. Free and Premium accounts, run by paying customers, sending first messages to people who did not follow them. The logs record every send, every refusal with X's response, and every lock.

How we counted the reset window: for each account we logged three things. The first cold DM of a batch, the first refused send, and the next send X accepted. The gap between the first send and that next accepted send is the window.

How we counted refusals: one refusal is one send X answered with a limit notice or an error code. A retry that failed counts again. A send that stuck on Sending with no answer does not count.

When does the request cap reset?

24.7 to 27 hours after the first send of the batch, on every account we measured. X's help page says only "in a 24-hour period". Nothing we saw pointed at midnight, or at any fixed clock time.

So a batch that starts at 9 in the morning opens again between about 9:45 and noon the next day. Start at 6 in the evening and the next window is the following evening. The X DM limit guide has the caps by tier.

What a refused send looks like

The notice depends on the plan.

The 226 finding matters, because X publishes that code as its automation flag. A paid account that hits the cap by hand gets the same code. If you see it after exactly 35 first messages in a day, it is the cap, not a verdict on your account.

Do retries work?

Almost never. In one workspace, in one week, 662 sends were retried inside the window and 11 got through. That is under 2 percent. The other 651 came back as fresh refusals.

We could not find any sign that a retry harms the account. We also could not find any sign that it helps. It spends the day on refusals that could have gone to new people. Since 3 September 2026 our sending never retries a refused lead.

Locks, challenges and bans

Everything X did to the 30 accounts, counted.

That is not a promise about your account. It is what happened to 30 accounts that stayed inside their caps and never sent the same text twice. X's own rules ban bulk DMs that nobody asked for, and its Authenticity policy lists suspension as an option.

What we did not measure

• Premium Plus and Premium Business. No account in the sample hit 75 or 500, so those rows are X's numbers, not ours.
• An hourly limit. We spaced sends 3 to 5 minutes apart, so we never tested one. X publishes none.
• Account age. The 9 locks were all first-week accounts, but 30 accounts is too few to say when scrutiny relaxes.
• Reply rates. This page counts what X allowed, not who answered. The cold DM scripts guide covers replies, with a vendor dataset.

Do this now: if a paid account shows error 226 today, count its first messages since yesterday. At exactly 35, it is the cap. Stop, note the time of the first one, and plan the next batch for 25 hours after it.

FAQ

Is the X DM limit a rolling 24 hours or a calendar day?

Rolling, from what we measured. On every one of 30 accounts the next accepted first message came 24.7 to 27 hours after the first send of the batch. The time of day made no difference. X's help page says "in a 24-hour period" and names no reset time, so treat the clock as starting at your first send.

Does error 226 mean X flagged my account?

Not on its own. X publishes 226 as its automation warning, but every paid account in our sample that hit its 35 a day cap got the same code. Count your first messages to non-followers since yesterday. At exactly 35 it is the cap. Well under 35, stop every tool and use the account by hand for a while.

How often did X suspend an account for cold DMs?

Never, in this sample: 30 accounts, 21 days, 1,078 refused sends, 0 suspensions and 0 DM locks. The only action X took was 9 phone or puzzle checks on first-week accounts, all cleared within a day. The accounts stayed inside their caps and never repeated a text, which is the condition that record comes with.