Loom performance degraded
Loom reported degraded performance for Recording, Viewing, Authentication, and Loom AI. Loom says the incident is resolved after about 9 hours and 45 minutes. Loom also says some videos recorded during the incident stayed in an uploading state and are not recoverable.
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
4Loom in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
90
Median duration
Not enough data
This incident
Not comparable
Other Loom incidents
All incidentsLoom·Multiple Atlassian services are experiencing issues
Loom reports that Recording, Viewing, Authentication, and Loom AI had degraded performance for some customers who use Atlassian products. Loom states that the issue is resolved and that the service operates normally for all affected customers. Loom did not give the duration.
Loom·Degraded performance of Loom app
Loom reports degraded performance in Recording, Viewing, Authentication, and Loom AI. Loom identified the root cause and resolved the issue. The affected services operate normally again.
Loom·Confluence, Jira Mobile and Forge users may experience authentication issues
Loom reports that authentication issues affected Recording, Viewing, Authentication, and Loom AI. Loom states that the root cause was identified and the issue is resolved. The impacted services operate normally now. Loom continues to monitor the services.
Loom·Some Loom users experiencing no audio when viewing recordings
Loom reports that some users cannot hear audio when they view recordings. The components affected are Recording, Viewing, Authentication, and Loom AI. Loom says the incident is resolved and the fix rollout is complete.
Loom·Atlassian Cloud Services impacted
Loom reports that Recording, Viewing, Authentication, and Loom AI do not work. Loom reports that the incident is resolved.
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.live/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.live/feed.xml?providers=loom/feed subscribe https://outages.live/feed.xml?providers=loomFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane