Live Domain Check

Is Confluence Down? Check confluence.atlassian.com Status and Outages

Run a live reachability check for confluence.atlassian.com. Compare the regional responses with the problem you see in Confluence.

Find Confluence 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 Confluence 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 Confluence connection and service problems

A public Confluence documentation hostname is not your organisation's Confluence site. Page access, editing and attachments need checks on that actual site.

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

Distinguish an Atlassian work-product issue from administration or support access with the relevant check: Atlassian Admin status check, Atlassian Support status check, Atlassian Status status check. Compare results separately; these links do not establish a shared outage.

Looking for another service? Browse work app checks.

Confluence status information and official help

Confluence service status

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

Confluence help and reporting

The public confluence.atlassian.com documentation host is not your organisation's Confluence instance.

Open confluence.atlassian.com

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

Where to report problems with Confluence

Open Confluence 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

Organisation site, page/space reference, editor or attachment action, time and error identifier.

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 Confluence.

What to check when Confluence is not working

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

Start with the action that failed

Open the affected organisation page and compare a second page you are permitted to read.

Narrow down the affected service

Preserve unsaved edits; compare whether an authorised colleague sees the same page or attachment failure.

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 Confluence is down

Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
Run the confluence.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 Confluence 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 Confluence Is Not Working Only For You, Start Here

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

1. Compare browser sessions

Open confluence.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 Confluence 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 Confluence support.

Frequently asked questions about Confluence problems

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

Run the confluence.atlassian.com check and compare its original timestamps and responses with your actual error. A public Confluence documentation hostname is not your organisation's Confluence site. Page access, editing and attachments need checks on that actual site.

Where can I report a problem with Confluence?

Use the community buttons on this page to share whether the service works for you. For help from Confluence, use the official help/reporting resource linked above. The public confluence.atlassian.com documentation host is not your organisation's Confluence instance.

What should I check first when Confluence is not working?

Open the affected organisation page and compare a second page you are permitted to read. Preserve unsaved edits; compare whether an authorised colleague sees the same page or attachment failure.

What information helps Confluence support investigate?