Anyone else getting this: HTTP Status 429 - Too many requests

[Donal Devine]

HTTP Status 429 - Too many requests

type Status report

message Too many requests

description The user has sent too many requests in a given amount of time.

---

Apache Tomcat/8.0.38

One of my colleagues is not getting this error, the other is. 

I have logged a support ticket here: https://support.atlassian.com/contact/#/

[Donal Devine · Accepted solution]

I have logged a support ticket here - https://support.atlassian.com/
I suggest you do the same - it appears community is not being monitored at the moment.

[Yogesh Mude]

HI @Donal Devine

What was the solution for this ..as we are also facing the same issue?

Without the solution, you have been accepted this.

[Donal Devine]

The issue resolves itself over time. It was back working in about 4 hours for me. I guess there is some cache or something that expires. You can raise a support ticket with Atlassian, but it will probably have resolved itself by the time they get back to you. :-)

[Quality Assurance Traffic]

Same goes for me.

HTTP Status 429 - Too many requests

type Status report

message Too many requests

description The user has sent too many requests in a given amount of time.

---

Apache Tomcat/8.0.38

[Mark Ackroyd]

As of 10:31am.  UK Time.   We are still getting these.      Anyone looking it? 

[Roberto Russo]

I've opened a support request just now

[Terrance Teoh]

Usually after 5.00 PM Singapore Time.

[Roberto Russo]

Same problem now for my organizzation

[Rahul Ingle]

Hi All,

This  issue due to rate limiting your jira instance.

You need to modify jira api rate limt particualr account or gloabl setting / exemptions.

Sharing below kb for the same.

https://confluence.atlassian.com/adminjiraserver/improving-instance-stability-with-rate-limiting-983794911.html

Thanks

Rahul Ingle

[Rik de Valk]

This is due to rate limiting. See https://developer.atlassian.com/cloud/jira/platform/rate-limiting/

[Tyler Mitchell]

How are other people capturing the Rate limit related HTTP response headers (X-RateLimit-Reset, Retry-After, X-RateLimit-NearLimit, etc.) to engineer our API calls within Atlassian's rate limit boundaries.

We run into the 429 HTTP status codes, but how are others going after the pertinent headers in the response to tailor their API calls better?

[Bernhard]

We're also facing the same error sporadically for our organization.

Edit: no longer a problem for us

[Donal Devine]

It is back working for me now. I guess the bad cache or session or whatever expired since??

[Roberto Russo]

Problem solved now for me

[Dave.]

Still getting HTTP Status 429- to many requests. 

[Donal Devine]

Getting HTTP ERROR 504 now!

[Roberto Russo]

I've opened a support request

[Donal Devine]

ok, thanks. I have done the same

[Mark Ackroyd]

We are still getting these.   

[Quality Assurance Traffic]

Yes, you're right. It is appearing again now and I'm unable to connect my bug reporting account as well.

[Quality Assurance Traffic]

This page isn’t working

URL took too long to respond.

HTTP ERROR 504

[Quality Assurance Traffic]

I guess its resolved now.

[Quality Assurance Traffic]

But still I'm unable to connect my bug reporting account (marker.io)

[Donal Devine]

Not for me, getting 504 error now.

[Quality Assurance Traffic]

Also, sometime the view issue screen appears but not in its way.