down
Is Jira down?
Jira is Atlassian’s project and issue tracking software
https://www.atlassian.com/software/jira ↗Mapped components are operational in the latest status update; individual experiences can vary.
Service disruption activity for Jira
Last 24 hoursObserved disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.
Latest observation: 2026-11-08 18:20:30 UTC. Refreshes automatically while this page is visible.
No user-submitted outage reports in the last 24 hours.
Jira outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Jira website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-11-08 18:15:46 UTC.
Public endpoint monitoring — this lightweight resource measures website connectivity and response time. It does not test the application, login, or API. Check official component status below for product availability.
Checked address: https://www.atlassian.com/software/jira
DNS lookup: 4 ms · TCP connection: 1 ms · TLS handshake: 4 ms. Certificate expires 2027-04-08; trusted connection: yes.
100%
Successful website checks (24h)
22 successful / 22 measurable checks
312 ms
Median response time
1526 ms
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
Jira official status · fetched 2026-11-08 18:20:30 UTC
12 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| Viewing content | operational |
| Create and edit | operational |
| Authentication and User Management | operational |
| Search | operational |
| Notifications | operational |
| Administration | operational |
| Marketplace | operational |
| Mobile | operational |
| Purchasing & Licensing | operational |
| Signup | operational |
| Automation for Jira | operational |
| Webhooks | operational |
Official incident timeline
Fields missing across Jira Work Items for some users · resolved · 2026-11-02T00:38:50.996Z
Product match: components.
Read the provider’s incident report
- · resolved
We have now confirmed that all field related operations across the Jira, Jira Software Management, Jira Work Management and Jira Product Discovery should now be fully operational. We apologize for any inconvenience this may have caused.
- · monitoring
Our team has now identified a potential configuration change that appears to have caused this issue and has now reverted this change. We are now starting to see recovery across impacted operations for this issue and will be monitoring to check for a full recovery.
- · investigating
We are aware of an issue that is currently impacting fields across Work Items in Jira family products, including impacts to searching and automations on these fields. We are investigating with urgency and will update within one hour or sooner if we have further information to share.
Jira - Project Sidebar Loading Degradation · resolved · 2026-10-21T15:45:09.481Z
Product match: components.
Read the provider’s incident report
- · resolved
On October 21, 2026, JIRA, JSM, JPD, and JWM users may have experienced performance degradation impacting the project sidebar and navigation. The issue has now been resolved, and the service is operating normally for all affected customers.
- · monitoring
Mitigations are in place and we are seeing recovery across Jira Cloud navigation services. Project sidebars are now loading as expected. Our teams continue to monitor the situation, and we expect to confirm full resolution in our next update in 1 hour or sooner.
- · investigating
We are investigating an issue impacting the project sidebar and navigation in Jira Cloud. Users may encounter timeouts or missing menus when attempting to access project views. Teams are actively analyzing telemetry to identify a mitigation. We will provide our next update in 60 minutes, or sooner.
Job processing and scheduling is degraded affecting multiple Atlassian products · postmortem · 2026-10-09T18:24:34.317Z
Product match: components.
Read the provider’s incident report
- · postmortem
### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhe
- · resolved
On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during th
- · identified
Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.
- · identified
Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.
- · identified
Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.
- · identified
Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.
- · investigating
Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.
Degraded Performance Viewing Issues and Boards · resolved · 2026-09-24T15:53:04.146Z
Product match: components.
Read the provider’s incident report
- · resolved
On September 24th 2026, some Jira and JSM users in the US region may have experienced a performance degradation impacting Jira issue creation, issue viewing, and board loading. The issue has now been resolved, and the service is operating normally for all affected customers.
- · monitoring
Mitigations have been deployed and we are seeing positive signs of recovery across Jira. Issues viewing work items, loading boards, and creating tickets are subsiding. We are continuing to monitor system health to ensure full stability and will share our next update within 60 minutes.
- · investigating
We continue to investigate the issue impacting Jira issue creation, issue viewing, and board loading. Our teams remain engaged on identifying a resolution. We will provide the next update in 1 hour, or sooner if there is material progress.
Degraded Performance Accessing Jira · resolved · 2026-09-24T11:46:14.510Z
Product match: components.
Read the provider’s incident report
- · resolved
On Sept 24th, 2026, between 07:28 to 08:08 UTC, some Jira users may have experienced errors or degraded performance when accessing Jira and viewing issues. The issue has now been resolved and the service is operating normally for all customers.
- · monitoring
We are continuing to closely monitor the situation to ensure full stability across Jira. Recovery signs remain steady. Our next update will be shared in 60 minutes, or sooner.
- · monitoring
We have been tracking an issue impacting Jira where users may have encountered errors or degraded performance accessing Jira and viewing issues. Mitigations are in place and we are seeing positive signs of recovery. Our teams are continuing to monitor the situation, and we expect to confirm resolution within the next 60 minutes.
Degraded performance affecting Jira Software and Jira Service Management · postmortem · 2026-09-21T22:36:31.407Z
Product match: components.
Read the provider’s incident report
- · postmortem
### Summary On September 11, 2026, between 07:02 and 07:56 UTC, Atlassian customers primarily from the EU region and some from APAC region using Jira and Jira Service Management products were unable to view work items or access boards consistently. The event was triggered by a backward-incompatible internal configuration rollout in the underlying graph data platform. The incident was detected within 3 minutes by our automated monitoring system and mitigated by rolling forward the stable de
- · resolved
On 11 September 2026, Between 07:02 UTC and 07:56 UTC, some Jira Software and Jira Service Management users may have experienced degraded performance and errors when accessing Work Items and Boards. The issue has now been resolved, and all services are operating normally.
- · monitoring
A mitigation has been deployed, and we are observing recovery across Jira Software and Jira Service Management issue views and boards. Our engineering teams are closely monitoring the environment to ensure sustained stability. We will provide another update once full resolution is confirmed or within 60 minutes.
- · investigating
We are investigating reports of an issue affecting Jira Software and Jira Service Management. Affected users may experience errors or delays when loading issue views and viewing boards. We are working to identify the root cause and will provide an update as more information becomes available.
Disrupted JIRA availability in US East · postmortem · 2026-09-10T18:15:35.297Z
Product match: components.
Read the provider’s incident report
- · postmortem
### Summary On September 3, 2026, between 14:52 and 17:02 UTC, Atlassian customers using Jira and Jira Service Management in the US-East region experienced intermittent errors and degraded access to core Jira experiences, including Rovo, viewing issues, boards, navigation, search-backed experiences, workflow-related actions. The event was triggered by a progressive rollout of a caching change in Atlassian's authorization service. The change increased cache traffic and caused saturation in the c
- · resolved
On September 3, 2026, JIRA experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
- · monitoring
Our teams have taken mitigation steps to reduce the impact and recovery among affected customers began at 16:15 UTC. We continue to investigate the root cause of the issue, and will share additional updates here as more information is available.
- · investigating
We are actively investigating reports of a service disruption affecting JIRA customers in US East. We will share updates here as more information is available.
Degraded performance of JIRA · resolved · 2026-09-01T21:35:09.621Z
Product match: components.
Read the provider’s incident report
- · resolved
On September 1, some JIRA users may have experienced performance degradation affecting forms functionality. The issue has now been resolved, and the service is operating normally for all affected customers.
- · monitoring
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.
- · identified
Our teams continue to work on the mitigation. We will continue to share additional updates here as more information is available.
- · identified
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience forms not working as expected. We will continue to share additional updates here as more information is available.
- · investigating
We are actively investigating reports of performance degradation affecting forms functionality. We will share updates here as more information is available.
Recovery tracker
No recent recovery can be established from available evidence.
1 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
No sustained slowdown has been established against the earlier baseline.
Recent median: 305 ms · Earlier median: 313 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Jira.
No active incidents recorded.
- Spectrum Availability Issue in Phoenix · monitoring
- Fedramp Customers have Delayed Purges · identified
About Jira status on Iszdown
Jira is Atlassian’s project and issue tracking software. Cloud and self-managed deployments have different operational environments.
This page combines the available Jira report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
12 product-matched official components are listed above. Latest public website measurement: 2026-11-08T18:15:46.000Z.
Visit the official Jira website · Official provider status · How it works
What to check when Jira is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Check your tenant and affected workflow
Note the product, account region or instance, and whether the issue affects sign-in, a specific workflow, or an integration. A public website response does not test your organization’s account.
Separate access problems from application errors
Check your organization’s sign-in service and whether colleagues see the same error. Keep private customer data, employee information, credentials, and access tokens out of public reports.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Jira outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Fields missing across Jira Work Items for some users | 28 min | resolved | |
| Jira - Project Sidebar Loading Degradation | 76 min | resolved | |
| Job processing and scheduling is degraded affecting multiple Atlassian products | 296 min | postmortem | |
| Degraded Performance Viewing Issues and Boards | 119 min | resolved | |
| Degraded performance affecting Jira Software and Jira Service Management | 51 min | postmortem | |
| Disrupted JIRA availability in US East | 65 min | postmortem | |
| Degraded performance of JIRA | 266 min | resolved | |
| Jira - Work Item transition failures | 151 min | resolved |
Frequently asked questions about Jira
Is Jira down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-08T18:22:13.000Z.
How many Jira outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-07T18:20:00.000Z to 2026-11-08T18:20:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Jira show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Jira feature.
When was Jira status last updated?
The latest status observation was 2026-11-08T18:20:30.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has Jira had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Jira or report a problem?
Use “Watch this service” to save Jira in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Jira
Check a related product separately; its status can differ from Jira.