Confluence Status
Official status updates for Confluence cloud components.
Live Domain Check
Check if Confluence is down right now (confluence.atlassian.com). Run a live multi-region check to see whether Confluence is offline for everyone or just you.
Get official Confluence outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Confluence incidents can affect page rendering, editor saves, or search indexing independently. This checker helps you confirm platform health before large rollback or migration steps.
For Confluence, incident signals are often feature-specific: Page rendering stays reachable while search and indexing becomes unreliable. Users report editor autosave failures after token refresh. If this matches what you see on confluence.atlassian.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Use official sources first, then social/community signals to estimate incident scope and speed of recovery.
Official status updates for Confluence cloud components.
Official support for page editing, permissions, and macro errors.
Community signal for incident scope and workarounds.
Real-time posts and official updates related to Confluence incidents.
Official teams often post outage status updates and recovery progress through these social channels.
Recognizing these patterns helps you avoid false assumptions and escalate with better evidence.
Practical steps to follow when confluence.atlassian.com seems down. Use this checklist to confirm whether Confluence is down for everyone or only for you.
Run confluence.atlassian.com in WebsiteDown.org first, then open confluence.atlassian.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Confluence service status page and compare timestamps with your failed checks.
Test related hosts such as atlassian.com, www.atlassian.com. If they work while confluence.atlassian.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for confluence.atlassian.com, then share those details with Confluence support for faster triage and recovery.
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.
Open confluence.atlassian.com in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on confluence.atlassian.com. Avoid repeated password or security resets until you confirm this is not a broader Confluence issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Confluence support.
Run the automatic multi-region check on this page for confluence.atlassian.com. If most regions fail at the same time, Confluence is likely experiencing a broader outage.
If only one or two regions fail, the issue is usually local to your route, resolver, device state, or account session. Recheck after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use this order so you get reliable signal quickly:
Official dashboards are the source of record, but social channels can surface impact faster in the first minutes of an incident.
That usually means a route-specific or client-specific issue instead of full provider downtime. Common reasons:
Try a private window, switch networks, and compare with this page's regional result before making major local changes.
Use this quick triage sequence:
This keeps your troubleshooting efficient and avoids unnecessary account resets during provider-side incidents.