Quick answer
Twilio documents default channel rates as WhatsApp: 80/s; RCS: 100/s. Error 63018 documents channel-specific limits distinct from combined account throughput.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| default channel ratesError 63018 documents channel-specific limits distinct from combined account throughput. | WhatsApp: 80/s; RCS: 100/s | Default channel limits | TwilioAug 22, 2026 |
Why does this limit matter?
A campaign under the 2,000/s account ceiling can still overload its WhatsApp or RCS channel.
This value is scoped to Default channel limits; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Partition throughput metrics by channel, sender, account, and subaccount.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Approved or configured sender capacity can vary.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related