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 Confluence is down?

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

How many people have reported Confluence issues today?

As of Oct 12, 2026 20:16 UTC, 0 users had reported issues with Confluence in the previous 24 hours.

How can I report a Confluence 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 Confluence down right now?

NormalOfficial status last polled Oct 12, 2026 19:48 UTCatlassian.com/software/confluence Official status page

Atlassian Confluence team wiki

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

Is Confluence down right now?

No. Confluence 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 20:16 UTC

Normal

Confluence is operating normally

As of Oct 12, 2026 20:16 UTC

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

Reports 24h

Last incident

Oct 1, 2026 09:15 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 Confluence.

Incident days

No recorded incident

6h 25m

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 Confluence. 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

1 incident

Busiest day

6h 25m

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

Confluence: vendor-reported major incident on October 1 (tracked 6h 0m)

Oct 1, 03:15 AM → Oct 1, 09:15 AM · 6h 0m · high

Confluence reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 6h 0m, from Thu, 01 Oct 2026 03:15:42 GMT to Thu, 01 Oct 2026 09:15:45 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration

6h 0m

tracked by PulseWatch

Impact

During the 6-hour incident, Confluence experienced a high-severity disruption. This incident was identified through automated monitoring and the vendor's status page. No user-reported data was collected for this event, therefore specific user-visible impacts such as affected features or regions were not recorded.

Incident timeline

Oct 1, 03:15 AM
The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it
Oct 1, 03:15 AM
Status updated: possible issue
Oct 1, 09:15 AM
PulseWatch closed the incident

Official updates

Oct 1, 03:15 AM
Confluence reported the incident on its status page.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.11%

90-day uptime

99.33%

Calculated from Confluence'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.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedHigh

Confluence: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Confluence or have an alert rule on it can be alerted, labelled vendor-reported.

10/1/2026, 3:15:42 AM · 6h 0m

03:15 AM09:15 AM

Detection10/1/2026, 3:15:42 AM · 11d ago

Detected — high severity

ResolvedLow

Server errors measured by PulseWatch checks. Detected by PulseWatch from its own measurements across 2 consecutive 15-minute windows; the vendor's status page reported no issues at detection time.

9/23/2026, 8:32:00 PM · 24 min

08:32 PM08:57 PM

Detection9/23/2026, 8:32:00 PM · 18d ago

Detected — low severity

Server errors measured by PulseWatch checks. Detected by PulseWatch from its own measurements across 2 consecutive 15-minute windows; the vendor's status page reported no issues at detection time.

ResolvedMedium