Multiple Atlassian services are experiencing issues
Loom Recording, Viewing, Authentication, and Loom AI had degraded performance for some customers using Atlassian products. Loom reports that the issue is resolved.
State
Resolved
Started
178 d ago
2026-05-08 03:00 UTC
Ongoing for
178 days
Worst impact
Degraded
Timeline
1 updateResolved
178 days 100%
Updates
Times in UTCAs posted by Loom
On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.
Affected components
4Follow Loom
Your coding agent knows when Loom is down, and tells you when a failure is theirs, not yours. You can also get Loom incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "loom" and tell me if Loom has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=loom/feed subscribe https://outages.cc/feed.xml?providers=loomFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane