Unrated
monitoring
since
Degraded software performance iOS
We've identified and have a fix for an issue affecting Reviewers added to Shares on the latest build for iOS.
Latest update 8 hours ago
Is Frame.io Down?
Partially — Frame.io is degraded
- Frame.io's status page
- Open incident · unrated incident (“Degraded software performance iOS”)
- FlareWarden checks
- Website reachable · 8 of 8 regions · 558 ms
Right now
The verdict is the worse of these two. How we decide
Frame.io's status page
status.frame.io · read · checked every 3 minutes
| Component | Status |
|---|---|
| next.frame.io (V4) | Operational |
| Developer Platform | Operational |
| Media Processing | Operational |
| blog.frame.io | Operational |
| support.frame.io | Operational |
| iOS | Operational |
FlareWarden checks
frame.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 558 ms
- Checked
By region
- Ashburn reachable, 250 ms
- Dallas reachable, 296 ms
- Frankfurt reachable, 361 ms
- Johannesburg reachable, 1919 ms
- London reachable, 286 ms
- Los Angeles reachable, 163 ms
- Newark reachable, 393 ms
- São Paulo reachable, 802 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 81 ms | 1 ms | 8 ms | 211 ms |
| Dallas | 33 ms | 1 ms | 58 ms | 242 ms |
| Frankfurt | 124 ms | 1 ms | 8 ms | 347 ms |
| Johannesburg | 206 ms | 0 ms | 74 ms | 1846 ms |
| London | 13 ms | 1 ms | 5 ms | 276 ms |
| Los Angeles | 10 ms | 1 ms | 25 ms | 140 ms |
| Newark | 127 ms | 4 ms | 16 ms | 308 ms |
| São Paulo | 467 ms | 1 ms | 6 ms | 780 ms |
We check that frame.io loads, not every feature behind it.
Test it yourself
History
Incidents Frame.io reported
Since Oct 22, 3 days · from status.frame.io
- Incidents
- 1
- Major or critical
- 0
- Median to resolve
- —
- Ongoing
Degraded software performance iOS
Unrated ·
Frame.io website availability
Measured by FlareWarden · frame.io
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 455ms
Last 30 days
80-day clean streakSep 25
Today
No downtime
Partial
Downtime
Not measurable
No data
Measured by FlareWarden's own checks of frame.io from multiple regions every 6 hours. Frame.io's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 80 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
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 up to 17 cities across three regions to find out where it breaks.
Related services
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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Frame.io itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Frame.io goes down
We check Frame.io every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free MonitoringFree plan available
No credit card required