Is savers.com down or not working?

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

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

savers.com outage reports in the last 24 hours

savers.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:
Savers
Main page description:
With over 300 thrift stores in the U.S., Canada and Australia you're sure to find great deals on clothing, accessories, hard goods, electronics, books, home goods, and more.
Protocol:
https
Status code:
200
Page size:
10.2 KB
Response time:
0.495sec.
IP:
18.239.83.56
Response headers:
content-type: text/html
content-length: 10453
connection: close
x-amz-id-2: sTVqfcpB0zvUVqB9RM8vs+MjfwsMFf6wfKA//LibnnyO5H5WgYPp35KRPeGmxJxx//u5ynRcAac=
x-amz-request-id: 3RNF0WZ02VNQB0YW
date: Tue, 01 Oct 2024 08:44:16 GMT
cache-control: max-age=0, no-cache, no-store, must-revalidate
last-modified: Thu, 05 Sep 2024 19:51:40 GMT
etag: "2b43a7ef2311ef577dafd330160e7baa"
server: AmazonS3
vary: Accept-Encoding
x-cache: Miss from cloudfront
via: 1.1 ca0e18fe48e6994b3446a58a1e05c1ce.cloudfront.net (CloudFront)
x-amz-cf-pop: AMS58-P5
x-amz-cf-id: u4UfJevArcswuB05LWHNPuPtEMNQTsKbqmbxu_qzNLp_qYOxvnmpIw==
x-xss-protection: 1; mode=block
x-frame-options: SAMEORIGIN
content-security-policy: script-src 'self' 'unsafe-inline' 'unsafe-eval' https://secure.quantserve.com/ https://www.instagram.com/ https://app.termly.io/ https://www.google.com/ https://www.gstatic.com/ http://rules.quantcount.com/ http://cdn.scarabresearch.com/ https://assets.juicer.io/ https://www.googletagmanager.com/ http://cdn.scarabresearch.com/ https://cdn.levelaccess.net/ https://www.google-analytics.com/ https://www.googleadservices.com/ http://pixel.quantserve.com/ http://connect.facebook.net/ https://secure-ds.serving-sys.com/ https://s.pinimg.com/ http://xfqprspx.micpn.com/ https://static.bytedance.com/ http://www.lightboxcdn.com/ http://api.lightboxcdn.com/ https://bs.serving-sys.com/ http://www.juicer.io/ https://js.adsrvr.org/; object-src 'none'
x-content-type-options: nosniff
strict-transport-security: max-age=31536000

How to solve problems with savers.com

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