Skip to content

Outage tracker / Jira (Atlassian)

Is Jira (Atlassian) down?

I'm having a problem

Operationalchecked 2 minutes ago

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

As of Oct 5, 2026, 9:54 PM UTC, Jira (Atlassian) answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 9:54 PM UTC
US-East264 msOperational
US-West628 msOperational
Europe490 msOperational
Asia-Pacific283 msOperational
US-Central243 msOperational
Canada135 msOperational
UK152 msOperational
Southeast Asia215 msOperational
Australia285 msOperational
South America359 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 Oct 5, 2026, 9:28 PM 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
  • WebhooksOperational

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
504msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 387ms2026-09-07 UTC: p95 379ms2026-09-08 UTC: p95 364ms2026-09-09 UTC: p95 345ms2026-09-10 UTC: p95 315ms2026-09-11 UTC: p95 322ms2026-09-12 UTC: p95 279ms2026-09-13 UTC: p95 275ms2026-09-14 UTC: p95 376ms2026-09-15 UTC: p95 414ms2026-09-16 UTC: p95 561ms2026-09-17 UTC: p95 426ms2026-09-18 UTC: p95 358ms2026-09-19 UTC: p95 299ms2026-09-20 UTC: p95 332ms2026-09-21 UTC: p95 345ms2026-09-22 UTC: p95 340ms2026-09-23 UTC: p95 552ms2026-09-24 UTC: p95 600ms2026-09-25 UTC: p95 662ms2026-09-26 UTC: p95 573ms2026-09-27 UTC: p95 596ms2026-09-28 UTC: p95 571ms2026-09-29 UTC: p95 501ms2026-09-30 UTC: p95 631ms2026-10-01 UTC: p95 344ms2026-10-02 UTC: p95 329ms2026-10-03 UTC: p95 403ms2026-10-04 UTC: p95 433ms2026-10-05 UTC: p95 504ms
Sep 6Sep 20Oct 5
US-West
425msp95 · 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-09-06 UTC: p95 457ms2026-09-07 UTC: p95 477ms2026-09-08 UTC: p95 465ms2026-09-09 UTC: p95 286ms2026-09-10 UTC: p95 357ms2026-09-11 UTC: p95 457ms2026-09-12 UTC: p95 505ms2026-09-13 UTC: p95 395ms2026-09-14 UTC: p95 424ms2026-09-15 UTC: p95 528ms2026-09-16 UTC: p95 700ms2026-09-17 UTC: p95 695ms2026-09-18 UTC: p95 618ms2026-09-19 UTC: p95 577ms2026-09-20 UTC: p95 654ms2026-09-21 UTC: p95 433ms2026-09-22 UTC: p95 453ms2026-09-23 UTC: p95 468ms2026-09-24 UTC: p95 715ms2026-09-25 UTC: p95 601ms2026-09-26 UTC: p95 455ms2026-09-27 UTC: p95 493ms2026-09-28 UTC: p95 588ms2026-09-29 UTC: p95 728ms2026-09-30 UTC: p95 433ms2026-10-01 UTC: p95 396ms2026-10-02 UTC: p95 300ms2026-10-03 UTC: p95 388ms2026-10-04 UTC: p95 502ms2026-10-05 UTC: p95 425ms
Sep 6Sep 20Oct 5
Europe
472msp95 · 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-09-06 UTC: p95 398ms2026-09-07 UTC: p95 382ms2026-09-08 UTC: p95 295ms2026-09-09 UTC: p95 358ms2026-09-10 UTC: p95 494ms2026-09-11 UTC: p95 473ms2026-09-12 UTC: p95 324ms2026-09-13 UTC: p95 453ms2026-09-14 UTC: p95 451ms2026-09-15 UTC: p95 276ms2026-09-16 UTC: p95 340ms2026-09-17 UTC: p95 359ms2026-09-18 UTC: p95 201ms2026-09-19 UTC: p95 196ms2026-09-20 UTC: p95 264ms2026-09-21 UTC: p95 251ms2026-09-22 UTC: p95 284ms2026-09-23 UTC: p95 303ms2026-09-24 UTC: p95 373ms2026-09-25 UTC: p95 677ms2026-09-26 UTC: p95 560ms2026-09-27 UTC: p95 493ms2026-09-28 UTC: p95 507ms2026-09-29 UTC: p95 378ms2026-09-30 UTC: p95 361ms2026-10-01 UTC: p95 364ms2026-10-02 UTC: p95 485ms2026-10-03 UTC: p95 487ms2026-10-04 UTC: p95 424ms2026-10-05 UTC: p95 472ms
Sep 6Sep 20Oct 5
Asia-Pacific
468msp95 · 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-09-06 UTC: p95 729ms2026-09-07 UTC: p95 803ms2026-09-08 UTC: p95 762ms2026-09-09 UTC: p95 806ms2026-09-10 UTC: p95 729ms2026-09-11 UTC: p95 614ms2026-09-12 UTC: p95 835ms2026-09-13 UTC: p95 879ms2026-09-14 UTC: p95 714ms2026-09-15 UTC: p95 858ms2026-09-16 UTC: p95 704ms2026-09-17 UTC: p95 790ms2026-09-18 UTC: p95 703ms2026-09-19 UTC: p95 691ms2026-09-20 UTC: p95 622ms2026-09-21 UTC: p95 662ms2026-09-22 UTC: p95 836ms2026-09-23 UTC: p95 916ms2026-09-24 UTC: p95 922ms2026-09-25 UTC: p95 696ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 713ms2026-09-30 UTC: p95 729ms2026-10-01 UTC: p95 806ms2026-10-02 UTC: p95 616ms2026-10-03 UTC: p95 500ms2026-10-04 UTC: p95 554ms2026-10-05 UTC: p95 468ms
Sep 6Sep 20Oct 5
US-Central
319msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 420ms2026-09-07 UTC: p95 410ms2026-09-08 UTC: p95 389ms2026-09-09 UTC: p95 450ms2026-09-10 UTC: p95 320ms2026-09-11 UTC: p95 365ms2026-09-12 UTC: p95 357ms2026-09-13 UTC: p95 381ms2026-09-14 UTC: p95 378ms2026-09-15 UTC: p95 292ms2026-09-16 UTC: p95 294ms2026-09-17 UTC: p95 297ms2026-09-18 UTC: p95 338ms2026-09-19 UTC: p95 368ms2026-09-20 UTC: p95 306ms2026-09-21 UTC: p95 452ms2026-09-22 UTC: p95 436ms2026-09-23 UTC: p95 459ms2026-09-24 UTC: p95 507ms2026-09-25 UTC: p95 376ms2026-09-26 UTC: p95 494ms2026-09-27 UTC: p95 338ms2026-09-28 UTC: p95 481ms2026-09-29 UTC: p95 422ms2026-09-30 UTC: p95 355ms2026-10-01 UTC: p95 306ms2026-10-02 UTC: p95 207ms2026-10-03 UTC: p95 207ms2026-10-04 UTC: p95 382ms2026-10-05 UTC: p95 319ms
Sep 6Sep 20Oct 5
Canada
278msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 459ms2026-09-07 UTC: p95 404ms2026-09-08 UTC: p95 519ms2026-09-09 UTC: p95 532ms2026-09-10 UTC: p95 403ms2026-09-11 UTC: p95 347ms2026-09-12 UTC: p95 525ms2026-09-13 UTC: p95 708ms2026-09-14 UTC: p95 405ms2026-09-15 UTC: p95 368ms2026-09-16 UTC: p95 367ms2026-09-17 UTC: p95 360ms2026-09-18 UTC: p95 359ms2026-09-19 UTC: p95 363ms2026-09-20 UTC: p95 361ms2026-09-21 UTC: p95 340ms2026-09-22 UTC: p95 376ms2026-09-23 UTC: p95 413ms2026-09-24 UTC: p95 387ms2026-09-25 UTC: p95 442ms2026-09-26 UTC: p95 957ms2026-09-27 UTC: p95 414ms2026-09-28 UTC: p95 452ms2026-09-29 UTC: p95 417ms2026-09-30 UTC: p95 453ms2026-10-01 UTC: p95 279ms2026-10-02 UTC: p95 270ms2026-10-03 UTC: p95 310ms2026-10-04 UTC: p95 271ms2026-10-05 UTC: p95 278ms
Sep 6Sep 20Oct 5
UK
406msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 378ms2026-09-07 UTC: p95 307ms2026-09-08 UTC: p95 265ms2026-09-09 UTC: p95 278ms2026-09-10 UTC: p95 224ms2026-09-11 UTC: p95 223ms2026-09-12 UTC: p95 230ms2026-09-13 UTC: p95 234ms2026-09-14 UTC: p95 225ms2026-09-15 UTC: p95 155ms2026-09-16 UTC: p95 245ms2026-09-17 UTC: p95 306ms2026-09-18 UTC: p95 325ms2026-09-19 UTC: p95 288ms2026-09-20 UTC: p95 323ms2026-09-21 UTC: p95 336ms2026-09-22 UTC: p95 367ms2026-09-23 UTC: p95 321ms2026-09-24 UTC: p95 414ms2026-09-25 UTC: p95 390ms2026-09-26 UTC: p95 487ms2026-09-27 UTC: p95 435ms2026-09-28 UTC: p95 338ms2026-09-29 UTC: p95 386ms2026-09-30 UTC: p95 318ms2026-10-01 UTC: p95 362ms2026-10-02 UTC: p95 264ms2026-10-03 UTC: p95 223ms2026-10-04 UTC: p95 366ms2026-10-05 UTC: p95 406ms
Sep 6Sep 20Oct 5
Southeast Asia
966msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 897ms2026-09-14 UTC: p95 939ms2026-09-15 UTC: p95 990ms2026-09-16 UTC: p95 997ms2026-09-17 UTC: p95 854ms2026-09-18 UTC: p95 973ms2026-09-19 UTC: p95 866ms2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 672ms2026-10-02 UTC: p95 992ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 936ms2026-10-05 UTC: p95 966ms
Sep 6Sep 20Oct 5
Australia
586msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 786ms2026-09-07 UTC: p95 941ms2026-09-08 UTC: p95 967ms2026-09-09 UTC: p95 815ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 974ms2026-09-13 UTC: p95 957ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 964ms2026-09-16 UTC: p95 825ms2026-09-17 UTC: p95 971ms2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 874ms2026-09-24 UTC: p95 771ms2026-09-25 UTC: p95 668ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 848ms2026-09-28 UTC: p95 723ms2026-09-29 UTC: p95 814ms2026-09-30 UTC: p95 653ms2026-10-01 UTC: p95 774ms2026-10-02 UTC: p95 660ms2026-10-03 UTC: p95 475ms2026-10-04 UTC: p95 603ms2026-10-05 UTC: p95 586ms
Sep 6Sep 20Oct 5
South America
790msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 788ms2026-09-07 UTC: p95 692ms2026-09-08 UTC: p95 613ms2026-09-09 UTC: p95 898ms2026-09-10 UTC: p95 787ms2026-09-11 UTC: p95 755ms2026-09-12 UTC: p95 802ms2026-09-13 UTC: p95 866ms2026-09-14 UTC: p95 643ms2026-09-15 UTC: p95 571ms2026-09-16 UTC: p95 763ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 786ms2026-09-19 UTC: p95 880ms2026-09-20 UTC: p95 789ms2026-09-21 UTC: p95 753ms2026-09-22 UTC: p95 754ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 827ms2026-09-26 UTC: p95 723ms2026-09-27 UTC: p95 892ms2026-09-28 UTC: p95 711ms2026-09-29 UTC: p95 698ms2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 918ms2026-10-02 UTC: p95 773ms2026-10-03 UTC: p95 675ms2026-10-04 UTC: p95 729ms2026-10-05 UTC: p95 790ms
Sep 6Sep 20Oct 5

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 we measured, function by function

Jira (Atlassian) answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Jira (Atlassian) go down, and when it is back

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.

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

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 264msstatus code: 200checked: Oct 5, 2026, 9:50 PM 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: 628msstatus code: 200checked: Oct 5, 2026, 9:53 PM 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.
    • US-Central
      Operationallatency: 243msstatus code: 200checked: Oct 5, 2026, 9:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Jira (Atlassian) normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 135msstatus code: 200checked: Oct 5, 2026, 9:39 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Jira (Atlassian) normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 359msstatus code: 200checked: Oct 5, 2026, 9:37 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Jira (Atlassian) normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 490msstatus code: 200checked: Oct 5, 2026, 9:54 PM 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.
    • UK
      Operationallatency: 152msstatus code: 200checked: Oct 5, 2026, 9:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Jira (Atlassian) normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 283msstatus code: 200checked: Oct 5, 2026, 9:50 PM 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.
    • Southeast Asia
      Operationallatency: 215msstatus code: 200checked: Oct 5, 2026, 9:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Jira (Atlassian) normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 285msstatus code: 200checked: Oct 5, 2026, 9:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Jira (Atlassian) normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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

Job processing and scheduling is degraded affecting multiple Atlassian products, 4h 56mdeclared on their status page2026-10-01
Degraded Performance Viewing Issues and Boards, 1h 59mdeclared on their status page2026-09-24
Degraded Performance Accessing Jira, 2h 54mdeclared on their status page2026-09-24
Degraded performance affecting Jira Software and Jira Service Management, 51mdeclared on their status page2026-09-11
Disrupted JIRA availability in US East, 1h 5mdeclared on their status page2026-09-03
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

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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

primaryfunctional: auth surface
https://auth.atlassian.com/.well-known/openid-configuration
secondary
https://jira-software.status.atlassian.com/api/v2/status.json
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 10 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. At least one endpoint we check for Jira (Atlassian) is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.