Is Atlassian down right now?

While you wait: the Atlassian incident checklist

1. Identify the product, not the brand. status.atlassian.com splits Jira, Confluence, Jira Service Management and platform services into separate components — and Bitbucket publishes on its own page at bitbucket.status.atlassian.com. Confirm exactly which product is degraded.
2. Grab your runbooks now. If incident runbooks live in Confluence, open your out-of-band copies before you need them. If there are no out-of-band copies, that's your first postmortem action item.
3. Verify paging still works. If Jira Service Management or Opsgenie carries your on-call paging, push a low-severity test page through the pipeline. Don't discover paging is dead when a real alert fires.
4. Treat Bitbucket like any Git-host outage. Repos and Pipelines blocked means pause deploys or switch to the break-glass path — and remember queued pipelines will all run on recovery.
5. Kill the prod-panic early. Atlassian cloud incidents are usually internal-tooling outages, not customer-facing ones. Say so explicitly: 'Jira/Confluence is down; production is unaffected; we're tracking work in the fallback channel.'

What breaks when Atlassian has issues

The classic Atlassian blast radius is losing your coordination layer at the worst moment: tickets, boards, and — most painfully — the Confluence pages your runbooks live on. If Jira Service Management or Opsgenie handles paging and support queues, an incident there can mean missed pages and a silent support inbox. Bitbucket outages block repos and Pipelines like any Git-host incident. Customer-facing impact is usually zero; the hit lands on your team's ability to respond and communicate.