Skip to content

Outage tracker / Jira (Atlassian)

Is Jira (Atlassian) down?

Short linkrlup.io/down/atlassian-jira

I'm having a problem

Operationalchecked 3 minutes ago

We reached Jira (Atlassian) from all 4 regions we check.

Reachability verified

No outage recorded in the 14 days we have measured Jira (Atlassian) (since Aug 20, 2026).

our independent probeslive · checked Sep 3, 2026, 1:29 AM UTC
US-East800 msOperational
US-West387 msOperational
Europe51 msOperational
Asia-Pacific698 msOperational
their status pagetheir claim, not our reading

Jira (Atlassian) reports: All systems operational (“All Systems Operational”)

from Jira (Atlassian)'s own status page, checked Sep 3, 2026, 12:26 AM UTC
Our probes and Jira (Atlassian)'s own status page agree: both show Jira (Atlassian) as reachable right now.

Jira (Atlassian)'s own component breakdown, as they publish it

  • Viewing contentOperational
  • Create and editOperational
  • Authentication and User ManagementOperational
  • SearchOperational
  • NotificationsOperational
  • AdministrationOperational
  • MarketplaceOperational
  • MobileOperational
  • Purchasing & LicensingOperational
  • SignupOperational
  • Automation for JiraOperational

These are Jira (Atlassian)'s components, named and scored by Jira (Atlassian). We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Jira (Atlassian)'s own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Jira (Atlassian) response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 413ms2026-08-21 UTC: p95 354ms2026-08-22 UTC: p95 369ms2026-08-23 UTC: p95 587ms2026-08-24 UTC: p95 525ms2026-08-25 UTC: p95 642ms2026-08-26 UTC: p95 527ms2026-08-27 UTC: p95 494ms2026-08-28 UTC: p95 669ms2026-08-29 UTC: p95 560ms2026-08-30 UTC: p95 701ms2026-08-31 UTC: p95 618ms2026-09-01 UTC: p95 681ms2026-09-02 UTC: p95 1.2s2026-09-03 UTC: p95 1.1s
Aug 5Aug 19Sep 3
US-West
573msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 533ms2026-08-21 UTC: p95 497ms2026-08-22 UTC: p95 372ms2026-08-23 UTC: p95 455ms2026-08-24 UTC: p95 397ms2026-08-25 UTC: p95 589ms2026-08-26 UTC: p95 367ms2026-08-27 UTC: p95 532ms2026-08-28 UTC: p95 755ms2026-08-29 UTC: p95 679ms2026-08-30 UTC: p95 455ms2026-08-31 UTC: p95 556ms2026-09-01 UTC: p95 490ms2026-09-02 UTC: p95 731ms2026-09-03 UTC: p95 573ms
Aug 5Aug 19Sep 3
Europe
273msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 184ms2026-08-21 UTC: p95 254ms2026-08-22 UTC: p95 258ms2026-08-23 UTC: p95 317ms2026-08-24 UTC: p95 579ms2026-08-25 UTC: p95 295ms2026-08-26 UTC: p95 354ms2026-08-27 UTC: p95 374ms2026-08-28 UTC: p95 325ms2026-08-29 UTC: p95 402ms2026-08-30 UTC: p95 336ms2026-08-31 UTC: p95 354ms2026-09-01 UTC: p95 320ms2026-09-02 UTC: p95 400ms2026-09-03 UTC: p95 273ms
Aug 5Aug 19Sep 3
Asia-Pacific
1.5sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 783ms2026-08-21 UTC: p95 834ms2026-08-22 UTC: p95 973ms2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 944ms2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 787ms2026-08-27 UTC: p95 952ms2026-08-28 UTC: p95 915ms2026-08-29 UTC: p95 1.1s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.0s2026-09-03 UTC: p95 1.5s
Aug 5Aug 19Sep 3

Is it Jira (Atlassian), or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Jira (Atlassian) -- it cannot diagnose Jira (Atlassian)'s own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 800msstatus code: 200checked: Sep 3, 2026, 1:07 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Jira (Atlassian) normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 387msstatus code: 200checked: Sep 3, 2026, 1:02 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Jira (Atlassian) normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 51msstatus code: 200checked: Sep 3, 2026, 1:29 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Jira (Atlassian) normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 698msstatus code: 200checked: Sep 3, 2026, 1:01 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Jira (Atlassian) normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionJira (Atlassian) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionJira (Atlassian) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionJira (Atlassian) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionJira (Atlassian) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionJira (Atlassian) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionJira (Atlassian) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Jira (Atlassian), counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Jira (Atlassian) yet, which is not evidence that nothing is wrong.

Recent outages

Degraded performance of JIRA, 4h 26mdeclared on their status page2026-09-01
Jira - Work Item transition failures, 2h 31mdeclared on their status page2026-09-01
Fetching mails from Microsoft accounts producing errors and preventing email based creation of Jira work items, 10h 50mdeclared on their status page2026-08-31
Issues accessing multiple Atlassian products in some regions, 54mdeclared on their status page2026-08-27
Notifications are delayed, 5h 51mdeclared on their status page2026-08-25
Degraded performance of Notifications, 3h 53mdeclared on their status page2026-08-24
Performance and access related issues with Jira, 1h 21mdeclared on their status page2026-08-07
Degraded performance of JIRA, 22mdeclared on their status page2026-08-07

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Jira (Atlassian) since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Jira (Atlassian) covering any window you pick, with our measurements and Jira (Atlassian)'s own claim at the time, side by side.

Full availability history for Jira (Atlassian): 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Jira (Atlassian), and again when they can reach it again. That is our own measurement from ten regions, not Jira (Atlassian)'s status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Jira (Atlassian) uptime measured by RealUptimeLive, from this page's own readings.
[![Jira (Atlassian) uptime measured by RealUptime](https://realuptime.io/outages/atlassian-jira/badge.svg?days=30)](https://realuptime.io/outages/atlassian-jira)
<a href="https://realuptime.io/outages/atlassian-jira"><img src="https://realuptime.io/outages/atlassian-jira/badge.svg?days=30" alt="Jira (Atlassian) uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Jira (Atlassian)'s SLA implies, from our measurement

At or above your target

We measured none of downtime for Jira (Atlassian) over the 337h 32m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Jira (Atlassian)'s SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primary
https://jira-software.status.atlassian.com/
secondary
https://www.atlassian.com/software/jira
RealUptime is not affiliated with Jira (Atlassian); the name identifies what we measured, and nothing here speaks for Jira (Atlassian)'s own team. We send a single web request to Jira (Atlassian) from 4 regions on our own schedule and time the response. We do not see inside Jira (Atlassian)'s systems, do not use an account or real transaction, and are not the same signal Jira (Atlassian)'s own team has access to. Treat this as one external data point, not a verdict. What we check for Jira (Atlassian) proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Jira (Atlassian) operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.

Related services

AkamaiAmplitudeAnthropicAuth0AWS (Amazon Web Services)