JSTOR help and reporting
Use the official help route for JSTOR; identify the specific product and action described on this page.
Live Domain Check
Run a live reachability check for jstor.org. Compare the regional responses with the problem you see in JSTOR.
Find JSTOR help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
JSTOR distinguishes public metadata, individual accounts and institutional access. Its login guidance notes that a library or school may supply the credentials or access route needed for subscribed content.
The checker above requests jstor.org from eight configured locations and shows the responses and measurement times. Compare those observations with the actual JSTOR action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
For separate work & learning services, compare these individual checks: Substack status check, ResearchGate status check, WordPress.com status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse work app checks.
Use the official help route for JSTOR; identify the specific product and action described on this page.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
We have not linked a separate status page for this service. Check the official help page for current notices.
Open JSTOR help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Stable item link, access route, library context and time; never publish institutional credentials or private access links.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to JSTOR.
These are troubleshooting comparisons, not claims that JSTOR is currently experiencing a particular incident.
Compare an article's record with the full-text action and identify whether you entered through your library or an individual account.
If institutional access is missing, contact the library about that entitlement and use JSTOR support for platform errors. A paywall or unavailable licence is different from a server outage.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use the comparison and support guidance above for the specific action. Keep the original check and error timestamps together; a cached result can be older than the problem you are seeing.
Repeat the same action in a second browser or on another available connection, keeping the item and account the same. Change one thing at a time so the result is comparable. Leave required workplace or school security controls in place.
Follow the website troubleshooting guide for connection checks. Preserve any unsent work before refreshing a form or changing a session.
Compare an article's record with the full-text action and identify whether you entered through your library or an individual account. If institutional access is missing, contact the library about that entitlement and use JSTOR support for platform errors. A paywall or unavailable licence is different from a server outage.
Use the community buttons on this page to share whether the service works for you. For help from JSTOR, use the official help/reporting resource linked above. Use the official help route for JSTOR; identify the specific product and action described on this page.
Compare an article's record with the full-text action and identify whether you entered through your library or an individual account. If institutional access is missing, contact the library about that entitlement and use JSTOR support for platform errors. A paywall or unavailable licence is different from a server outage.
Stable item link, access route, library context and time; never publish institutional credentials or private access links.