Is Atlassian down right now?

No. Our checks are finding no problems with Atlassian right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Atlassian continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are website / app down, can't log in, API errors, slow or laggy, can't connect, 5xx error pages, files won't sync and no notifications. Those are the options the report button offers for Atlassian, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Atlassian specifically, Jira, Confluence, Bitbucket and Atlassian Access run separately, and cloud sites are spread across regions. Your site can be broken while a colleague's on another region is fine, which is why Atlassian reports incidents per product rather than per customer. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Atlassian, open a different Atlassian product on the same account, so Confluence if Jira is failing. One working and the other not is them. Both failing while atlassian.com loads points at your own site URL, your session or your identity provider. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Atlassian's side. Specifically: avoid re-saving a Confluence page or repeating a Jira transition that appeared to fail. Atlassian often applies the write and loses the response, so retrying leaves you with duplicate issues and conflicting page versions to merge later. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Atlassian publishes a machine-readable status feed, so our first check reads it directly and reports what Atlassian itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.atlassian.com, and it is linked further up this page. That is Atlassian's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Atlassian or atlassian.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Atlassian's own support, not us.