Is Jira (Atlassian) down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

Run the live check at the top of this page - it tests jira.atlassian.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Jira (Atlassian) is reachable for everyone or only failing for you.

Run the live check at the top of this page - it tests jira.atlassian.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Jira (Atlassian) is reachable for everyone or only failing for you.

Run the live check at the top of this page - it tests jira.atlassian.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Jira (Atlassian) is reachable for everyone or only failing for you.

Only if it's a genuine Atlassian Cloud incident. Every organisation runs Jira on its own *.atlassian.net subdomain, and these tenant sites share Atlassian's underlying Cloud infrastructure, so a platform-wide incident does take down every tenant at once - that's the pattern to watch for. A problem affecting only your team, while colleagues at other companies report Jira working fine, points instead at something local to your instance rather than Atlassian's servers.

Login failures are frequently an identity-service problem rather than a Jira-specific one. Atlassian centralises sign-in through id.atlassian.com across its whole product suite, so an incident there blocks access to Jira, Confluence and everything else at once, even though the applications themselves are running normally behind that gate. If you can't sign in but Jira's own status looks fine, the identity layer is the more likely place to look.

Not usually a full outage, but it can be a real incident of a narrower kind. Automation rules run through their own processing queue, and a backlog there delays triggers - a status change that should have notified someone, a field that should have updated - without the rest of Jira becoming unreachable. The site stays usable while automations lag behind, a distinct symptom from Jira itself being down, and it typically resolves once the backlog clears.

Not from Atlassian's side, even though it can feel exactly like an outage to your team. Marketplace apps are third-party additions that plug into Jira, and a broken update, an expired license or a bug in the app itself can disable a feature your workflow depends on while the core Jira platform underneath keeps working fine. Disabling the app, or checking its own support channel, is the right next step; a platform-wide Jira check won't show a problem because there isn't one at that layer.