Is WeTransfer Down?

No — WeTransfer is up

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

Right now

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

WeTransfer's status page

status.wetransfer.com · read 3 minutes ago · checked every 3 minutes

Operational

WeTransfer's components, as its status page reports them
Component	Status
Website	Operational
Downloads	Operational
Uploads	Operational
Email	Operational
Transfer Mobile	Operational
Previews	Operational
Support	Operational

Open their status page

FlareWarden checks

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

Reachable

Regions up: 8 of 8
Response: 305 ms
Checked: 5 hours ago

By region

Ashburn reachable, 221 ms
Chicago reachable, 328 ms
Frankfurt reachable, 172 ms
Johannesburg reachable, 548 ms
London reachable, 108 ms
Los Angeles reachable, 224 ms
São Paulo reachable, 407 ms
Tokyo reachable, 436 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	71 ms	2 ms	3 ms	220 ms
Chicago	208 ms	1 ms	3 ms	327 ms
Frankfurt	103 ms	2 ms	7 ms	169 ms
Johannesburg	126 ms	1 ms	4 ms	368 ms
London	32 ms	3 ms	5 ms	99 ms
Los Angeles	42 ms	2 ms	5 ms	221 ms
São Paulo	180 ms	1 ms	4 ms	406 ms
Tokyo	155 ms	2 ms	4 ms	434 ms

We check that wetransfer.com loads, not every feature behind it. Test it yourself

History

Incidents WeTransfer reported

Since Oct 22, 15 days · from status.wetransfer.com

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

No incidents reported in this window.

WeTransfer website availability

Measured by FlareWarden · wetransfer.com

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

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

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

What WeTransfer does

WeTransfer moves large files between people without requiring an account, by uploading them once and emailing the recipient a download link. Designers, video editors and agencies use it to hand off work too big for email attachments, which means an outage tends to land in the middle of a delivery deadline rather than at a convenient moment.

What an outage looks like

Uploads stall partway and restart from the beginning, or the site refuses the file outright. Recipients opening an existing link get an error, or a download that stops mid-transfer. The notification email announcing a transfer never arrives, so the recipient does not learn anything was sent. Previews fail to render while downloads themselves still work.

What to do about it

Check status.wetransfer.com, which reports Uploads, Downloads, Email and Previews as separate components, so a failing upload does not mean existing links are dead. Send the recipient the transfer link directly if the notification email has not arrived, since Email and Downloads are tracked independently. Hold off restarting a large upload until Uploads is healthy.

Is it down for everyone, or just you?

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

Figma

Cloudflare

AWS

SoundCloud

WeTransfer outage FAQ

Is WeTransfer down or is my file too large?

A size limit gives an explicit message naming the limit for your plan, while an outage gives timeouts, stalled progress bars or a generic failure. Check status.wetransfer.com to separate them. If Uploads is green and a smaller test file transfers successfully, the problem is the file or your connection rather than the service.

Do my existing transfer links still work during an outage?

Often yes. Uploads and Downloads are separate status components, so new transfers can fail while links already created keep serving. The reverse also happens. If a recipient reports a broken link while your uploads work fine, check the Downloads component rather than assuming the transfer itself was corrupted or never completed.

The recipient never got the email. Was the transfer lost?

Not necessarily. Email is tracked as its own component, so a transfer can upload and store correctly while the notification fails to send. The link works independently of the email that announces it. Copy the transfer link from your own screen or transfer history and send it directly rather than re-uploading the files.

Should I restart a stalled WeTransfer upload?

Not while Uploads is reported unhealthy. A restarted large upload begins again from the start, consuming time and bandwidth on a service that cannot currently accept it, and repeated attempts add load to a recovering system. Wait for the status page to clear, then start once. Keep the source files untouched until the recipient confirms delivery.

How long do transfers stay available after an outage?

Expiry is counted from when the transfer was created, and an outage does not extend it. A transfer that spent part of its life undownloadable still expires on its original schedule, so a link created just before an incident may have less usable time left than expected. Re-send if the window has closed.

How we measure this

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

We check WeTransfer 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