Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Upcoming rate limiting changes to Statuspage REST API

Statuspage will soon be making changes to how rate limiting is implemented in our authenticated REST API. If you have an existing integration with our REST API, you may need to make updates to accommodate these changes, so please read on to understand the details.

What is changing

  1. Rate limit policy changes. Effective Sep 15, 2020, unpaginated GET requests to the page-access-users and components endpoints will be limited to 1 request per minute. Paginated requests to those endpoints will continue to be rate limited at the existing rate of 60 requests per minute.
  2. Rate limit response code change from 420 to 429. Effective Feb 15, 2021 when you exceed the Statuspage API rate limit, we’ll respond with HTTP status code 429 (Too Many Requests) instead of the current behavior of responding with a 420.
  3. Inclusion of Retry-After header in rate limit responses. Effective immediately, we’ll include a Retry-After HTTP header in 420 / 429 responses, e.g. Retry-After: 60 for unpaginated requests that exceed the rate limit.

What you need to do

You may need to update your integration to prepare for these changes:

  • We strongly recommend that you implement pagination for GET requests where possible, since the unpaginated rate limit will be much more restrictive.
  • If you've implemented rate-limiting handling that expects a 420 status code, you should update it to also accommodate a 429 response.
  • You should look for the Retry-After header and limit your requests accordingly.

If you have questions about these changes, please feel free to post a comment here, or contact our support team.


Eric Taba Atlassian Team Aug 05, 2021

Unfortunately, due to existing customer integrations built around the 420 response, we did not end up swapping the 420 response for 429 in the existing API v1 service. So in the case of rate-limiting, the response may be an HTTP 420 or a HTTP 429 depending on the service.

Like Chris DeGidio likes this


Is there a rate limit on the non authenticated apis? Or is there some latency charts available for the open APIs?


Log in or Sign up to comment

Atlassian Community Events