Is MASV Down?

No — MASV is up

Reachable from all 8 checked regions

Average response time: 167ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://masv.statuspage.io

MASV uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

239ms

Avg response, 30 days

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

30-day history

48-day clean streak

Sep 12 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

267ms

DNS 129ms TCP 2ms TLS 11ms TTFB 246ms

arn

89ms

DNS 63ms TCP 1ms TLS 6ms TTFB 85ms

nrt

305ms

DNS 184ms TCP 1ms TLS 9ms TTFB 287ms

ord

101ms

DNS 44ms TCP 1ms TLS 9ms TTFB 93ms

sin

129ms

DNS 13ms TCP 1ms TLS 8ms TTFB 122ms

sjc

258ms

DNS 76ms TCP 1ms TLS 9ms TTFB 251ms

syd

34ms

DNS 10ms TCP 1ms TLS 7ms TTFB 29ms

yyz

156ms

DNS 56ms TCP 1ms TLS 12ms TTFB 124ms

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

This page refreshes every 6 hours. 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