Messaging API 429s at high concurrency US1

Just noticed that the Open Web Messaging API throws 429 Too Many Requests when JMeter hits 200 concurrent sessions on US1. Using SDK 2.3.0 to send messages via /api/v2/conversations/messaging/send. The rate limit resets faster than expected. Is this a known bottleneck for digital channels? Need to validate capacity for our load test plan.