← Back to the carnage
CONFLUENCE

🟑 Confluence's Rovo agents decided to ghost their automation rules, turning "set and forget" into "set and wonder where it went." Atlassian is now playing detective while your workflows contemplate early retirement. (Auto-resolved: no updates in 24h)

⏰ Apr 14, 2026 Fixed (for now) spotted via status_rss

// The official story

Disrupted Rovo availability for Automation rules

// Status page says

Apr 14 , 12:25 UTC Update - We have identified that this incident also affects automation rules in Confluence that use Rovo agents. We are investigating and will provide updates as we learn more. Apr 14 , 12:25 UTC Investigating - We are actively investigating reports of a partial service disruption affecting Rovo, specifically for customers using automation rules that inv

πŸ”— Official status page (for the PR-approved version)

https://confluence.status.atlassian.com/incidents/4fwvl5sdyz7m

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)