Jira Status: How to Check If Jira Is Down Right Now (2026)
Where to find the official Jira and Atlassian status page, what each component means, and how to diagnose Jira Software, Jira Service Management, Confluence, and API issues.
Is Jira Down Right Now?
Check status.atlassian.com for Atlassian Cloud status across all products, or jira-software.status.atlassian.com specifically for Jira Software.
Atlassian Status Pages: Which One to Check?
Atlassian runs separate status pages for each product. Here's where to go for each:
Key insight: Jira Software and Jira Service Management share infrastructure but report separately. An outage in one doesn't always affect the other. The Atlassian Access / identity service affects login across all products — check it first when login fails.
Monitor your Jira project tracking independently
Better Stack checks your Jira API endpoints every 30 seconds. Know about Atlassian outages before your sprint planning is disrupted.
Try Better Stack Free →Jira Software Status Components
The Jira Software status page tracks these components:
How to Check Jira Status (Step by Step)
Check jira-software.status.atlassian.com
The official Jira Software status page. Check per-component rows rather than just the banner. Also check status.atlassian.com for shared Atlassian infrastructure issues affecting all products.
Go to Jira Status Page →Query the Atlassian Statuspage API
For programmatic monitoring, the Jira Software status API returns machine-readable JSON.
curl https://jira-software.status.atlassian.com/api/v2/status.json
curl https://jira-software.status.atlassian.com/api/v2/components.jsonTest the Jira REST API
If you use the Jira API, test connectivity with a simple request to your site's REST endpoint.
curl -u user@example.com:API_TOKEN \
https://yoursite.atlassian.net/rest/api/3/myselfCheck Atlassian's Twitter / X
Atlassian posts incident updates on @AtlassianOps and @Jira. Search "Jira down" or "Atlassian down" on Twitter for crowd-sourced reports.
Follow @AtlassianOps →Try incognito mode or a different browser
Browser extensions (especially ad blockers) frequently break Jira's UI. Test in a private/incognito window — if Jira works in incognito, an extension is the cause.
Common Jira Issues and Causes
| Symptom | Likely Cause | First Check |
|---|---|---|
| Can't log in to Jira | Atlassian Access incident or SSO issue | status.atlassian.com → Atlassian Access; check IdP |
| Board not loading issues | Jira Software incident or board filter error | Check status page; check board filter config |
| JQL search returning wrong results | Search index degradation or query syntax | status.atlassian.com → Search; verify JQL query |
| Automation rules not triggering | Jira Automation incident or rule condition | Check Automation component on status page; review rule conditions |
| Email notifications not arriving | Notifications incident or spam filtering | Status page → Notifications; check spam folder |
| API returning 429 | Rate limiting (not an outage) | Add backoff/retry; use Bulk API endpoints |
| Attachments not uploading | Media service incident or file size | Status page → Attachments; check 250MB limit |
| Slow page loads | Performance degradation incident | Status page for "degraded performance"; check browser extensions |
Jira Cloud vs Jira Data Center: Status Differences
Jira Cloud
- Status: jira-software.status.atlassian.com
- Hosted by Atlassian on AWS
- Public status page with incident history
- Atlassian handles all infrastructure
- Auto-updates — always on the latest version
Jira Data Center
- Self-hosted — no public Atlassian status page
- Check your own server/cluster health directly
- Your IT/ops team manages infrastructure
- Check Jira application logs for errors
- Atlassian support for licensing, not infrastructure
Note: Atlassian ended support for Jira Server (self-hosted, single-node) in February 2024. If you're on Jira Server, you should migrate to Cloud or Data Center.
What to Do When Jira Is Down
Immediate Steps
- Confirm at jira-software.status.atlassian.com
- Subscribe to email incident updates
- Work from a local copy of your sprint notes
- Use GitHub Issues or Linear as a temporary fallback
- Notify your team so they know it's platform-wide
Long-Term Resilience
- Export project data periodically via Jira backup
- Set up independent Jira API uptime monitoring
- Document critical sprint goals offline/in Notion
- Add Jira + Atlassian status to team monitoring board
- Consider GitHub Issues as a lighter fallback option
Monitor your Jira instance and API independently
Better Stack monitors your Jira REST API endpoints every 30 seconds. Know about Atlassian outages before your next sprint ceremony is disrupted.
Try Better Stack Free →Frequently Asked Questions
Where is the official Jira status page?
Jira's official status page is at jira-software.status.atlassian.com (for Jira Software specifically) or the broader Atlassian Cloud status page at status.atlassian.com. The Atlassian Cloud status page covers Jira Software, Jira Service Management, Confluence, Bitbucket, Atlassian Access, and Atlas. Atlassian also provides a per-site status check — if your company site is at mycompany.atlassian.net, issues may be site-specific rather than platform-wide.
Why can't I log in to Jira?
Jira login failures have several causes: (1) Atlassian Access / identity service incident — check status.atlassian.com for Atlassian Access, (2) SSO/SAML configuration issue — if your organization uses Okta, Azure AD, or another IdP, verify the IdP is operational, (3) Password change or account suspension — try resetting your password at id.atlassian.com, (4) Browser cookie corruption — clear browser cookies for atlassian.net, (5) Corporate network blocking atlassian.net — test on mobile data. If login works on mobile but not corporate Wi-Fi, your network/firewall is the issue.
Why are Jira issues not loading or boards not showing?
Jira board or issue loading failures are typically caused by: (1) Jira Software platform incident — check status.atlassian.com; (2) Project permission misconfiguration — the user may lack view permissions for the project; (3) Browser extension interference — ad blockers or privacy extensions sometimes break Jira's React frontend; test in incognito mode; (4) Jira project schema or board filter misconfiguration — check the board configuration and verify the filter returns issues; (5) Browser cache — Jira caches aggressively; try Shift+Reload or clear cache.
What is the difference between Jira Software and Jira Service Management status?
Jira Software and Jira Service Management (JSM) are separate Atlassian Cloud products tracked at different URLs. Jira Software is for engineering teams tracking sprints, issues, and roadmaps. JSM is the IT service desk product (formerly Jira Service Desk). They share Atlassian's underlying infrastructure but have their own status pages: jira-software.status.atlassian.com and jira-service-management.status.atlassian.com. An incident in one product does not necessarily affect the other — always check the specific product's status page.
How do I check Jira/Atlassian status programmatically?
Atlassian provides a Statuspage API for all their products. The Jira Software status API is at jira-software.status.atlassian.com/api/v2/status.json and the components endpoint at jira-software.status.atlassian.com/api/v2/components.json. The broader Atlassian Cloud status is at status.atlassian.com/api/v2/status.json. These return standard Atlassian Statuspage JSON with status fields of 'operational', 'degraded_performance', 'partial_outage', or 'major_outage'. You can also use the Atlassian REST API (api.atlassian.com) to check site-level health.
What is the Jira Cloud API rate limit?
Jira Cloud REST API rate limits are based on your Atlassian Cloud plan tier. As of 2025, Atlassian enforces a global rate limit per user token and per app (OAuth). The exact limit varies but is typically around 200-400 requests per minute per token. The API returns HTTP 429 with a Retry-After header. For heavy integrations, use Jira's Bulk API endpoints where available, paginate all list requests, and implement exponential backoff on 429 responses. Atlassian also has a 10,000 result limit per JQL query — use pagination with startAt/maxResults.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Jira goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Jira + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial