Loom
Apps and SaaS. Source: Loom status page.
- Incidents, last 90 days
- 0
- Median to mitigation
- none resolved
- Median to resolution
- none resolved
- p95 to resolution
- none resolved
- Naming an upstream provider
- no incidents
- With a postmortem on the status page
- no incidents
Incidents per month
All recorded incidents
Multiple Atlassian services are experiencing issues
Affected: Recording, Viewing, Authentication, Loom AI
Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.
-
identified
We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
-
identified
Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.
-
identified
We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
-
identified
Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.
-
identified
We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each...
-
monitoring
The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation...
-
monitoring
We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.
-
monitoring
Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We...
-
resolved
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.
-
postmortem
All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded...
Excerpts are shortened. Read the full incident on Loom's status page.
Degraded performance of Loom app
Affected: Recording, Viewing, Authentication, Loom AI
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are investigating degraded performance issues affecting Loom's core functionalities - authentication, recording, viewing and editing looms. We will provide more details within the next hour.
-
resolved
The Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.
Excerpts are shortened. Read the full incident on Loom's status page.
Confluence, Jira Mobile and Forge users may experience authentication issues
Affected: Recording, Viewing, Authentication, Loom AI
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or...
-
investigating
Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or...
-
resolved
Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.
Excerpts are shortened. Read the full incident on Loom's status page.
Some Loom users experiencing no audio when viewing recordings
Affected: Recording, Viewing, Authentication, Loom AI
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
We are aware of some customers that are experiencing no audio when viewing their Loom recordings. Our team has identified this issue and is working urgently to restore the audio for these recordings. Please rest assured that the audio has been recorded correctly, and we expect...
-
identified
Our team believes that we have identified the cause of the issue impacting audio during playback of videos for some customers. As mentioned in our previous updates, new recordings will be working as expected, however videos recorded between 19 Nov 16:51 UTC and 19 Nov 21:30 UTC...
-
identified
The fix to resolve issues on audio recordings impacted by this incident is now being prepared for deployment. Currently the expected duration of the rollout is 3 hours, at which point we expect the audio from the impacted recordings to be fully restored. We will provide further...
-
resolved
The rollout of the fix for impacted videos without audio has now completed. Customers should now be able to review existing videos without audio and see that it has been properly restored. If you are continuing to see any issues with playback of your videos, please reach out to...
Excerpts are shortened. Read the full incident on Loom's status page.
Loom performance degraded
Affected: Recording, Viewing, Authentication, Loom AI
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are investigating an issue with Recording, Loom AI, Authentication, and billing that is impacting some Loom Cloud customers. We will provide more details within the next hour.
-
investigating
We are continuing to investigate the issue with Recording, Loom AI, Authentication, and billing that is impacting some Loom Cloud customers. We are investigating and will post updates at 17:35 UTC or sooner.
-
investigating
We are continuing to investigate the issue with Recording, Loom AI, Authentication, and billing that is impacting some Loom Cloud customers. We will post another update at 18:35 UTC or sooner, as things progress.
-
investigating
We are continuing to actively investigate the issue with Recording, Loom AI, Authentication, and billing that is impacting some Loom Cloud customers. We appreciate your patience. We will post another update at 19:35 UTC or sooner, as things progress.
-
monitoring
We have identified the root cause of the issue with Recording, Loom AI, Authentication, and billing which is impacting some Loom Cloud customers. We have implemented mitigations to address the problem and are now monitoring closely. We will provide another update at 20:00 UTC or...
-
monitoring
We are actively implementing further mitigations to resolve the issue affecting Recording, Loom AI, Authentication, and billing for some Loom Cloud customers. We will continue to monitor closely and provide another update at 21:00 UTC or sooner, as things progress.
-
monitoring
We have implemented further mitigations to resolve the issue affecting Recording, Loom AI, Authentication, and billing for some Loom Cloud customers. We are seeing good signs of recovery and all services are operational. We will continue to monitor closely and provide another...
-
resolved
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...
-
postmortem
### Summary On October 27, 2025 between 12:30 and 20:55 UTC, Loom was significantly degraded for all customers. Users also experienced short periods of degradation on October 28, 2025 from 20:26 to 20:33 UTC and October 30, 2025 19:22 to 19:27 UTC. During the incident, users...
Excerpts are shortened. Read the full incident on Loom's status page.
Atlassian Cloud Services impacted
Affected: Recording, Viewing, Authentication, Loom AI
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
We have noticed that Atlassian Cloud services are impacted and our teams are actively investigating the same. We shall keep you informed of the progress every hour.
-
investigating
Atlassian Cloud services are impacted and we are aware that our customers might not be able to create support tickets. Our teams are actively investigating the same. We shall keep you informed of the progress every hour.
-
investigating
We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not...
-
investigating
We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not...
-
identified
We understand that our public cloud provider has identified the cause of the issue. We are starting to see some recovery and is working towards mitigation. We appreciate your patience. We shall continue to share updates every hour, if not sooner.
-
identified
We continue to work with our public cloud provider towards mitigating the issue at the earliest. We appreciate your patience. We shall continue to share updates every hour, if not sooner.
-
identified
Atlassian team is actively engaged and continues to work with our public cloud provider to mitigate this issue at the earliest. We are starting to see partial operations succeed. We appreciate your patience. We shall continue to share updates every hour, if not sooner.
-
identified
Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.
-
identified
Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.
-
identified
Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.
-
identified
We understand your pain and mitigating or fixing this issue is of utmost importance. Our public cloud provider is actively working to mitigate this issue on priority. We have been seeing partial operational success. We appreciate your patience and will continue to provide...
-
identified
Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...
-
identified
Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...
-
identified
Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and...
-
identified
Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and...
-
identified
Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...
-
identified
We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and...
-
monitoring
There have been no changes since our last update. We will provide our next updated by 9:00PM UTC or sooner as new information becomes available. We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS....
-
monitoring
Monitoring - We've started seeing continued product experience improvement. While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and...
-
monitoring
Our teams are continuing to monitor the recovery of systems across Atlassian products. This update is to inform that the Atlassian Support portal is fully operational at this time for customers that wish to contact support.
-
monitoring
Our team is now seeing recovery across all impacted Atlassian products. We are continuing to monitor for individual products that may still be processing backlogged items now that services are restored. The Atlassian Support portal is currently still displaying a message...
-
monitoring
We continue to see recovery progressing across all impacted products as backlogged items continue to be processed. The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is...
-
monitoring
The issue relating to the Atlassian Support portal displaying a message to customers to use our temporary support channel has now been resolved. The Atlassian Support portal is fully functional for any ongoing support issues. With regards to other Atlassian products, we continue...
-
resolved
Our team is now able to see full recovery across the vast majority of Atlassian products. We are aware of some ongoing issues with specific components such as migrations and JSM virtual service agents, and our team is continuing to investigate with urgency. We apologise for the...
-
postmortem
### Postmortem publish date: Nov 19th, 2025 ### Summary All dates and times below are in UTC unless stated otherwise. Customers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service...
Excerpts are shortened. Read the full incident on Loom's status page.
Issue with Loom Meeting Recordings in Zoom
Affected: Recording
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
monitoring
From 5:03 AM ET to 4:15 PM ET, some customers were unable to record Zoom meetings using Loom Meeting Recordings. Attempts made during this time may appear in your library but will not be playable, as no recording was captured. Unfortunately, these recordings cannot be recovered....
-
resolved
The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Loom's status page.
Issues with Recording on Loom Chrome Extension
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
resolved
From 5:20AM to 3:45PM UTC today some customers using the Loom Chrome Extension experienced issues with recording. Looms recorded during this time may show up in the library but will not be playable. Unfortunately we are unable to recover these videos. If you are still...
Excerpts are shortened. Read the full incident on Loom's status page.
Loom Intermittent Issues
Affected: Recording, Viewing, Authentication, Loom AI
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
We are investigating reports of issues for Loom customers. Including names showing as IDs. We will provide more details once we identify the cause.
-
monitoring
We have identified the cause of the issues and we are monitoring recovery.
-
resolved
Between 18:45 and 19:35 UTC we experienced degraded functionality for Loom. The issue has been resolved and the service is operating normally.
Excerpts are shortened. Read the full incident on Loom's status page.
Customers unable to checkout with loom monthly plans
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
Customers are unable to choose a monthly plan when upgrading or purchasing from loom.com. We are investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results
-
resolved
This issue is now resolved and customers can checkout as expected.
Excerpts are shortened. Read the full incident on Loom's status page.