PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Jira is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Jira. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Jira issues today?

As of Oct 12, 2026 21:39 UTC, 0 users had reported issues with Jira in the previous 24 hours.

How can I report a Jira outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is Jira down right now?

NormalOfficial status last polled Oct 12, 2026 21:38 UTCwww.atlassian.com/software/jira Official status page

Atlassian Jira issue and project tracking

Are you on the Jira team and see something inaccurate? Report it to us. We respond within one business day.

Is Jira down right now?

No. Jira has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 21:39 UTC

Normal

Jira is operating normally

As of Oct 12, 2026 21:39 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 1, 2026 21:37 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unavailable

Current measurements are not available for a health score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Jira.

Incident days

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Jira. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Jira outage on May 4 — 19-minute disruption

May 4, 04:13 AM → May 4, 04:33 AM · 19 minutes · medium

On May 4, 2026, an outage affecting Jira was detected through user reports. The disruption began at approximately 04:13 UTC and was resolved by 04:33 UTC. This resulted in a 19-minute period of service unavailability.

Duration

19 minutes

tracked by PulseWatch

Impact

Users experienced a disruption to Jira services. While specific features or regions were not broadly identified in reports, a peak of 4 user reports were observed within a 15-minute window. No specific issue types or impacted regions were recorded from these reports. The service disruption was detected through these user reports.

Incident timeline

May 4, 04:13 AM
PulseWatch detected elevated report volume (medium severity)
May 4, 04:15 AM
Peak of 0 reports in 15 minutes (baseline 1.3)
May 4, 04:33 AM
Report volume returned to baseline — incident resolved

Official updates

May 4, 04:13 AM
Jira status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.99%

90-day uptime

99.13%

Calculated from Jira's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.