---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/51202#article
headline: "51202: Twilsock : CPS, Too many requests"
url: https://www.twilio.com/docs/api/errors/51202
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 51202: Twilsock : CPS, Too many requests

Log Level: ERROR

## Description

This error occurs when your application sends too many requests over Twilsock in a short period. Twilio enforces connection establishment and upstream request limits for SDK traffic to protect service quality. In Conversations and Sync, those limits include up to 110 new or re-established connections per second per subaccount, up to 500 upstream requests per second per connection, and up to 20,000 upstream requests per second per subaccount.

### Possible causes

* Your client is sending reads, writes, updates, or other upstream requests faster than the allowed rate.
* Your application is repeatedly creating or re-establishing SDK connections, which can exceed connection establishment limits.
* Multiple clients in the same subaccount are generating enough combined traffic to exceed the shared subaccount request budget.
* Your application is polling or retrying too aggressively instead of relying on SDK events, callbacks, or synchronized state updates.

### Possible solutions

* Throttle, debounce, or batch client operations so you send fewer requests over each connection.
* Keep SDK connections open and reuse them where possible instead of repeatedly creating new clients or reconnecting. This follows directly from Twilio's documented connection establishment limits.
* Implement retries with exponential backoff after a throttled request. Requests rejected with a rate limit response are safe to retry. ([help.twilio.com](https://help.twilio.com/hc/en-us/articles/360044308153-Twilio-API-response-Error-429-Too-Many-Requests-))
* Reduce unnecessary fetching. Prefer SDK events, callbacks, subscriptions, and Sync fanout over polling when you need state changes or status updates.
* Review your expected traffic against the documented limits for your product. If your production load is expected and you still need more capacity after optimization, contact Support.

#### Additional resources

* [Conversations Limits](/docs/conversations/conversations-limits)
* [Sync Limits](/docs/sync/limits)
* [Twilio API response Error 429 "Too Many Requests"](https://help.twilio.com/hc/en-us/articles/360044308153-Twilio-API-response-Error-429-Too-Many-Requests-)