HTTP Error 500: Internal Server Error

[thibault hillmeyer]

Hello,

We cannot connect to all our Atlassian account, neither Jira nor Confluence, 

It appears that the error is coming from your servers, but when I am going on your status page I don't see anything talking about it... 

As it is the tool we are using for all our developers, it is completely bloking our work now...

Could you please inform me of when the issue will be solved.

Thanks you in advance for your reactivity, 

Thibault Hillmeyer

[Suren Raj · Accepted solution]

Hi There,

We're experiencing an incident that is affecting a group of our Cloud customers. This issue is high on our radar, and our engineering team is working actively to resolve the issue.

We sincerely apologize for the inconvenience caused due to this issue.

Please access any of our status pages below and click on *Subscribe* to receive updates about our progress on this incident:

• https://status.atlassian.com/incidents/2x4splh4hgvq
• https://jira.atlassian.com/browse/JRACLOUD-70473
• https://jira.atlassian.com/browse/CONFCLOUD-62960

Best Regards,
Suren Raj

[Lewis Davie]

Thanks for keeping us up to date. Best of luck!

[Manon Soubies-Camy]

Hello @thibault hillmeyer,

Same here, there is an outage on Jira and Confluence Cloud:

You can subscribe to updates on status.atlassian.com

- Manon

[Deleted user]

That subscribe-option is not working at moment ;-) 

[Lewis Davie]

It's working, but you have to click 'Subscribe' in the orange box (shown in the screenshot) rather than the big 'Subscribe to Updates' button.

[Deleted user]

Ah, thanks Lewis!

[Viveksamuelraj Santhanam]

Hi we are facing issue as 500 internal error. Please advise

[Lewis Davie]

It's back up!

[Janeks Kalniņš]

Someone updated Java on the server side?

[Craig Botha]

We were getting a 500:Internal Server Error but it's now a 504: Gateway Time-out. And the status page (https://status.atlassian.com/) isn't responding either!

[Дмитрий Тарасов]

also get 500 in cloud jira TT

[Lewis Davie]

Same here, although our error appears to be a 504: Gateway Time-out.