Is jstor.org down or not working?

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

What to do if the site jstor.org is not available? Try our guide.

jstor.org outage reports in the last 24 hours

jstor.org - 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:
JSTOR Home
Main page description:
JSTOR is a digital library of academic journals, books, and primary sources.
Protocol:
https
Status code:
200
Page size:
41.7 KB
Response time:
0.511sec.
IP:
151.101.192.152
Response headers:
connection: close
content-length: 42753
x-envoy-upstream-service-time: 75
x-frame-options: DENY
server: envoy
set-cookie: AccessSession=H4sIAAAAAAAA_4WRTW_bMAyG_4vOVUCJkiX5FgTtWnTooUsPWzEM-nLmwmkDfwzYgv73UY7b9ZRZPpD085Kv6CObpjaxmjUxO0hK8NhIy5V2DXdV1jwltBlkyqgtu2DtgVi9UnplxEqrUilqkbVwVQjOClQ2aediwiqixAShqTRx_QwGr3KTK8NTIyRXVngeInpudFaQnK5ESgR3fiRYglQcHEfYSqhlVWugmVIiVlJ_K9h0FlP0Fmw4TxmYm42R1Y3vhnzBfvludvtRg-8aOoDWFo0fx35g9ZFtNoRfPlBps6XI74cx98nvf9xdl9pXqt19puh-8xZ9KdzN9np9u2av1Gkaf65jHKnb43dKl_B42i8aZaSQJMtz7oMFgzJwFyHQGqXhTmfkpnEymKQDSleu9PuQib7Pu_blmfJ9-9zu2z_5qvM7Vo_9RHftlgFoDVZlp4uon0UPQ-7J3mJDAAC-m3CZTKQceYOGTESjuY9WcojCOq9jAA__THzqX6bDWQ_yw_RdoU_DaRtP83f4z8NOW1z-4utfYvcDKtsCAAA; Path=/; SameSite=Lax; Secure,AccessSessionSignature=2e495df0231004fe345848132ee6cd6e8a0fe024613223fbbd9d2cca3607a77f; Path=/; SameSite=Lax; Secure,AccessSessionTimedSignature=5510b02ed0fdc2115fc18073650915bfa2358b355b9351b8756200907669066f; Path=/; SameSite=Lax; Secure,UUID=fce90d41-cf28-459f-96e5-dd38e02de358; expires=Thu, 30 Sep 2027 20:26:50 GMT; Max-Age=94608000; Path=/; SameSite=None; Secure,csrftoken=3HV8qULUnKrglGMuF1KlCrcMgTePFWlZ; expires=Mon, 29 Sep 2025 20:26:50 GMT; Max-Age=31449600; Path=/; SameSite=Lax; Secure,ReferringRequestId=fastly-default:02f53be6eadc3891b7180b7a3ceae046; Path=/; SameSite=Lax; Secure
content-type: text/html; charset=utf-8
x-jstor-restarts: 0
accept-ranges: bytes
date: Mon, 30 Sep 2024 20:26:50 GMT
via: 1.1 varnish
x-served-by: cache-ams2100114-AMS, cache-ams2100140-AMS
x-cache: MISS, MISS
x-cache-hits: 0, 0
x-timer: S1727728010.443606,VS0,VE178
vary: Cookie, origin, Accept-Encoding,Fastly-SSL,Origin,X-Requested-Host
alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400
DNS records:
A address151.101.0.152
ttl3600
A address151.101.192.152
ttl3600
A address151.101.128.152
ttl3600
A address151.101.64.152
ttl3600
MX exchangesmtp2.ithaka.org
priority100
MX exchangemx2.hc5909-85.iphmx.com
priority10
MX exchangemx1.hc5909-85.iphmx.com
priority10
MX exchangesmtp1.ithaka.org
priority100
NS valueusnjpr2ns02.ithaka.org
NS valueusmiaa1ns03.ithaka.org
NS valueusnyny1ns05.ithaka.org
NS valueusnjpr2ns01.ithaka.org
NS valueusnjpr2ns04.ithaka.org
TXT entriesv=spf1 mx exists:%{i}.spf.hc5909-85.iphmx.com include:_spf.act-on.net include:u1397501.wl.sendgrid.net include:mail.zendesk.com include:_spf.ultipro.com include:aspmx.pardot.com ~all
TXT entriesgoogle-site-verification=fUzFvqROnu3S1gFEmkwguY42PzRgOFzwg4qQMP24sU4
TXT entries_globalsign-domain-verification=-lBuNJDFRxDkLkNbYOLBU03PlWjnPqAzBPAVUokhAw
TXT entries59bemol8mg22oln54totem851d.
TXT entriessending_domain1053043=a4a2b757167b9ba217895b3e2bb19f3873b9db5b7c0e9b4c6dd2c98c32b93935
TXT entriesfacebook-domain-verification=t7mhq4udodhlfom0rn909rrhmrcq7f
TXT entriesMS=ms59722565
TXT entriespardot1053043=4a6c81f133c99f6b859af420931577c383a1b1cd4e153d11ddb1b150a902b382
SOA nsnameusnjpr2ns02.ithaka.org
hostmasterhostmaster.ithaka.org
serial2024091801
refresh10800
retry3600
expire1209600
minttl3600

How to solve problems with jstor.org

Errors on the jstor.org 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 jstor.org on your own.