Skip to main content

Is Frame.io Down?

No — Frame.io is up

Reachable from all 8 checked regions

Average response time: 481ms

Last checked · checks run every 6 hours

Official status page: https://status.frame.io

Frame.io uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
355ms
Avg response, 30 days

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

30-day history

18-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: 100.00% uptime, 16 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 40 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 27 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 40 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 36 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
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.

ewr
187ms
DNS 0ms TCP 1ms TLS 19ms TTFB 172ms
fra
265ms
DNS 0ms TCP 1ms TLS 8ms TTFB 207ms
gru
336ms
DNS 0ms TCP 3ms TLS 11ms TTFB 299ms
iad
368ms
DNS 0ms TCP 2ms TLS 8ms TTFB 342ms
jnb
1649ms
DNS 0ms TCP 0ms TLS 48ms TTFB 1604ms
lax
189ms
DNS 0ms TCP 1ms TLS 25ms TTFB 167ms
lhr
358ms
DNS 0ms TCP 2ms TLS 8ms TTFB 344ms
nrt
479ms
DNS 0ms TCP 1ms TLS 10ms TTFB 464ms
ord
206ms
DNS 0ms TCP 2ms TLS 27ms TTFB 164ms

What Frame.io does

Frame.io is a video review and collaboration service owned by Adobe. Editors upload cuts and clients leave frame-accurate comments and drawings against the timeline. It generates the proxies and thumbnails that make large media reviewable in a browser, and it connects to Premiere Pro and After Effects so notes appear inside the editing application rather than in a separate document.

What an outage looks like

Uploads complete but the asset sits without a thumbnail, because media processing is a separate stage from storage. Playback fails or stalls on a black frame while comments still post. Share links sent to clients return errors, and the Premiere Pro and After Effects panels stop syncing. Incidents on 28 July 2026 hit thumbnail generation on uploaded proxies and collection viewing while the rest of the application worked.

What to do about it

Check status.frame.io, which reports next.frame.io for V4 and app.frame.io for the legacy application as separate components, alongside Media Processing and the Developer Platform. Confirm which version your account is on, because one can be degraded while the other serves normally. An asset that uploaded but has not processed will generally finish once Media Processing recovers, so wait before re-uploading a large file over a slow connection.

Is it down for everyone, or just you?

If this page says Frame.io 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

A
Adobe Creative Cloud
V
Vimeo
Figma
Figma
L
Loom

Frame.io outage FAQ

Is it Frame.io or did my upload fail?
Check whether the asset appears in the project at all. If it is listed but stuck without a thumbnail, the file reached Frame.io and Media Processing has not finished with it, which is a server-side stage that completes on its own once the component recovers. If the asset never appears, the upload itself failed and needs restarting. The status page separates Media Processing from the applications for exactly this distinction.
Does an outage affect V4 and the legacy app the same way?
Not necessarily. The status page lists next.frame.io (V4) and app.frame.io (LEGACY) as separate components, so an incident can take out one while the other serves normally. Accounts have been moving between the two, which means two people on the same team can see different behaviour during the same incident. Establish which one you are on before concluding the platform is down.
Will my client's comments be lost?
Comments that posted successfully are stored, and recent incidents have affected playback and media processing rather than comment storage. The risk is a comment typed while the connection was failing that was never acknowledged. Ask reviewers to reload and confirm their notes appear before closing the tab, because a note that never reached the server leaves no local copy to recover afterwards.
Do the Premiere Pro and After Effects panels work when the site is down?
No. The panels are clients for the same service, so they read and write through the same infrastructure the browser uses and typically show a stale comment list or fail to connect. Media already on your machine stays editable and only the review layer stops, so an edit session can continue. Adobe Creative Cloud sign-in is a separate service with its own status page.
Does an Adobe outage take Frame.io down?
Not automatically. Adobe owns Frame.io, but it reports separately at status.frame.io rather than on status.adobe.com, and the two can disagree. Sign-in is the shared point worth checking: an Adobe identity problem can stop you reaching Frame.io while Frame.io itself is healthy. Read both pages when access fails but the service reports every component operational.

How we measure this

  • We request Frame.io'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 Frame.io 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 Frame.io 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