# RFC 130: Upcoming changes to invocation rate limits

**URL:** <https://community.developer.atlassian.com/t/rfc-130-upcoming-changes-to-invocation-rate-limits/100191>\
**Category:** Request for Comments (RFC)\
**Created:** [April 13, 2026, 11:35pm UTC](https://community.developer.atlassian.com/t/rfc-130-upcoming-changes-to-invocation-rate-limits/100191 "2026-04-13T23:35:49Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![nathanwaters](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/nathanwaters/32/38195_2.png) [@nathanwaters](https://community.developer.atlassian.com/u/nathanwaters)\
**Post date:** [April 17, 2026, 4:48am UTC](https://community.developer.atlassian.com/t/rfc-130-upcoming-changes-to-invocation-rate-limits/100191/19 "2026-04-17T04:48:06Z")

</div>

> [@HeyJoe](#):
>
> We’re not planning to create some new system that requires paperwork or new bureaucracy - quite the opposite!

Hopefully not. The new [API rate limit model did](https://ecosystem.atlassian.net/servicedesk/customer/portal/34/group/110/create/4626) AND opened a [new DoS attack surface](https://community.developer.atlassian.com/t/rate-limit-abuse-new-attack-vector/99654).

---

_[View the full topic](https://community.developer.atlassian.com/t/rfc-130-upcoming-changes-to-invocation-rate-limits/100191)._