
Crossref Status
Real-time updates of Crossref issues and outages
Crossref status is Operational
Crossref website
You're checking on Crossref - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
Yesterday, 13 September, we reported an incident with our website: www.crossref.org. It was down from 11:13 to 12:23 UTC. We resolved that incident prematurely. The outage was caused by a know intermittent issue that our technical team is working to resolve, but does not yet have fixed. We're monitoring the issue, and anticipate doing so for the foreseeable future. Thus, we have re-opened a new incident here. We'll provide updates as we have them. -IF
Recently Resolved Incidents
Our main website at www.crossref.org was down for 70 minutes earlier, from 11:13 to 12:23 UTC. It's been up since but we'll investigate what happened. Sorry for the inconvenience. -GH
Crossref Outage Survival Guide
Crossref Components
Crossref APIs
Public REST API
Polite REST API
OAI-PMH
XML API
OpenURL
Event Data Query API
Crossmark dialog server
Public content negotiation
Polite content negotiation
Crossref Metadata Plus
Plus REST API
Plus OAI-PMH
XML Snapshots
JSON Snapshots
Plus content negotiation
Key Manager
Crossref Content Registration
Admin tool
Test admin tool
Web deposit form
New Metadata Manager
Crossref Metadata files
Open Funder Registry
Retraction Watch
Annual public data files
Crossref Sites
Crossref website
Our main website at www.crossref.org was down for 70 minutes earlier, from 11:13 to 12:23 UTC. It's been up since but we'll investigate what happened. Sorry for the inconvenience. -GH
Yesterday, 13 September, we reported an incident with our website: www.crossref.org. It was down from 11:13 to 12:23 UTC. We resolved that incident prematurely. The outage was caused by a know intermittent issue that our technical team is working to resolve, but does not yet have fixed. We're monitoring the issue, and anticipate doing so for the foreseeable future. Thus, we have re-opened a new incident here. We'll provide updates as we have them. -IF