Crossref had 50 outages in the last 2 years totaling 1828h 47m of downtime — averaging 2.1 incidents per month.
There were 50 Crossref outages since January 17, 2025 totaling 1828h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.
The main Crossref website (www.crossref.org) has been down since 07:40 - 08:13 UTC. The website is available again.
The REST API public and polite pools are experiencing issues with requests that return lists of results, including filters and queries. Requests are intermittently not returning all matching metadata records. We are investigating the cause.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have received multiple reports that requests in the REST API that use cursors to paginate through multiple pages of results are finishing early and not returning all of the requested records. We are investigating the cause. -IF
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved and our REST API is operating normally.
We are receiving a very large number of requests from a user that is applying various strategies to get around our rate limits on our public REST API pool. This is impacting performance, including on the public and polite REST API pools, Crossmark, content negotiation, Crossref Metadata Search and reference matching. We are investigating solutions.
We are continuing to work on a fix for the performance issue.
We have deployed and are monitoring a fix for this issue that affected our APIs and Metadata Search.
We experienced a couple of downtimes for the Public REST API at 3:09 and 4:15 UTC due to high rates of requests. We are continuing to implement fixes and are monitoring the degraded performance on the Public and REST APIs.
We are continuing to monitor our fixes for any further issues affecting the Public and Private REST APIs, Crossmark, content negotiation, and metadata search.
This incident has been resolved.
We are investigating an incident with multiple tools and services including: - Web deposit form (https://apps.crossref.org/webDeposit) - Participation Reports (https://crossref.org/members/prep/) - Browsable title list (https://www.crossref.org/titleList/) - Other reports and forms under crossref.org Starting from around 04.16am UTC on 16 June, users attempting to access these tools have been receiving 503 errors. Our technical team are investigating. We'll provide updates as soon as we know more.
A fix has been implemented. The services are available again and working as expected. We are now monitoring their performance and continuing to investigate the cause of the incident.
Participation Reports, the web deposit form, and other small apps and reports have been fully operational again since about 08.30am UTC.
Due to a configuration change, we stored, but did not send out, DOI Error Reports starting on May 11th 2026. The problem was reported, identified, and a fix was implemented, on June 10th 2026. All DOI Error Reports from the outage period are intact and will be emailed shortly.
We are experiencing delays in updating some metadata fields on the REST API. This includes citation counts, Retraction Watch retractions, aliased DOIs, and metadata in the member, journal, and funder routes. We are currently investigating the cause.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We have identified a bug in our system which may result in failing submissions at this time. An emergency release is scheduled for approximately 1900 UTC with a fix. During the release, our members may experience delays in deposit system admin tool (doi.crossref.org) processing. Deposits submitted during that time will be stored and processed after the maintenance has been completed.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
Emergency release version 0.274.2 has been released. We are monitoring the results.
This incident has been resolved and the emergency maintenance has been completed.
Due to problems with API indexing that occurred between 4/29 and 5/3, the current JSON snapshot for April 2026 is missing 1-2 days of data. We've resolved the indexing issue and are currently re-pushing the missing records into the API. Once that's completed, over the next few days, we'll build and release a new snapshot for April.
The corrected JSON snapshot is in process. It will be completed and available in the next 2-3 days.
The corrected April 2026 JSON snapshot has been released.
Submission processing within our admin tool - doi.crossref.org - stalled and was therefore delayed between 10:56 and 20:57 UTC Sunday, 3 May. This issue has been fixed and submissions are again being processed. No submissions were lost during the processing delay; we stored all of those submissions in our system and began processing them at 20:57 UTC. There are no delays currently. -IF
No newly created records have been index in REST API since 4/29. Our technical team is investigating. Impacts on downstream services such as Crossmark, Participation Reports, Metadata Search, and Co-Access/Multiple Resolution interim pages.
We are continuing to investigate this issue.
We've resolved the issue. Records are being indexed in the REST API as expected again. This includes the backlog of records that were affected by this incident.
Records are being indexed in the REST API as expected again. This includes the backlog of records that were affected by this incident.
This issue has been resolved. Missed records have been indexed, and indexing of newly created and updated records has resumed.
On 31 March, we migrated our test system - test.crossref.org - and brought it into sync with our production admin tool - doi.crossref.org. As a result of that migration, access to some of the test accounts was temporarily lost. In addition, members with notification callbacks enabled in test may have noticed that test callbacks were being misrouted to the endpoints set up for your production callbacks. We have since fixed both issues. If you're a test system user who is experiencing any issues today, do contact us at [email protected] so we can investigate and assist. - IF
The main Crossref website (www.crossref.org) has been down since 05:46 UTC. We are investigating the cause of the issue.
The website is available again. We are monitoring the situation.
From 05:46 UTC on 17 April we experienced a sustained surge of traffic to our website, which was caused by bot activity distributed across multiple IP addresses. The service recovered automatically without intervention after about an hour, and we have since applied tighter rate-limiting to the source. We are also reviewing options to further improve the scalability and resilience of the service going forward.
Our depositor reports (e.g., https://data.crossref.org/depositorreport?pubid=J533343) are returning status code 504 gateway timeout errors. We're aware of the issue and our technical team is investigating. -IF
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The 2026 public data file was stalling during download via Academic Torrents (https://academictorrents.com/details/b5ee0e102689b3e67023dd024694c0f5f124646f) for the last few days due to an issue with the number of available sources. We have addressed the issue and downloads should now be completing with no stalling/delays.
Crossref Resolution Reports (https://www.crossref.org/06members/51depositor.html) are currently unavailable. We will provide an update as soon as we have further information.
Resolution reports were unavailable from around 02:28 UTC to 09:42 UTC, due to the server running out of memory. We have rebooted the server and the service is now available again.
Crossref DOIs have not been resolving as expected since around 06:56 UTC. Any attempt to resolve them returns the error message: “DOI Cannot Connect to Server.” We are currently investigating the issue.
UPDATE: Crossref DOIs have not been resolving as expected since around 06:56 UTC. Any attempt to resolve them returns the error message: “DOI Cannot Connect to Server.” Some DOI registrations are impacted too. We are closely working with the DOI Foundation on a fix.
The DOI Foundation identified the issue as a surge in traffic affecting the backend infrastructure of doi.org. This has been resolved. Crossref registration servers have been restarted, and metadata registrations are now processing successfully.
We continue to monitor the system to ensure stability and consistent processing of registrations.
This incident has been resolved. All affected metadata submissions have now been reprocessed.
Yesterday, we experienced a brief website (www.crossref.org) downtime from 10:05 UTC to 10:24 UTC. This issue was resolved, and a temporary fix was implemented to prevent such spontaneous disruptions while we work on a permanent solution. EA
We have had members reporting ‘Error Loading Metadata’ failure messages in the new Metadata Manager tool -https://manage.crossref.org/records - when updating existing records. Our technical team is investigating. -IF
The issue has been identified. This bug is only affecting DOIs with more than one /. Those DOIs will continue to trigger the ‘Error Loading Metadata’ failure messages until we fix the issue. -IF
We are continuing to work on a fix for this issue.
This incident has been resolved.
Our test admin tool - test.crossref.org - is experiencing degraded performance at the moment. Author-title and funder searches for deposits are failing and we have a backlog of test submissions that we're working through. Our technical and infrastructure teams are investigating. -IF
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our Participation Reports were unavailable from 02:24 UTC until 10:10 UTC due to a problem with their server. Our team has now increased the size of this server and enabled the report to run across more servers. Apologies for the inconvenience if you were trying to check your participation during this time - AB
Turnitin has reported that users in Europe may have issues logging into their iThenticate accounts. They are currently investigating the issue. Please see their status for updates: https://turnitin.statuspage.io/incidents/krzh571rxsc2
This incident has now been resolved by Turnitin. - KL
Several members have reported that their sessions have been dropped (screen turning white) when attempting to add contributor metadata to their registrations within Metadata Manager - https://www.crossref.org/metadatamanager/. Members facing this issue should register their metadata without contributors and then use the new record registration form - https://manage.crossref.org/records - to import those records so their contributors can be added to the metadata. Please contact our support team - [email protected] - if you have questions. - IF
We have deprecated - https://www.crossref.org/deprecated/ - our previous Metadata Manager tool. Members who previously made use of Metadata Manager to register their metadata should move to our new form - https://manage.crossref.org/records. Please contact our support team - [email protected] - if you have questions. - IF
Cloudflare network problems are affecting multiple sites, including doi.org resolution, meaning many DOI links are very slow or result in errors. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
The DOI Foundation is also aware: https://doi.statuspage.io/incidents/z0rwt8tqcfsm
Clouflare reports that the issues are fixed, and DOIF subsequently reports that doi.org resolutions have returned to normal.
CNRI has written a postmorterm about how they handled the Cloudflare outage for doi.org: [https://doi.statuspage.io/incidents/z0rwt8tqcfsm](https://doi.statuspage.io/incidents/z0rwt8tqcfsm)