Skip to content

Outage tracker / Jira (Atlassian)

Is Jira (Atlassian) down?

I'm having a problem

Vendor reports no incidentWhat Jira (Atlassian) reports

Jira (Atlassian) reports no incident on its status page.

As of the last successful poll, 2026-10-22 21:50 UTC.

Jira (Atlassian)'s status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Jira (Atlassian) pass from all 10 regions we check.

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

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 9:54 PM UTC
US-East455 msChecks passing
US-West343 msChecks passing
Europe181 msChecks passing
Asia-Pacific571 msChecks passing
US-Central350 msChecks passing
Canada172 msChecks passing
UK253 msChecks passing
Southeast Asia1217 msChecks passing
Australia538 msChecks passing
South America866 msChecks passing
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 22, 2026, 9:52 PM UTC
Jira (Atlassian)'s own status page shows no incident, and our checks of Jira (Atlassian) pass 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
929msp95 · 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-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 544ms2026-10-06 UTC: p95 494ms2026-10-07 UTC: p95 537ms2026-10-08 UTC: p95 394ms2026-10-09 UTC: p95 433ms2026-10-10 UTC: p95 478ms2026-10-11 UTC: p95 480ms2026-10-12 UTC: p95 544ms2026-10-13 UTC: p95 549ms2026-10-14 UTC: p95 468ms2026-10-15 UTC: p95 529ms2026-10-16 UTC: p95 631ms2026-10-17 UTC: p95 509ms2026-10-18 UTC: p95 775ms2026-10-19 UTC: p95 986ms2026-10-20 UTC: p95 854ms2026-10-21 UTC: p95 742ms2026-10-22 UTC: p95 929ms
Sep 23Oct 7Oct 22
US-West
659msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 475ms2026-10-06 UTC: p95 665ms2026-10-07 UTC: p95 407ms2026-10-08 UTC: p95 398ms2026-10-09 UTC: p95 428ms2026-10-10 UTC: p95 468ms2026-10-11 UTC: p95 412ms2026-10-12 UTC: p95 478ms2026-10-13 UTC: p95 542ms2026-10-14 UTC: p95 473ms2026-10-15 UTC: p95 471ms2026-10-16 UTC: p95 488ms2026-10-17 UTC: p95 405ms2026-10-18 UTC: p95 706ms2026-10-19 UTC: p95 713ms2026-10-20 UTC: p95 607ms2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 659ms
Sep 23Oct 7Oct 22
Europe
335msp95 · 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-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 471ms2026-10-06 UTC: p95 419ms2026-10-07 UTC: p95 344ms2026-10-08 UTC: p95 366ms2026-10-09 UTC: p95 308ms2026-10-10 UTC: p95 390ms2026-10-11 UTC: p95 371ms2026-10-12 UTC: p95 616ms2026-10-13 UTC: p95 406ms2026-10-14 UTC: p95 376ms2026-10-15 UTC: p95 333ms2026-10-16 UTC: p95 302ms2026-10-17 UTC: p95 334ms2026-10-18 UTC: p95 401ms2026-10-19 UTC: p95 519ms2026-10-20 UTC: p95 407ms2026-10-21 UTC: p95 292ms2026-10-22 UTC: p95 335ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.2sp95 · 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-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 494ms2026-10-06 UTC: p95 511ms2026-10-07 UTC: p95 520ms2026-10-08 UTC: p95 492ms2026-10-09 UTC: p95 503ms2026-10-10 UTC: p95 490ms2026-10-11 UTC: p95 576ms2026-10-12 UTC: p95 592ms2026-10-13 UTC: p95 722ms2026-10-14 UTC: p95 613ms2026-10-15 UTC: p95 528ms2026-10-16 UTC: p95 663ms2026-10-17 UTC: p95 651ms2026-10-18 UTC: p95 468ms2026-10-19 UTC: p95 772ms2026-10-20 UTC: p95 726ms2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
US-Central
424msp95 · 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-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 322ms2026-10-06 UTC: p95 407ms2026-10-07 UTC: p95 286ms2026-10-08 UTC: p95 336ms2026-10-09 UTC: p95 342ms2026-10-10 UTC: p95 513ms2026-10-11 UTC: p95 373ms2026-10-12 UTC: p95 618ms2026-10-13 UTC: p95 680ms2026-10-14 UTC: p95 500ms2026-10-15 UTC: p95 455ms2026-10-16 UTC: p95 382ms2026-10-17 UTC: p95 249ms2026-10-18 UTC: p95 247ms2026-10-19 UTC: p95 247ms2026-10-20 UTC: p95 387ms2026-10-21 UTC: p95 355ms2026-10-22 UTC: p95 424ms
Sep 23Oct 7Oct 22
Canada
262msp95 · 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-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 274ms2026-10-06 UTC: p95 240ms2026-10-07 UTC: p95 252ms2026-10-08 UTC: p95 379ms2026-10-09 UTC: p95 328ms2026-10-10 UTC: p95 424ms2026-10-11 UTC: p95 502ms2026-10-12 UTC: p95 524ms2026-10-13 UTC: p95 463ms2026-10-14 UTC: p95 489ms2026-10-15 UTC: p95 515ms2026-10-16 UTC: p95 500ms2026-10-17 UTC: p95 530ms2026-10-18 UTC: p95 428ms2026-10-19 UTC: p95 430ms2026-10-20 UTC: p95 589ms2026-10-21 UTC: p95 662ms2026-10-22 UTC: p95 262ms
Sep 23Oct 7Oct 22
UK
305msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 420ms2026-10-06 UTC: p95 360ms2026-10-07 UTC: p95 387ms2026-10-08 UTC: p95 397ms2026-10-09 UTC: p95 405ms2026-10-10 UTC: p95 387ms2026-10-11 UTC: p95 394ms2026-10-12 UTC: p95 394ms2026-10-13 UTC: p95 295ms2026-10-14 UTC: p95 321ms2026-10-15 UTC: p95 338ms2026-10-16 UTC: p95 378ms2026-10-17 UTC: p95 523ms2026-10-18 UTC: p95 923ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 754ms2026-10-21 UTC: p95 607ms2026-10-22 UTC: p95 305ms
Sep 23Oct 7Oct 22
Southeast Asia
1.2sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 947ms2026-10-06 UTC: p95 669ms2026-10-07 UTC: p95 607ms2026-10-08 UTC: p95 974ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 997ms2026-10-11 UTC: p95 921ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 932ms2026-10-15 UTC: p95 917ms2026-10-16 UTC: p95 993ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
Australia
737msp95 · 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-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 579ms2026-10-06 UTC: p95 686ms2026-10-07 UTC: p95 926ms2026-10-08 UTC: p95 464ms2026-10-09 UTC: p95 430ms2026-10-10 UTC: p95 712ms2026-10-11 UTC: p95 779ms2026-10-12 UTC: p95 836ms2026-10-13 UTC: p95 907ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 780ms2026-10-16 UTC: p95 890ms2026-10-17 UTC: p95 923ms2026-10-18 UTC: p95 585ms2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 745ms2026-10-22 UTC: p95 737ms
Sep 23Oct 7Oct 22
South America
1.3sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 784ms2026-10-06 UTC: p95 693ms2026-10-07 UTC: p95 2.6s2026-10-08 UTC: p95 630ms2026-10-09 UTC: p95 584ms2026-10-10 UTC: p95 777ms2026-10-11 UTC: p95 652ms2026-10-12 UTC: p95 532ms2026-10-13 UTC: p95 692ms2026-10-14 UTC: p95 577ms2026-10-15 UTC: p95 728ms2026-10-16 UTC: p95 533ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 774ms2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22

Check your own site while you wait on Jira (Atlassian)

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Jira (Atlassian) reports an incident on its status page, and again when it reports it resolved.

Get an email when Jira (Atlassian) reports an incident

Email me when Jira (Atlassian) reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Jira (Atlassian)'s own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 455msstatus code: 200checked: Oct 22, 2026, 9:54 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
      Checks passinglatency: 343msstatus code: 200checked: Oct 22, 2026, 9:47 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
      Checks passinglatency: 350msstatus code: 200checked: Oct 22, 2026, 9:54 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
      Checks passinglatency: 172msstatus code: 200checked: Oct 22, 2026, 9:53 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
    Checks passinglatency: 866msstatus code: 200checked: Oct 22, 2026, 9:35 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 181msstatus code: 200checked: Oct 22, 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
      Checks passinglatency: 253msstatus code: 200checked: Oct 22, 2026, 9:35 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 571msstatus code: 200checked: Oct 22, 2026, 9:54 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
      Checks passinglatency: 1217msstatus code: 200checked: Oct 22, 2026, 9:35 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
      Checks passinglatency: 538msstatus code: 200checked: Oct 22, 2026, 9:54 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 probe events

Jira - Project Sidebar Loading Degradation, 1h 16mdeclared on their status page2026-10-21
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

check 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 check readings and Jira (Atlassian)'s own claim at the time, side by side.

Full check history for Jira (Atlassian): 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![Jira (Atlassian) uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Jira (Atlassian) down?", https://realuptime.io/outages/atlassian-jira. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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

What our check can and cannot see

A pass means the configuration document the service publishes, such as an API or sign-in description, loaded. That document is usually static or cached, so it does not show that the endpoints it describes are answering.

Host checked: auth.atlassian.com

RealUptime is not affiliated with Jira (Atlassian); the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.