← Back to the carnage
CONFLUENCE

πŸ”΄ Confluence, Jira, and Rovo Chat all lost their ability to find anything. Turns out the search feature took the 'ignore everything' approach to problem-solving. Downstream services are now experiencing existential crises. (Auto-resolved: no updates in 24h)

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

// The official story

Multiple products impacted by search failures

// Status page says

Apr 8 , 06:01 UTC Update - The impact of this incident is now understood to also be impacting search in Jira and Confluence, as well as additional downstream impacts to Rovo Chat, User Management, Administration and Guard. Our team is continuing to investigate with urgency and we will provide further update within 1 hour. Apr 8 , 06:01 UTC Update - Our team is

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

https://confluence.status.atlassian.com/incidents/7g63c08d951j

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)