504 Gateway Timeout

Hi there

I am aware of the interuptions this morning as mentioned on https://status.atlassian.com/

But we are still getting a 504 Gateway Timeout on API calls done from our Connect App to Jira via the REST API.

Please advise what the issue is and timeline on resolvement? Anyone else getting this?

Thank you


I was at online customer meeting today and on this meeting Jira Cloud was down and no any error massage. Just a blank page appeared.

1 Like

Thanks for the response. Yeah, it seems that is resolved, @matti.kiviharju (from the front end / UI side)

This issue is relating to REST API calls made to the Jira API via the Connect App.

Anyone got any feedback or idea on why this is an issue that is still persisting? This is affecting a production integration (work logs, custom timesheets, customfields , etc)

Please advise urgently?



Any updates on this?

Did anyone find a solution to this?

Hey community,

Today, there are no ecosystem incidents on https://status.atlassian.com/. And there are no on-going incidents from 2020. Across the various APIs and authorization schemes there are different operational components, which effectively means there are different “gateways” for different situations. For 504 errors, or any other errors, Atlassian will need more than just the error code to help, like is provided in the details of @Martyn’s cross post: 504 Gateway Timeout jira Rest API

I recommend new community members scan:

To encourage new threads with details of the error conditions, I’m locking this thread.