Is Jira Down?

No — Jira is up

Reachable from all 8 checked regions

Average response time: 780ms

Last checked 11 minutes ago · checks run every 6 hours

Official status page: https://jira-software.status.atlassian.com

Jira uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

830ms

Avg response, 30 days

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

30-day history

23-day clean streak

Jul 20 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.

cdg

687ms

DNS 0ms TCP 0ms TLS 3ms TTFB 467ms

dfw

709ms

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

ewr

547ms

DNS 1ms TCP 1ms TLS 5ms TTFB 347ms

fra

613ms

DNS 0ms TCP 1ms TLS 6ms TTFB 409ms

gru

716ms

DNS 1ms TCP 2ms TLS 5ms TTFB 502ms

iad

572ms

DNS 0ms TCP 6ms TLS 4ms TTFB 421ms

jnb

1660ms

DNS 0ms TCP 0ms TLS 2ms TTFB 1440ms

lax

796ms

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

lhr

634ms

DNS 1ms TCP 2ms TLS 4ms TTFB 409ms

What Jira does

Jira is Atlassian's issue and project tracking tool, used for engineering backlogs, sprints and service desks. It commonly holds the workflow that gates releases, and it connects to source hosting and chat, so an outage stops more than ticket updates: it can stall the process a team uses to ship.

What an outage looks like

When Jira is down, boards and backlogs fail to load, issue creation returns errors, and searches time out. Automation rules may not fire, so transitions that normally happen on a commit or a merge silently do not. Linked Confluence pages and service desk portals can be affected at the same time, since they share Atlassian infrastructure.

What to do about it

Check jira-software.status.atlassian.com, which reports Jira separately from Confluence and the other Atlassian products, and confirm the cloud region your site runs in. Work that must be recorded can be captured elsewhere and entered afterwards. Automation that did not fire during the incident generally needs re-running by hand rather than catching up on its own.

Is it down for everyone, or just you?

If this page says Jira 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

Jira outage FAQ

Is Jira down or is it just my site?

Atlassian reports per product and per cloud region, so a global all-clear can sit alongside your site being unavailable. Check the region your instance runs in rather than the headline. Single-site problems that do not appear on the status page at all are usually worth raising with Atlassian support directly.

Does a Jira outage take Confluence down as well?

Not necessarily. They are separate products with separate status components, but they share underlying infrastructure, so platform-level incidents often affect both. Each has its own status page, and comparing them is the quickest way to tell a Jira-specific problem from something broader across Atlassian Cloud.

Do automation rules run once Jira comes back?

Generally not. Rules that would have fired during the incident are missed rather than queued, so transitions, notifications and linked updates that depend on them will not happen retroactively. After a significant outage it is worth reviewing what should have moved and triggering those transitions manually.

Can I still deploy if Jira is down?

Technically yes, unless your pipeline blocks on a Jira check. Many teams gate releases on ticket state, and that gate fails closed during an outage. If you deploy anyway, the tickets will need reconciling afterwards, so note what shipped rather than trusting the board to reflect it later.

How we measure this

We request Jira'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 Jira 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 Jira 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