Is publishersweekly.com down or not working?

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

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

publishersweekly.com outage reports in the last 24 hours

publishersweekly.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

Protocol:
https
Status code:
200
Page size:
17.4 KB
Response time:
0.745sec.
IP:
18.215.213.228
Response headers:
date: Mon, 30 Sep 2024 22:50:17 GMT
content-type: text/html; charset=UTF-8
content-length: 18803
connection: close
server: nginx/1.6.2
cache-control: max-age=7200
vary: Accept-Encoding
content-encoding: gzip
x-cache-status: HIT
DNS records:
A address34.197.182.16
ttl60
A address52.0.155.202
ttl60
A address52.202.171.48
ttl60
A address23.22.26.170
ttl60
A address18.215.213.228
ttl60
A address34.235.101.123
ttl60
MX exchangemx2-us1.ppe-hosted.com
priority10
MX exchangemx1-us1.ppe-hosted.com
priority5
NS valuens-190.awsdns-23.com
NS valuens-1999.awsdns-57.co.uk
NS valuens-1370.awsdns-43.org
NS valuens-525.awsdns-01.net
TXT entriess7ft96aps4neuh2ll8stgu22jt
TXT entriesv=spf1 include:spf.protection.outlook.com a:dispatch-us.ppe-hosted.cominclude:amazonses.com ~all
TXT entriesthreatmate-dns-verification=TXT3425b1366f625864ad379dd4d19e45cd
TXT entriesppe-68f6e42cfbad1b1a51c0
TXT entriesMS=ms20322626
TXT entries1+xfSj66fDLMOBo3FU7jFXrl4sbzDAPzp7jNeHIyu3yxo4p+IfGkrnOXBBVK4Rhm1AiSeMwXOPlWvEQ1w7svNA==
SOA nsnamens-190.awsdns-23.com
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

How to solve problems with publishersweekly.com

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