Loom
Loom is operational
Some Loom users experiencing no audio when viewing recordings
Loom users cannot hear audio when they view some recordings. The affected components are Recording, Viewing, Authentication, and Loom AI. Loom reports that the incident is resolved, and the fix rollout is complete.
Loom performance degraded
Loom reported degraded performance. Recording, Viewing, Authentication, and Loom AI were affected for some customers. Loom stated the incident is resolved. The degraded performance lasted from 12:30 to 22:15 UTC on Oct 27, 2025. Loom deployed a fix and verified recovery.
Issue with Loom Meeting Recordings in Zoom
Loom Meeting Recordings in Zoom do not work for the Recording component. Loom reports that the issue is resolved and the service operates normally. Loom did not give the outage duration.
Loom Intermittent Issues
Loom had degraded functionality for Recording, Viewing, Authentication, and Loom AI. The issue lasted from 18:45 to 19:35 UTC. Loom reports that the issue is resolved and the service operates normally.
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.
Degraded performance of Loom app
Loom reported degraded performance in the Loom app. The affected components were Recording, Viewing, Authentication, and Loom AI. Loom says the problem is resolved and the services operate normally.
Confluence, Jira Mobile and Forge users may experience authentication issues
Loom users had authentication problems that affected Recording, Viewing, Authentication, and Loom AI. Loom reports that the issue is resolved and the services work normally. Loom will monitor the services.
Atlassian Cloud Services impacted
Loom reports that Recording, Viewing, Authentication, and Loom AI do not work. Loom later reported full recovery for most Atlassian products. The incident is resolved, but the provider did not state how long it lasted.
Issues with Recording on Loom Chrome Extension
Recording on the Loom Chrome Extension did not work for some customers from 5:20AM to 3:45PM UTC. Loom recorded videos from this period may appear in the library but will not play, and Loom cannot recover them. The issue is resolved; Loom asks users who still see the problem to record with extension version 5.5.121.
Customers unable to checkout with loom monthly plans
Loom customers could not check out with Loom monthly plans. Loom reports that the issue is resolved and that customers can check out as expected. Loom did not state how long the issue lasted.
History
Incidents in 90 days
10
Days with an incident
90
Median duration
No data
Longest incident
No data
Components
4No incident in the last 90 days.
Follow 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=loomGo from tracking outages to fixing production issues with Polylane.
Try Polylane