Is Confluence Down?

No — Confluence is up

Reachable from all 8 checked regions

Average response time: 326ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://confluence.status.atlassian.com

Confluence uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

365ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 7 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

7-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad

149ms

DNS 1ms TCP 1ms TLS 5ms TTFB 144ms

jnb

1817ms

DNS 0ms TCP 0ms TLS 3ms TTFB 1814ms

lax

119ms

DNS 0ms TCP 1ms TLS 4ms TTFB 116ms

lhr

89ms

DNS 0ms TCP 2ms TLS 4ms TTFB 84ms

nrt

101ms

DNS 0ms TCP 2ms TLS 4ms TTFB 97ms

ord

142ms

DNS 0ms TCP 1ms TLS 4ms TTFB 137ms

sin

78ms

DNS 0ms TCP 2ms TLS 3ms TTFB 74ms

sjc

115ms

DNS 0ms TCP 1ms TLS 3ms TTFB 113ms

What Confluence does

Confluence is Atlassian's team wiki: shared pages, meeting notes, requirements and internal documentation, normally sitting next to Jira. Teams keep runbooks and onboarding guides in it, which is why an outage often surfaces in the middle of some other incident. Customer sites run on per-tenant atlassian.net hostnames, so this page measures Atlassian's own public Confluence surface rather than your site.

What an outage looks like

Pages open but editing fails, or a save returns a Something went wrong error. Search stops returning results while existing pages still load. Comments and notifications lag or disappear. Anonymous readers following public share links break while signed-in users continue working. Macros and Marketplace apps embedded in a page render as error blocks instead of content.

What to do about it

Check confluence.status.atlassian.com, which reports Confluence by component: View Content, Create and Edit, Search, Comments, Notifications and Marketplace Apps. Matching your symptom to a component tells you whether to wait or to look at your own network and SSO. Leave unsaved editing tabs open, because drafts are held client-side. Jira and Bitbucket have their own separate status pages.

Is it down for everyone, or just you?

If this page says Confluence is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Confluence outage FAQ

Is Confluence down for everyone or only my site?

Atlassian Cloud spreads customers across separate instances, so an incident can affect some tenants and leave others untouched. The status page reports Cloud-wide components, so a fully green board alongside a broken site points at your own instance, network or SSO rather than at Atlassian. Testing from another network, or asking a colleague on a different connection, separates the two in a minute.

Does a Confluence outage take Jira down too?

Not necessarily. Confluence and Jira are separate products with separate status pages, but they share Atlassian account infrastructure. When that shared piece fails, authentication and user management break in both at once. When only Confluence components are degraded, Jira keeps working and the Confluence pages linked inside Jira issues are the part that fails to load.

Will I lose the page I was editing?

Usually not. Confluence writes drafts as you type and keeps unsaved changes in the editor, so a page normally recovers once the service returns. The real risk is closing the tab or navigating away while saves are failing. Leave the tab open, copy anything long into a local file, then retry the save after the status page clears.

Why can outside readers not open our public pages when our team can?

Anonymous access runs through a different path from signed-in access, and it can fail on its own. Atlassian has had incidents where people arriving through public share links saw an error while logged-in users were unaffected. If your published documentation is broken for external readers but fine internally, that pattern fits an Atlassian-side anonymous-access fault rather than a permissions change on your side.

How we measure this

We request Confluence's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Confluence publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Confluence goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required