Is upworthy.com down or not working?

What happened to upworthy.com, why did the website go down and not work? Here you can see who else is having the same problem with upworthy.com, 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, upworthy.com is working fine, but single failures are possible. If upworthy.com does not work for you, then report your problem and write a comment.
Add comment

What to do if the site upworthy.com is not available? Try our guide.

upworthy.com outage reports in the last 24 hours

upworthy.com - 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.

Technical information

Main page title:
Upworthy
Main page description:
Positive stories that inspire and uplift. From heartwarming moments to thought-provoking content, we’re sharing the best of humanity with the world, one story at a time.
Protocol:
https
Status code:
200
Page size:
172.0 KB
Response time:
0.148sec.
IP:
151.101.129.68
Response headers:
connection: close
content-length: 176108
server: nginx
content-type: text/html; charset=utf-8
cache-control: public, max-age=0
cache-tag: long_cache_articles/19596302,section/0-19596302,section/489453095
cloudflare-cdn-cache-control: max-age=21600, stale-while-revalidate=2592000, stale-if-error=87600
etag: "d55e37c9cb2f8e108d58194c4749a0d3"
via: 1.1 [email protected] cluster-prod,1.1 [email protected] cluster-prod, 1.1 ingress@dev, 1.1 varnish, 1.1 varnish
x-assets-optimize: 1
x-rebelmouse-origin-timing: 0
xkey: long_cache_articles/19596302 section/0-19596302 section/489453095
x-request-category: public
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
x-request-id: 563d8406-1016-4b6f-ad10-1624e76ebf12
fastly-swr: 2592000.000
fastly-sie: 86400.000
fastly-request-backend: fastly
accept-ranges: bytes
age: 3485
date: Tue, 01 Oct 2024 03:04:17 GMT
x-served-by: cache-iad-kjyo7100113-IAD, cache-ams2100084-AMS
x-cache: HIT, HIT
x-cache-hits: 8, 0
x-timer: S1727751858.618404,VS0,VE1
vary: Accept-Encoding, Accept-Encoding
x-rebelmouse-authorization: disabled
x-rebelmouse-layouts-key: www.upworthy.com,(null)
alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400
DNS records:
A address151.101.65.68
ttl60
A address151.101.1.68
ttl60
A address151.101.129.68
ttl60
A address151.101.193.68
ttl60
MX exchangeaspmx3.googlemail.com
priority30
MX exchangeaspmx5.googlemail.com
priority30
MX exchangeaspmx4.googlemail.com
priority30
MX exchangeaspmx2.googlemail.com
priority30
MX exchangealt2.aspmx.l.google.com
priority20
MX exchangeaspmx.l.google.com
priority10
MX exchangealt1.aspmx.l.google.com
priority20
NS valuens-1425.awsdns-50.org
NS valuens-715.awsdns-25.net
NS valuens-457.awsdns-57.com
NS valuens-2044.awsdns-63.co.uk
TXT entriesahrefs-site-verification_208180a6cc0928b213e74c3d7f7a1a590b2465cabfadeee5ecbf89284b2fc165
TXT entriesfacebook-domain-verification=jue4v89bvl11q68r5cfutqjxjc7lgf
TXT entriesgoogle-site-verification=iQvdguHpbFJGNa0R5eY0pK5mWxe-vbvZ-GIxtrJhUnM
TXT entries_globalsign-domain-verification=PILG2L7GR-2KecCXJkC9QC-kzXA2GQir70Rw22Bv9C
TXT entriesgoogle-site-verification=uVat-KAWajrF5bolggbyYinaR6jyd8eeFB0afmn_SRI
TXT entriesglobalsign-domain-verification=8DqtGiinnsWmU7Jx8drsM7aOLda0Uy2HVd8iE4qWWF
TXT entriesv=spf1 include:aspmx.sailthru.com include:_spf.google.com ip4:208.85.55.231 include:mailgun.org include:servers.mcsv.net ~all
TXT entriesspf2.0/pra include:aspmx.sailthru.com include:_spf.google.com ~all
TXT entriesfastly-domain-delegation-fiCFm1rTLjufgmAU-20200831
TXT entries_globalsign-domain-verification=KGGPxZTljntNuhXtwn8XgxduaNwNNWTC3gor_8vRoq
TXT entriesgoogle-site-verification=j_XnClieLxg_UNWBIMpT18FjAeZ0pHPrIVumerShUHg
TXT entriesfastly-verification-201906
SOA nsnamens-715.awsdns-25.net
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

SEO headers

h2 Cool video shows why everyone used to wear hats and then suddenly stopped
h1 Delivering the best of humanity every day

How to solve problems with upworthy.com

Errors on the upworthy.com 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 upworthy.com on your own.