Live Domain Check

Is Atlassian Community Down? Check community.atlassian.com Status and Outages

Run a live reachability check for community.atlassian.com. Compare the regional responses with the problem you see in Atlassian Community.

Find Atlassian Community help and reporting links, specific checks, and step-by-step guidance below the live result.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked -

Verdict -

Response Time -

Final URL -

Regional checks 8 regions

Rate:

No ratings yet.

Is Atlassian Community working for you?

Share a quick update and see what other visitors are experiencing.

Loading community reports…

Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy

Understanding Atlassian Community connection and service problems

The Atlassian Community is a discussion service, not the incident authority for every Atlassian product.

The checker above requests community.atlassian.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Atlassian Community action that failed. A homepage response alone cannot verify an account, app workflow or transaction.

Looking for another service? Browse social app checks.

Atlassian Community status information and official help

Atlassian Community service status

Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.

Atlassian Community help and reporting

Select the actual Atlassian product/site; a Jira incident does not necessarily cover the admin or community site.

Open community.atlassian.com

Open the website in your browser and compare it with the result above.

Where to report problems with Atlassian Community

Open Atlassian Community help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.

Details to include in your report

Community URL, sign-in/posting error, browser and time; include the product site separately if the incident concerns a product.

Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Atlassian Community.

What to check when Atlassian Community is not working

These are troubleshooting comparisons, not claims that Atlassian Community is currently experiencing a particular incident.

Start with the action that failed

Check a public discussion and a signed-in action separately; record whether only posting or login fails.

Narrow down the affected service

For Jira, Confluence or Bitbucket failures, select that product's status/support page instead of relying on forum activity.

Read the actual checker response

A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.

How to check if Atlassian Community is down

Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
Run the community.atlassian.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
Check for a service notice. Open Atlassian Community status and check whether the named service and incident time fit your error.
Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.

If Atlassian Community Is Not Working Only For You, Start Here

Use these local troubleshooting steps after the down-check workflow when Atlassian Community seems broken only for you. This section focuses on app, browser, account, and network fixes.

1. Compare browser sessions

Open community.atlassian.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.

2. Preserve a working account session

Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Atlassian Community issue.

3. Try another network

If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.

4. Capture support-ready evidence

Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Atlassian Community support.

Frequently asked questions about Atlassian Community problems

Is Atlassian Community down, or is the problem limited to one feature?

Run the community.atlassian.com check and compare its original timestamps and responses with your actual error. The Atlassian Community is a discussion service, not the incident authority for every Atlassian product.

Where can I report a problem with Atlassian Community?

Use the community buttons on this page to share whether the service works for you. For help from Atlassian Community, use the official help/reporting resource linked above. Select the actual Atlassian product/site; a Jira incident does not necessarily cover the admin or community site.

What should I check first when Atlassian Community is not working?

Check a public discussion and a signed-in action separately; record whether only posting or login fails. For Jira, Confluence or Bitbucket failures, select that product's status/support page instead of relying on forum activity.

What information helps Atlassian Community support investigate?