---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/25021#article
headline: "25021: Rate limit exceeded"
url: https://www.twilio.com/docs/api/errors/25021
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 25021: Rate limit exceeded

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio rejected the request because your application exceeded the allowed request rate for the Organization API. Reduce the request volume before retrying.

### Possible causes

* Your application sent too many Organization API requests in a short period.
* Multiple services or workers are using the same credentials and collectively exceeded the rate limit.
* A retry loop, polling pattern, or burst of concurrent requests caused a sudden spike in traffic.
* Your application does not use backoff when it receives a rate limit response.

### Possible solutions

* Reduce how frequently your application calls the Organization API.
* Add exponential backoff and retry logic so your application waits before sending another request after a rate limit response.
* Smooth out traffic bursts by queueing or staggering requests instead of sending many requests at once.
* Review your application logs for unexpected loops, duplicate jobs, or parallel workers that may be generating excess traffic.
* If the request volume is expected for your use case, contact Support to discuss your current limits and options.

#### Additional resources

* [Twilio IAM documentation](/docs/iam)