# Notify Limits

> \[!CAUTION]
>
> Twilio deprecated Notify in October 2022 and no longer supports it. Learn more about [transitioning off Notify](https://support.twilio.com/hc/en-us/articles/11746930233115-Transitioning-off-Notify).
>
> If you're starting a new project, use [Programmable Messaging](/docs/messaging) for SMS notifications. For push notifications, integrate directly with platform-specific services such as APNs for iOS or FCM for Android. If you've already built on Notify, visit the [transition guide](https://support.twilio.com/hc/en-us/articles/11746930233115-Transitioning-off-Notify) to learn about your options.

Notify limits depend on each particular use case. In both **Passthrough** and **Notify modes,** customers have a default limit of **100 notifications** per second per service instance. These limits aim to protect the system by reducing the likelihood of misuse by accidental code or bad actors.

This limit can be raised up to **1,000 notifications/sec** per [service instance](/docs/notify/api/service-resource), which is **3.6M notifications per hour**. Please contact Twilio Support to raise this limit.

## Passthrough mode

You can send bulk notifications using different[binding types](/docs/notify/api/binding-resource) via the [Passthrough mode](https://www.twilio.com/blog/bulk-sms-with-one-api-request.html) by providing addresses directly in your request. Please be aware that Passthrough mode is limited by the **Push provider** (iOS and Android) capacity.

Your request can include up to **10,000 addresses**, provided the total size does not exceed 1 MB. You have the option to send multiple requests.

## Notify mode

Notify provides complex logic based on **tags** and **identities**, therefore its throughput depends on the way a customer uses these features. Your request can include up to 1,000 notifications per second.

There is no binding count limit for a notification service.