Error 226 on a DM usually means you hit X's daily cap on first messages, not that X caught a bot. On Premium that cap is 35 a day. On the 46 customer accounts we ran from July to October 2026, most days with a 226 came right after 33 to 37 sends. A 226 well under the cap is a real warning.
What error 226 says
Error 226 is X's spam filter refusing an action, and in full it reads: "This request looks like it might be automated. To protect our users from spam and other malicious activity, we can't complete this action right now". Some people also see "Please try again later". X says its filters are "tuned in real-time".
The worry behind the code is X's automation rule, which says "You may not send unsolicited Direct Messages in a bulk or automated manner". That rule covers every tool and every person sending cold DMs, ours included. Most of the time, though, a 226 is about how many you sent today.
Is it the cap or a real flag?
The code alone cannot tell you, so count your first messages to strangers since this time yesterday. In our 21 day study of 30 accounts, to 1 September 2026, all 23 Premium accounts that stopped at exactly 35 in a day got a 226 on the next try. Find your own case here:
| Your account and count | What it most likely is |
|---|---|
| Premium, about 35 first messages today. | The daily cap. It reopens in about a day. |
| Premium, well under 35. | Most likely a real flag. Pause new first messages. |
| Free, any count. | Most likely a flag. At 7, the 3 free accounts in our study got a plain notice instead. |
| Premium Plus or Business. | Unknown. None of ours sent more than 36 in a day. |
Replies in an open chat do not count, and the DM limit for each X plan lists all four caps.
Why it can come one send early
X's count runs a little longer than 24 hours, which is why a 226 sometimes arrives at 34. On 26 September 2026 we went through 180 refusals on 21 Premium accounts. In 147 of them, the account had sent 34 in the past day and X still said no. It was still counting a send made up to about 30 minutes before that day began.
So a count of 33 or 34 is still the cap. A 226 at 20 is not.
How long error 226 lasts
If it is the cap, a 226 lasts about a day. In our study the next send went through 24.7 to 27 hours after the first send of the batch, timed from that send rather than from midnight. The full counts are in the X DM Limit Study.
If it is a real flag, X gives no length, so send no new first messages that day. A 226 is also not a lock, which says "this account is temporarily locked" and asks for a phone or puzzle check.
What to do after a 226
Work through these in order, because the reply test decides which of the last two steps applies:
- Stop every tool and tab that sends from this account.
- Reply in one open chat. If the reply goes and a new chat fails, you are almost certainly at the cap.
- Count and note the time of your first message to a stranger since this time yesterday.
- At the cap, start again about 25 hours after that first message, under the same cap.
- Well under the cap, send no new first messages until tomorrow.
Xsender reads each account's cap from X and stops one send short of it, apart from one test send about once a week that checks whether the account's plan has gone up. After a 226 at the cap it waits about 24 and a half hours from the first send; below the cap it pauses an hour, then four, then the rest of the day.
FAQ
Will error 226 get my account banned?
Not on its own, in our data. From 2 July to 5 October 2026, none of the 46 X accounts Xsender ran was suspended. 9 had a temporary phone or puzzle check. That is a record, not a promise. More in can cold DMs get you banned on X.
Why do I get error 226 on a free account?
On a free account, error 226 is most likely a real flag and not the cap. All 3 free accounts in our study that reached 7 got a plain limit notice instead.
Is error 226 the same as "Rate limit exceeded"?
No. "Rate limit exceeded" is error 88, with the HTTP code 429, and it means too many requests in a short time. Other DM errors are listed in why a message is not sent on X.
Can I appeal error 226?
X's help pages describe no appeal for DMs, and its old error page sent developers to a support ticket. If the 226 came at the cap, there is nothing to appeal; the cap reopens on its own.
Try it on your own X accounts. See plans and the 7-day trial
Sources and method
Sources and dates
- Error 226, its wording, the "tuned in real-time" note, error 88 and the lock line: X's API error code page, last static copy 17 May 2022.
- "Please try again later": X's developer forum.
- Caps and what counts as a request: X's Chat help page, archived 4 October 2026.
- The DM rule: X's automation rules, updated April 2026.
- The 23 accounts at 35, the free notice and reset times: the X DM Limit Study, 30 accounts over 21 days, recorded 1 September 2026.
- The 180 refusals: our logs for 21 Premium accounts, checked 26 September 2026, recorded in our sending code.
- The 226 days, daily sends, checks and suspensions: our logs for 46 accounts, 2 July to 5 October 2026.