Is Jira site creation broken?

[Amber _ Saddlemark]

Hello,

I just tried to create a new jira site: saddlemark.atlassian.net.

The creation page was stuck in an infinite loop (10+ minutes), so I refreshed the page, and tried to recreate it. 

Atlassian is saying the name is already taken, yet when I go to load the page, I encounter "Your Atlassian Cloud site is currently unavailable."

a3135d69a01b4795aa9c71ac6550cf30

I'm located in the US.

How can I get out of this loop? I'm sure this will require some sort of internal support, however, I'm unable to use the url to submit a support ticket because "it doesn't exist". 

[Hari Krishna]

Hi @Amber _ Saddlemark ,

This is not you, and Jira site creation itself isn’t fully broken — this is a known edge-case when site creation fails mid-process.

What happened is that Atlassian reserved the site name (saddlemark.atlassian.net) but the provisioning didn’t finish. That’s why:

Atlassian says the site name is already taken

The URL shows “Your Atlassian Cloud site is currently unavailable”

Support forms can’t find the site because it never fully completed creation

Unfortunately, there’s no self-service way to get out of this loop. The site is in a “ghost” state and must be fixed internally by Atlassian.

Since you can’t submit a ticket using the site URL, the correct workaround is:

Open a support request without selecting a site, or

Raise the ticket under Account / Billing / Site creation issues, and

Include the Request ID (a3135d69a01b4795aa9c71ac6550cf30) and the intended site name

An Atlassian support agent can then either complete the site creation or release the reserved name so you can retry.

This does happen occasionally during peak provisioning times, and Atlassian support is the only team that can resolve it.

[Amber _ Saddlemark]

Thank you for the context. Unfortunately, the support portal does not allow you to submit a request with a recognizable cloud url.

[Hari Krishna]

That’s expected in this situation. Since the site never fully completed creation, the support portal won’t recognize the cloud URL.

In this case, submit the request without selecting a site URL. Choose a generic category like Account / Billing / Site creation issue, and clearly mention in the description that the site creation failed mid-process and the URL is stuck in an unavailable state.

Be sure to include:

The intended site name: saddlemark.atlassian.net

The Request ID you’re seeing

A note that the site cannot be selected because it does not fully exist

Atlassian Support can still locate and fix the “ghost” site internally using the request ID, even without a valid cloud URL selected.