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.
State
Resolved
Started
370 d ago
2025-10-27 22:00 UTC
Ongoing for
370 days
Worst impact
Partial outage
Timeline
1 updateResolved
370 days 100%
Updates
Times in UTCAs posted by Loom
On Oct 27, 2025, between 12:30 and 22:15 UTC, we experienced degraded performance affecting Recording, Loom AI, Authentication, and Billing services for some Loom customers. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the issue have been addressed and we're actively working on a permanent fix. The issue has been resolved and the service is operating normally. Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking to prevent this from happening again in the future. Note: As a result of this incident, some Looms recorded during the period of degraded performance may have remained in an "uploading" state. These videos are not recoverable, and have been Archived from users' libraries.
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