Is MASV Down?

No — MASV is up

MASV's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 222 ms

Right now

The verdict is the worse of these two. How we decide

MASV's status page

masv.statuspage.io · read 4 minutes ago · checked every 3 minutes

Operational

MASV's components, as its status page reports them
Component	Status
MASV API and Services	Operational
MASV Delivery Network	Operational
US East	Operational
US West	Operational
Admin Console Pages	Operational
Admin Console CDN	Operational
Admin Console Network	Operational

6 locations All operational

Open their status page

FlareWarden checks

masv.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 222 ms
Checked: 1 hour ago

By region

Chicago reachable, 158 ms
London reachable, 184 ms
Los Angeles reachable, 247 ms
San Jose reachable, 210 ms
Singapore reachable, 116 ms
Sydney reachable, 223 ms
Tokyo reachable, 331 ms
Toronto reachable, 307 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Chicago	26 ms	2 ms	10 ms	109 ms
London	41 ms	28 ms	19 ms	174 ms
Los Angeles	188 ms	2 ms	11 ms	239 ms
San Jose	94 ms	2 ms	12 ms	191 ms
Singapore	17 ms	2 ms	11 ms	106 ms
Sydney	125 ms	1 ms	8 ms	216 ms
Tokyo	116 ms	1 ms	11 ms	316 ms
Toronto	56 ms	1 ms	15 ms	200 ms

We check that masv.io loads, not every feature behind it. Test it yourself

History

Incidents MASV reported

Since Oct 22, 15 days · from masv.statuspage.io

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

MASV website availability

Measured by FlareWarden · masv.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 244ms

Last 30 days

73-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of masv.io from multiple regions every 6 hours. MASV's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 73 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What MASV does

MASV moves very large files between people and cloud storage, over a network the company describes as more than 400 accelerated servers. Post-production studios, broadcasters, newsrooms, drone and geospatial teams and machine-learning groups use it to send footage and datasets that email and ordinary file sharing cannot carry. It connects to S3, Google Cloud, Azure, Backblaze, Wasabi, Frame.io and NAS devices.

What an outage looks like

Uploads stall part-way and do not resume, or refuse to start at all. Download links sent to clients return errors, so a delivery you have already promised does not arrive. Transfers to connected cloud storage never land, leaving a completed upload with nothing at the destination. The web app fails to load, and because delivery is reported per region, a transfer can fail for one recipient while succeeding for another.

What to do about it

Check masv.statuspage.io, which MASV's own documentation names as the place to look for delivery problems. It reports the API and Services, the Delivery Network and the File Storage Network, with per-region rows for US East, US West, London, Mumbai, Sao Paulo, Singapore, Sydney and Tokyo, and splits the web app into pages, CDN and network. You can subscribe there by email, Slack or RSS.

Is it down for everyone, or just you?

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

Test it yourself

Related services

WeTransfer

Frame.io

Box

AWS

MASV outage FAQ

Will my interrupted upload have to start over?

MASV describes auto-resume and retry as built into its transfers, so an interrupted upload is meant to continue rather than restart. During an incident the practical answer is to leave it alone rather than cancelling and re-uploading, since a manual restart discards progress the client may be able to recover. Confirm the file arrived at the destination before deleting your local copy.

Is the problem my region or the whole service?

Check the regional rows. MASV reports US East, US West, London, Mumbai, Sao Paulo, Singapore, Sydney and Tokyo separately, alongside the Delivery Network and the File Storage Network. A transfer routed through one region can fail while a colleague sending from another has no trouble, which is common on international deliveries where sender and recipient are far apart.

My recipient says the download link is broken. Is that an outage?

It may be. The status page separates the Delivery Network from the API and the web app, so links can fail while uploading still works. Before re-sending, check whether the package has passed its expiration date or its access limits, since MASV packages carry expiry and optional password protection that produce a similar-looking failure.

Does a MASV outage affect files already delivered to my cloud storage?

No. Once a transfer has landed in S3, Google Cloud, Azure, Backblaze, Wasabi or a connected NAS, those files are in your own storage and an incident at MASV does not touch them. What is at risk is anything still in flight, and anything sitting in MASV's own temporary storage waiting to be collected within its retention window.

How we measure this

We request MASV'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 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. 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 MASV 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 MASV 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 MASV goes down

We check MASV 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 Monitoring

Free plan available No credit card required