Unable to contact Atlassian Support when Jira Cloud was unavailable

[Jills Francis]

We recently experienced a major Jira Cloud outage where our Jira site was completely unavailable for more than 30 minutes, affecting our team and preventing us from carrying out our normal work.

The bigger concern is that we were unable to properly report the outage to Atlassian while it was happening.

When we attempted to contact Atlassian Support, the support form asked for our Jira Cloud URL. Even though our URL is a valid *.atlassian.net Cloud URL, the form returned:

Sorry, we can't find this Cloud URL.
See instructions below on how to find your URL.

As a result, we were effectively stuck with the Community as the only available route while our production Jira environment was down.

We understand that support requests may require the appropriate admin permissions, but during a major production outage, there should be a reliable way for affected customers to report the incident. If the Jira site itself is unavailable and the support form also cannot recognize the site URL, the current process leaves customers without a practical way to escalate the issue.

Could Atlassian please clarify:

1. What is the recommended emergency escalation path for a Jira Cloud customer when the site is completely unavailable?
2. Why does the Support portal reject a valid Cloud URL during these situations?
3. Is there a way for non-admin users to report a critical production outage when the designated admin is unavailable?
4. Can Atlassian provide a more resilient support mechanism for major Cloud outages?

This is particularly important because the issue lasted approximately 30 minutes and we were unable to report it through the normal support channel while the outage was actively occurring.

Any clarification from an Atlassian Team member would be appreciated.

[Staffan Redelius]

Hi @Jills Francis 

Valid points, I hope Atlassian looks into this and updates their routines

Best regards,
/Staffan

[Arkadiusz Wroblewski]

Hello @Jills Francis 

Your main concerns are valid.

Regarding the rejection: are you an admin? From my experience, the Support portal can reject an otherwise valid request if your account does not have the required entitlement to open Support tickets.

Regarding point 4: that question really needs to go directly to Atlassian. We are just users here, so anything beyond that would be speculation.

Best,

Arek 🤠

[Jills Francis]

Hi @Arkadiusz Wroblewski,

Thanks for the response. I am not an Atlassian organization/site admin, so I understand that I may not have the required permissions to raise a support ticket. But I don’t think that explains why the Contact Support portal rejects our valid Cloud URL and says, “Sorry, we can't find this Cloud URL”.

Also, I think there is still a usability and escalation issue here. I would expect a regular user to have some way of reporting an issue, even if they cannot raise a P1 or create a full support ticket.


For example, when we access the Contact Support portal (https://support.atlassian.com/contact) while logged in, I would expect one of two things:

1. If our account does not have the required permissions or entitlement to raise a support ticket, the portal should clearly tell us that before allowing us to go through the form.
2. Alternatively, it should allow users to submit a basic incident report or escalation that can then be picked up by the appropriate admin or Atlassian Support team.
   
   

What happened in our case was confusing because we could go through the support form normally, but when we entered our valid Jira Cloud URL, it returned:



The URL was valid. Our Jira site was simply unavailable at the time. This makes it difficult to understand whether the problem is our permissions, the site being unavailable, or an issue with the Support portal itself.

Today's incident is a good example of why this matters. The outage affected Jira Cloud, Jira Service Management and Confluence for more than 30 minutes. During a major incident like that, being able to report the problem through as many appropriate channels as possible is important. The more reports Atlassian receives, the easier it should be to establish the scope and impact of an incident.

I also agree with your point about point 4. Ultimately, that is something Atlassian needs to answer. I raised it here because I think it is worth bringing visibility to the issue and hopefully having someone from the Atlassian Team look into it. I don't think the Community consists only of end users, and hopefully someone from Atlassian monitoring the discussions can provide some clarification.

More generally, I think there is value in having a support/escalation channel that remains available independently of the affected platform. Some cloud providers use separate customer support systems for this reason, so that customers can still report an outage even when the primary service is unavailable.

If you agree that this is a reasonable concern, an upvote/like would certainly help give it more visibility. Hopefully someone from Atlassian can clarify whether there is already an intended process for this scenario or whether the Contact Support portal behaviour we experienced is something they need to address.

Thanks & Regards
Jills