Is Loom Down?

No — Loom is up

Reachable from all 8 checked regions

Average response time: 72ms

Last checked just now · checks run every 6 hours

Official status page: https://status.loom.com

Loom uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

72ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

99ms

DNS 0ms TCP 0ms TLS 2ms TTFB 52ms

arn

35ms

DNS 0ms TCP 0ms TLS 3ms TTFB 29ms

bom

53ms

DNS 1ms TCP 2ms TLS 6ms TTFB 45ms

cdg

39ms

DNS 0ms TCP 1ms TLS 5ms TTFB 34ms

dfw

127ms

DNS 1ms TCP 1ms TLS 3ms TTFB 102ms

ewr

85ms

DNS 0ms TCP 0ms TLS 3ms TTFB 77ms

fra

51ms

DNS 0ms TCP 2ms TLS 4ms TTFB 46ms

syd

31ms

DNS 0ms TCP 0ms TLS 2ms TTFB 28ms

yyz

90ms

DNS 0ms TCP 8ms TLS 11ms TTFB 63ms

What Loom does

Loom records your screen and camera and turns the result into a shareable link, used for async standups, bug reports, customer walkthroughs and handover notes. It is now an Atlassian product and runs on Atlassian's status infrastructure. Teams that replaced meetings with Loom links experience an outage as a communication gap rather than a broken feature.

What an outage looks like

Recording fails to start, or a finished recording sits on processing and never produces a link. Existing Loom links open to a player that spins or shows a playback error, so videos you shared previously stop working for the people you sent them to. Sign-in fails in the desktop app and the browser extension. Loom AI summaries and transcripts stop generating.

What to do about it

Check status.loom.com, which redirects to Loom's page on Atlassian's status site and reports Recording, Viewing, Authentication and Loom AI as four separate components. Viewing failing while Recording stays green means the links you already shared are broken but new captures still work, which changes what you tell the people waiting on them. Keep an unsent recording in the app rather than deleting it and starting again.

Is it down for everyone, or just you?

If this page says Loom is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Loom outage FAQ

Is Loom down, or is it just my browser extension?

Check the Authentication and Recording components on status.loom.com before reinstalling anything. Extension problems usually affect only capture while playback of existing links keeps working, whereas a Loom incident tends to show on one of the four named components. Reinstalling the extension mid-incident wastes time and can lose a local recording that had not finished uploading.

Do Loom links I already shared stop working during an outage?

They can, because Viewing is tracked separately from Recording. An incident confined to Viewing means every link you have ever sent returns a player error for your audience while you can still record new videos perfectly well. If you shared a Loom with a customer or candidate and playback is failing, tell them rather than waiting, since nothing about the link looks broken from their side.

Will a recording I made during the outage be lost?

Not necessarily, but do not force the issue. A recording captured locally that has not finished uploading still exists in the app, and deleting it to re-record is how people actually lose the take. Leave it alone until Recording shows healthy on the status page. Re-recording a long walkthrough costs more than waiting out most incidents.

Is Loom part of Atlassian, and does that matter during an outage?

Yes, Atlassian owns Loom, which is why status.loom.com redirects to Loom's page on Atlassian's status site. It matters mainly for where you look: Loom has its own components rather than being folded into Jira or Confluence, so an Atlassian incident elsewhere does not imply a Loom one, and a Loom incident will not appear on the Jira status page.

How we measure this

We request Loom's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Loom publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Loom goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required