Sync Limits

up to 7,000
in each Twilio Subaccount

and

100,000 overall, shared among all your subaccounts.

Contact sales for more information or to request an override.

up to 110/s
in each Twilio Subccount

and

1,000/s overall, shared among all your subaccounts.

Rate of
Upstream Requests

up to 500/s
per connection

and

up to 20,000/s
per Subccount

• An object write is an explicit request in your code to change a value stored in Sync.
• The limit applies at the top level of each Document, Map, and List, e.g. updating any item in a Map still counts towards the containing Map's write rate.
• Fanout to subscribers is not rate-limited. If a write is accepted, all online subscribers will receive a state update and their number is inconsequential to the object's read or write usage.
• Objects larger than 1KiB are rate-limited more aggressively. The most strict rate limit, applicable for payloads 10KiB and larger, is 2 writes/s sustained.

• Object reads are effectively GET requests for Sync data. These usually occur when initializing your Sync app. Fanout of state updates to an online subscriber does not count as a read.
• The limit applies at the top level of each Document, Map, and List.
• When requesting List or Map items en masse, each requested page counts as one read.

• Fanout to subscribers is not rate-limited. If a message is accepted, delivery will be scheduled for all subscribers.
• Delivery is not guaranteed, and occurs independently of the message's acceptance from the sender. If a receiver fails to accept a message within a few seconds of acceptance, Sync will silently drop that message for that subscriber.
• Messages larger than 1KiB will be rate-limited more aggressively. The most strict rate limit, applicable for payloads larger than 3KiB, is 7 messages/s sustained.

up to 80/s per object permission

burst window: 10s

• These limits apply to all permissions on an individual Sync object (except Sync Streams) and are separate from the main read and write limits. The limits will be enforced only if ACLs are enabled for service instance associated with your application.
• Object permission reads are GET requests for Sync object identity where every individual identity can have various permissions for different Sync objects.
• Object permission writes are POST and DELETE requests for Sync object identity where every individual identity can have various permissions for different Sync objects.

up to 200/s per index per service instance

up to 20/s per index per client identity

burst window: 10s

• Establishing a new Live Query fetches a dataset with filters applied and is rate controlled.
• Live Query global rate control applies per individual index within a single Sync service instance.
• Live Query client rate control applies per client identity established by Sync SDK.

• You can create at most 20 objects per second, per Sync service. Important to mention, delete operations are counted into 20 objects per second limit.
• Deleting objects is free if this action is triggered by TTL, and not subject to any rate limit.

Sync Maps may contain Items with payloads up to 16 KiB of valid JSON serialized to a UTF-8 string.

NB! Due to some accidents of serialization and deserialization, which we do in the process of ensuring valid JSON payloads, the actual data written may be of subtly different size than it is upon transmission. In these cases, you may find payloads being rejected "too large" as they approach the 16KB limit. If your application stores large payloads, please do test at the extremes.

By default, this will return the first 50 items. Specify a PageSize value to fetch up to 100 items at once. There is no difference if the flag IncludeItems enabled or not. See paging for more information.

Default sorting order is ascending of ListItems per itemIndex and Map Items per item Key.

Any array within query expression must contain less than 30 elements.