Is we.tl down or not working?

What happened to we.tl, why did the website go down and not work? Here you can see who else is having the same problem with we.tl, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, we.tl is working fine, but single failures are possible. If we.tl does not work for you, then report your problem and write a comment.

Add comment

What to do if the site we.tl is not available? Try our guide.

we.tl outage reports in the last 24 hours

we.tl - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.

No registration required.
Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
Active links in the text of the message are not published, but displayed in plain text.
It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Your name:

Message:

Technical information

Main page title:

WeTransfer | Send Large Files Fast - Up To 2GB Free

Main page description:

The simple, quick and secure way to send your files around the world without an account. Share your files, photos, and videos today for free.

Protocol:

https

Status code:

200

Page size:

10.3 KB

Response time:

0.300sec.

IP:

65.9.95.115

Response headers:

content-type:	text/html; charset=utf-8
content-length:	10531
connection:	close
cache-control:	private, no-cache, no-store, max-age=0, must-revalidate
date:	Wed, 02 Oct 2024 07:24:22 GMT
etag:	"2923-ycAyULghfpJ3SHAUXOcrX5zk2qo"
referrer-policy:	strict-origin-when-cross-origin
set-cookie:	_wt_snowplowid.0497=2e3a6e66-7b78-48cf-af99-804d6849f46b.1727853862403.0.1727853862403.; Max-Age=63072000; Domain=.wetransfer.com; Path=/
strict-transport-security:	max-age=31536000; includeSubDomains
vary:	Accept-Encoding
x-content-type-options:	nosniff
x-dns-prefetch-control:	on
x-frame-options:	SAMEORIGIN
x-xss-protection:	1; mode=block
x-cache:	Miss from cloudfront
via:	1.1 d33f640b9793fb0553cc6dbe55988068.cloudfront.net (CloudFront)
x-amz-cf-pop:	PRG50-C1
alt-svc:	h3=":443"; ma=86400
x-amz-cf-id:	bhs6Cyh8dhwjfen1IrBAKXwOEsAmxh7f7K-aRKRgZVXOQ3y6ihVdvA==

DNS records:

A	address	18.65.39.126
A	ttl	60
A	address	18.65.39.71
A	ttl	60
A	address	18.65.39.60
A	ttl	60
A	address	18.65.39.127
A	ttl	60
MX	exchange	alt3.aspmx.l.google.com
MX	priority	10
MX	exchange	alt4.aspmx.l.google.com
MX	priority	10
MX	exchange	aspmx.l.google.com
MX	priority	1
MX	exchange	alt2.aspmx.l.google.com
MX	priority	5
MX	exchange	alt1.aspmx.l.google.com
MX	priority	5
NS	value	ns-67.awsdns-08.com
NS	value	ns-1528.awsdns-63.org
NS	value	ns-696.awsdns-23.net
NS	value	ns-1831.awsdns-36.co.uk
TXT	entries	v=spf1 -all
TXT	entries	apple-domain-verification=H5byjhvjDBB293EL
TXT	entries	google-site-verification=WnCfvGQ57Jq74gDr0JXy727scdaSI-8POqB0wfQ7tE4
SOA	nsname	ns-67.awsdns-08.com
	hostmaster	awsdns-hostmaster.amazon.com
	serial	1
	refresh	7200
	retry	900
	expire	1209600
	minttl	86400
CAA	critical	0
CAA	issue	amazon.com
CAA	critical	0
CAA	iodef	mailto:[email protected]

SEO headers

h1 Uh-oh...

How to solve problems with we.tl

Errors on the we.tl website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of we.tl on your own.