We started checking Loom on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Loom reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Loom's own status page declared. Below it, any public chatter we saw about Loom and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Loom's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Loom in the last 24 hours, which is not evidence that nothing is wrong.
Loom's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Loom's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Loom next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
Bluesky posts2 in the last hour (prior day averaged 0.1/hour)
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
431
US-West
99.70%
332
Europe
100.00%
303
Asia-Pacific
100.00%
186
Their declared record
Loom's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Multiple Atlassian services are experiencing issuesMinor incident
May 8, 2026, 3:00 AM UTC to May 8, 2026, 7:45 PM UTC (16h 45m)postmortem published
their latest update (May 20, 2026, 6:57 AM UTC): 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 per…
Degraded performance of Loom appMinor incident
Apr 29, 2026, 7:00 AM UTC to Apr 29, 2026, 7:50 AM UTC (50 min)resolved
their latest update (Apr 29, 2026, 7:50 AM UTC): 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.
Confluence, Jira Mobile and Forge users may experience authentication issuesMinor incident
Feb 3, 2026, 10:19 AM UTC to Feb 3, 2026, 10:50 AM UTC (31 min)resolved
their latest update (Feb 3, 2026, 10:50 AM UTC): 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.
Some Loom users experiencing no audio when viewing recordingsPartial outage
Nov 19, 2025, 10:32 PM UTC to Nov 20, 2025, 5:39 AM UTC (7h 7m)resolved
their latest update (Nov 20, 2025, 5:39 AM UTC): 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 t…
Loom performance degradedPartial outage
Oct 27, 2025, 10:00 PM UTC to Oct 27, 2025, 10:00 PM UTC (0 min)postmortem published
their latest update (Nov 21, 2025, 7:49 PM UTC): ### 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 ex…
Atlassian Cloud Services impactedAll systems operational
Oct 20, 2025, 7:56 AM UTC to Oct 21, 2025, 5:24 AM UTC (21h 28m)postmortem published
their latest update (Oct 24, 2025, 5:53 PM UTC): ### 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…
Issue with Loom Meeting Recordings in ZoomPartial outage
Sep 12, 2025, 8:43 PM UTC to Sep 12, 2025, 10:14 PM UTC (1h 31m)resolved
their latest update (Sep 12, 2025, 10:14 PM UTC): The issue has been resolved and the service is operating normally.
Issues with Recording on Loom Chrome ExtensionAll systems operational
Sep 8, 2025, 9:46 PM UTC to Sep 8, 2025, 9:46 PM UTC (0 min)resolved
their latest update (Sep 8, 2025, 9:46 PM UTC): 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 experiencin…
Loom Intermittent IssuesPartial outage
Aug 15, 2025, 7:35 PM UTC to Aug 15, 2025, 7:58 PM UTC (24 min)resolved
their latest update (Aug 15, 2025, 7:58 PM UTC): Between 18:45 and 19:35 UTC we experienced degraded functionality for Loom. The issue has been resolved and the service is operating normally.
Customers unable to checkout with loom monthly plansAll systems operational
Apr 14, 2025, 7:07 PM UTC to Apr 14, 2025, 7:34 PM UTC (27 min)resolved
their latest update (Apr 14, 2025, 7:34 PM UTC): This issue is now resolved and customers can checkout as expected.
These entries are Loom's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Loom's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.