Is Jira Down?
- Jira's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 872 ms
Right now
The verdict is the worse of these two. How we decide
Jira's status page
jira-software.status.atlassian.com · read · checked every 3 minutes
| Component | 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 |
FlareWarden checks
atlassian.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 872 ms
- Checked
By region
- Ashburn reachable, 649 ms
- Frankfurt reachable, 550 ms
- Johannesburg reachable, 1922 ms
- London reachable, 623 ms
- Los Angeles reachable, 636 ms
- Newark reachable, 758 ms
- São Paulo reachable, 998 ms
- Tokyo reachable, 846 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 116 ms | 1 ms | 4 ms | 448 ms |
| Frankfurt | 62 ms | 3 ms | 4 ms | 359 ms |
| Johannesburg | 154 ms | 1 ms | 3 ms | 1881 ms |
| London | 20 ms | 3 ms | 5 ms | 428 ms |
| Los Angeles | 41 ms | 5 ms | 5 ms | 437 ms |
| Newark | 101 ms | 6 ms | 5 ms | 590 ms |
| São Paulo | 163 ms | 1 ms | 3 ms | 647 ms |
| Tokyo | 39 ms | 2 ms | 4 ms | 642 ms |
History
Incidents Jira reported
Since Oct 22, 15 days · from jira-software.status.atlassian.com
- Incidents
- 2
- Major or critical
- 1
- Median to resolve
- 52m
- lasted 28m
- lasted 1h 16m
Jira website availability
Measured by FlareWarden · atlassian.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 963ms
Last 30 days
91-day clean streakMeasured by FlareWarden's own checks of atlassian.com from multiple regions every 6 hours. Jira's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
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 up to 17 cities across three regions to find out where it breaks.
Related services
Jira outage FAQ
Is Jira down or is it just my site?
Does a Jira outage take Confluence down as well?
Do automation rules run once Jira comes back?
Can I still deploy if Jira is down?
How we measure this
- We request Jira's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Jira itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Jira goes down
We check Jira every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring