Reminder: Please ensure your Apps comply with Jira Cloud Burst API rate limit

[#1]

As part of Atlassian’s ongoing commitment to reliability, performance, and fair usage, burst API rate limits are now introduced for all Jira Cloud customers. These limits, first announced in the change-log in August 2025, are designed to prevent service disruptions caused by sudden spikes and sustained high load to API traffic. By proactively managing high-volume requests, we ensure a stable and seamless experience for all customers.

What does this mean for you?

• If your app or integration exceeds the allowed number of API requests in a short period, you will receive a “429: Too Many Requests” error.

• These limits are enforced on a per-tenant per-API basis.

• Rate limits are enforced using industry-standard token bucket algorithms, allowing for short bursts of activity but maintaining a sustainable average rate over time.

What action is required?

• Review and update any custom integrations or apps to ensure they compely with the new burst rate limits.

• For existing apps or integrations, implement exponential backoff and retry logic to handle rate limiting gracefully.

Why is this important?

• These limits are based on industry best practices and are essential for maintaining a reliable and high-performing Jira Cloud platform for all users and partners.

• Adhering to these limits helps prevent service disruptions and ensures a positive experience for all Atlassian customers.

Need help or more information?

• For detailed guidance and updates, please review our Atlassian developer changelog and Rate limiting.

We appreciate your cooperation in adopting these changes. Respecting burst limits is essential to maintaining a reliable and high-performing Jira Cloud for all customers.