CheckWebsiteNow

Live status check

Is Atlassian (Jira, Confluence) down right now?

We check atlassian.com from one measurement point when you open this page. This shows what we saw, not a worldwide verdict.

A fresh check of atlassian.com runs in your browser. If no result appears, run the check on the start page.

Our last check

Not checked yet — a fresh check starts when you open this page.

About Atlassian (Jira, Confluence) problems

Atlassian problems can affect sign-in, Jira or Confluence pages that will not load, search or notifications in Atlassian Cloud products. Check the Atlassian status page first, which lists each product separately, then check whether only your own site or one product shows the problem. Integrations that call the Atlassian Cloud APIs can also be slowed down by rate limiting.

Official information

Atlassian (Jira, Confluence) official status page (verified )

Our check and Atlassian (Jira, Confluence)'s own status page can disagree. We test from one location and read only the homepage response. The provider reports what it knows about its own systems, such as sign-in, apps or single regions. A site can answer our check while one feature is broken, and a regional problem can affect one location but not another.

Atlassian (Jira, Confluence) help pages

How this check works

  • One measurement location (single-self-hosted-probe), not a worldwide test.
  • We read only the response headers of the HTTPS homepage; page content and features are not tested.
  • We follow at most 5 HTTPS redirects and check every new address again.
  • The whole check stops after 10 seconds.
  • Results are reused for 60 seconds; this page refreshes its saved check at most every 10 minutes.

Full method and limits

Typical Atlassian (Jira, Confluence) problems

An editorial list of typical problems, not based on live user reports.

  • Sign-in keeps looping Atlassian sign-in goes through id.atlassian.com or a company single sign-on page, so stale cookies for those addresses can cause a loop. Guide: ERR_TOO_MANY_REDIRECTS
  • Jira or Confluence does not load If a Jira or Confluence site shows a server error, compare the product with the Atlassian status page before changing browser settings. Guide: 503 Service Unavailable
  • API requests are limited Atlassian Cloud REST APIs answer 429 when an integration sends too many requests, so it should wait for the Retry-After time before retrying. Guide: 429 Too Many Requests
  • Access to an issue or page is denied A Jira issue or Confluence page that says you do not have access can need a permission change by a site or project admin. Guide: 403 Forbidden
  • Notifications do not arrive Missing Jira or Confluence emails can be caught by spam filters or turned off in personal notification settings, so check both before assuming an outage.

General fixes: Developer tools

  1. Read the full error response API and git errors include a status code and a message. A 401 or 403 points to credentials or permissions, a 429 to rate limits and a 5xx code to the provider.
  2. Check tokens and scopes Expired tokens and missing scopes can cause sudden failures. Create a fresh token with only the scopes you need.
  3. Try HTTPS and SSH If git fails over one protocol, test the other one. Some networks block SSH while HTTPS still works.
  4. Retry with growing pauses For temporary errors, wait and retry with longer pauses each time instead of retrying in a tight loop, which can trigger rate limits.

Check another website

One measurement point. Results explain what we saw, not a worldwide verdict.