# Atlassian status

> Is Atlassian down? Live status for Jira and Confluence Cloud, uptime history, and per-region response times from our own probes every 2 minutes.

Published: 2026-09-08 | Canonical: https://yoping.me/status/atlassian

## How we check Atlassian

We watch id.atlassian.com from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

Atlassian Cloud spans Jira, Confluence, Bitbucket, and more across independently hosted customer sites, so no single URL represents every customer's experience. We watch the shared identity host every Atlassian Cloud product authenticates through regardless of which product or site is being accessed, and pin the response an anonymous request receives rather than assuming a 2xx.

The live board - the current verdict, 24-hour, 7-day, and 30-day uptime, and per-region response times - is on the HTML page at https://yoping.me/status/atlassian. Those numbers change too fast to repeat honestly in a static mirror, so where an answer below says "the board above", it means that page.

## What is Atlassian?

Atlassian's cloud products, Jira for issue tracking, Confluence for
documentation, and Bitbucket for code hosting among others, are sold as
independently hosted sites under one identity system and one billing
relationship. That architecture means an incident affecting one product
or one customer's site does not necessarily say anything about the
others, which is worth understanding before treating any single
disruption as a platform-wide event.

Every Atlassian Cloud product authenticates through a shared identity
layer regardless of which product or which customer's site is being
accessed, which is why this page watches that shared entry point rather
than any single product or instance. It is a meaningful signal for
whether the platform's shared front door is reachable, and it is
deliberately narrower than a claim about Jira, Confluence, or Bitbucket
specifically, each of which can have its own incident independent of the
identity layer.

Marketplace apps are a frequent source of trouble that looks like a
platform incident and is not one. Jira and Confluence both support a
large ecosystem of third-party apps, and one that hooks into workflows,
permissions, or automation can break in a way that makes part of a site
appear broken while Atlassian's core infrastructure answers every
request correctly. Disabling a recently installed or updated app is
often a faster diagnosis than waiting on a status update.

Permission and scheme changes inside a site cause a similar kind of
confusion. A permission scheme edited during unrelated reorganisation, a
workflow changed to add an approval step, or a project archived by
mistake will all make part of a site behave unexpectedly while Atlassian
itself remains entirely healthy. These are changes made inside the site,
not platform incidents, and reviewing recent administrative activity
usually finds the cause faster than anything external can.

Integrations built on the Jira or Confluence REST API depend on
credentials that expire or get revoked on their own schedule, independent
of the platform's health. An integration failing with an authentication
error after working reliably for weeks is worth checking against recent
token rotations or permission changes before it is treated as evidence
that Atlassian itself is having a problem.

## Frequently asked questions

### Is Atlassian down right now?

Check the board above; it reflects our own probes against Atlassian's shared identity host from all five of our regions, refreshed every couple of minutes. Your team's actual Jira or Confluence site runs on its own instance, so this is a reading of the shared login layer rather than of your specific site.

### Our Jira or Confluence site is unreachable but this page shows Atlassian up. What should I check?

Check Atlassian's status page for incidents scoped to your specific product and region, because Atlassian Cloud hosts sites across many independent instances and an incident is typically scoped to one product or region rather than the whole platform. A recently changed app installed from the Marketplace, a permission scheme edit, or an expired API token used by an integration can all make a site behave as if it is down while Atlassian broadly reports healthy.

### Does an Atlassian outage affect issues or pages already created?

No. An outage affects the ability to reach and edit content going forward, not the durability of issues, pages, or comments already saved. The practical question after any incident is whether an automation rule or integration mid-run completed successfully, which the audit log settles more reliably than assuming either outcome.

### Is the Atlassian status page the same as this one?

No. Atlassian's own status page reports what their team has confirmed internally, broken down by product and region, in more detail than an outside probe can offer. This page reports what our own probes measured against the shared identity host, from outside Atlassian's infrastructure, on a fixed schedule, whether or not Atlassian has posted an update yet.

### An integration using the Jira or Confluence API is failing with an authentication error. Is that an outage?

Usually not. API tokens and OAuth credentials expire or get revoked independently of the platform's health, and a security policy change, a token rotation, or a permission scheme edit can all break an integration's access without anything on Atlassian's side going down.