Downrightnow
// Incident Post-MortemDRN-48658722

Atlassian outage on April 30, 2025

Major severityResolved45 minDeveloper Tools
Started · UTC
Apr 30, 06:43 AM
444d ago
Resolved · UTC
Apr 30, 07:28 AM
444d ago
Duration
45 min
End-to-end
Peak confidence
80.00
0 snapshots
// User impact

Atlassian users likely saw failed connections, degraded availability, or session instability for this Developer Tools service. The incident reached Major severity and lasted 45 min. The stored report window does not show a preserved user-report spike.

// What happened

Apr 30, 06:43 UTCCompleted - okie dokie, RDSs have been upgraded as quickly as expected, nothing related seems to have exploded in the time since, so i think we're in the clear, yayApr 30, 06:31 UTCUpdate - update: from the AWS console for commercial production:- April 30, 2025, 16:09 (UTC+10:00) Multi-AZ instance failover completed- April 30, 2025, 16:09 (UTC+10:00) The RDS instance was modified by customer.- April 30, 2025, 16:08 (UTC+10:00) DB instance restarted- April 30, 2025, 16:08 (UTC+10:00) The parameter max_wal_senders was set to a value incompatible with replication. It has bee

Deterministic readout · awaiting AI summary pass

// Timeline

  1. Incident detected

    Major confidence crossed the incident threshold for MICROSCORE-4348 Micros API outage to upgrade RDSs from db.t4g.large to db.m8g.large.

  2. Marked resolved

    The incident was closed after 45 min of observed impact.

// Signals by source0 sources

No per-source signal payloads were preserved in this incident's snapshot window.

// Aggregate evidence

Confidence scoring

80.00

The incident reached 80.00 peak confidence across available stored status snapshots.

User reports

0 / 15m

No elevated user-report volume was preserved in the incident window snapshots.

Status samples

0 affected

The incident row exists, but the bounded snapshot window does not include affected status samples.

Recovery signal

Resolved

Recovery was recorded at Wed, Apr 30, 2025, 07:28 AM UTC.