CONFLUENCE

⚪ Your static macros went full amnesiac for a few hours—they looked at your page and said 'who am I?'—but Atlassian's engineering team performed an exorcism and sent them back to work. Service is pretending nothing happened. (Auto-resolved: no updates in 24h)

⏰ Mar 13, 2026 Fixed (for now) spotted via status_rss

// The official story

Static macro rendering is failing in Confluence Cloud

// Status page says

Mar 13 , 00:26 UTC Resolved - On March 12, 2026, affected Confluence Cloud users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers. Mar 12 , 13:38 UTC Identified - Our team has identified the cause of this issue, and a fix is currently being deployed. We are monitoring the deploym

🔗 Official status page (for the PR-approved version)

https://confluence.status.atlassian.com/incidents/9xld4vg1mly0

Confluence's Greatest Hits

🟢 CONFLUENCE Aug 27, 2026

⚪ Jira Cloud, Service Management, and Confluence took an unscheduled geographic vacation across multiple regions. Atlassian's engineers played hide-and-seek with the infrastructure and won. Services are now pretending nothing happened. (Auto-resolved: no updates in 24h)

🟢 CONFLUENCE Jul 06, 2026

🟠 Atlassian's dynamic duo went silent, leaving automation tasks in the void. They're limping back to life now, but any requests that got submitted during the blackout are gone—like emails to your ex, unread and unacknowledged. (Auto-resolved: no updates in 24h)

🟢 CONFLUENCE Jun 12, 2026

🟠 Confluence decided to practice its namesake by flowing absolutely nowhere for 4 hours straight. Users got a masterclass in document inaccessibility. The hamster powering it all has since been replaced with a slightly angrier one. (Auto-resolved: no updates in 24h)

🟢 CONFLUENCE May 08, 2026

🔴 Multiple Atlassian services decided to ghost their users after the cloud provider experienced what engineers are calling 'an infrastructure oopsie.' Confluence, Jira, and friends are all caught in the crossfire while Atlassian plays the blame game with their cloud vendor. (Auto-resolved: no updates in 24h)