Crossref Outage History

Started Apr 03, 2026, 06:31 PM UTC· resolved Apr 03, 2026, 06:37 PM UTC

1. investigating Apr 03, 2026, 06:31 PM UTC

   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

2. monitoring Apr 03, 2026, 06:35 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Apr 03, 2026, 06:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 31, 2026, 09:00 PM UTC· resolved Mar 31, 2026, 09:00 PM UTC

1. resolved Apr 21, 2026, 09:19 PM UTC

   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

Read the full incident report →

Started Mar 30, 2026, 03:13 PM UTC· resolved Mar 30, 2026, 03:13 PM UTC

1. resolved Mar 30, 2026, 03:13 PM UTC

   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.

Read the full incident report →

Started Mar 24, 2026, 09:41 AM UTC· resolved Mar 24, 2026, 10:49 AM UTC

1. investigating Mar 24, 2026, 09:41 AM UTC

   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.

2. resolved Mar 24, 2026, 10:49 AM UTC

   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.

Read the full incident report →

Started Mar 17, 2026, 07:56 AM UTC· resolved Mar 17, 2026, 08:03 PM UTC

1. investigating Mar 17, 2026, 07:56 AM UTC

   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.

2. investigating Mar 17, 2026, 09:45 AM UTC

   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.

3. identified Mar 17, 2026, 10:35 AM UTC

   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.

4. monitoring Mar 17, 2026, 10:38 AM UTC

   We continue to monitor the system to ensure stability and consistent processing of registrations.

5. resolved Mar 17, 2026, 08:03 PM UTC

   This incident has been resolved. All affected metadata submissions have now been reprocessed.

Read the full incident report →

Started Feb 25, 2026, 10:00 AM UTC· resolved Feb 25, 2026, 10:24 AM UTC

1. resolved Feb 26, 2026, 11:14 AM UTC

   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

Read the full incident report →

Started Dec 16, 2025, 07:17 PM UTC· resolved Jan 09, 2026, 03:44 PM UTC

1. investigating Dec 16, 2025, 07:17 PM UTC

   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

2. identified Dec 16, 2025, 08:55 PM UTC

   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

3. identified Jan 05, 2026, 08:03 PM UTC

   We are continuing to work on a fix for this issue.

4. resolved Jan 09, 2026, 03:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 16, 2025, 07:11 PM UTC· resolved Dec 16, 2025, 10:34 PM UTC

1. investigating Dec 16, 2025, 07:11 PM UTC

   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

2. monitoring Dec 16, 2025, 08:29 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Dec 16, 2025, 10:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 16, 2025, 02:00 AM UTC· resolved Dec 16, 2025, 10:10 AM UTC

1. resolved Dec 16, 2025, 10:38 AM UTC

   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

Read the full incident report →

Started Dec 11, 2025, 04:41 PM UTC· resolved Dec 11, 2025, 05:25 PM UTC

1. investigating Dec 11, 2025, 04:41 PM UTC

   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

2. resolved Dec 11, 2025, 05:25 PM UTC

   This incident has now been resolved by Turnitin. - KL

Read the full incident report →

Started Dec 02, 2025, 07:54 PM UTC· resolved Jan 02, 2026, 07:06 PM UTC

1. investigating Dec 02, 2025, 07:54 PM UTC

   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

2. resolved Jan 02, 2026, 07:06 PM UTC

   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

Read the full incident report →

Started Nov 18, 2025, 12:51 PM UTC· resolved Nov 18, 2025, 08:01 PM UTC

1. investigating Nov 18, 2025, 12:51 PM UTC

   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

2. investigating Nov 18, 2025, 01:12 PM UTC

   The DOI Foundation is also aware: https://doi.statuspage.io/incidents/z0rwt8tqcfsm

3. resolved Nov 18, 2025, 08:01 PM UTC

   Clouflare reports that the issues are fixed, and DOIF subsequently reports that doi.org resolutions have returned to normal.

4. postmortem Nov 20, 2025, 08:22 PM UTC

   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)

Read the full incident report →

Started Oct 27, 2025, 06:10 PM UTC· resolved Nov 04, 2025, 03:27 AM UTC

1. investigating Oct 27, 2025, 06:10 PM UTC

   We have found that starting on 24th October around 1800 UTC that not all submissions logs are being emailed to our members. Our technical team is investigating. -IF

2. investigating Oct 27, 2025, 09:04 PM UTC

   We are continuing to investigate this issue.

3. identified Oct 28, 2025, 04:06 PM UTC

   The issue has been identified and a fix is being implemented.

4. resolved Nov 04, 2025, 03:27 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 03, 2025, 10:18 PM UTC· resolved Oct 05, 2025, 03:58 PM UTC

1. identified Oct 03, 2025, 10:18 PM UTC

   We had a configuration error on our end with the Metadata Plus snapshots that was resulting in Plus subscribers being unable to retrieve snapshots for yesterday and today. We have fixed that setting and snapshots should again be available to Plus subscribers. The XML snapshots for September has finished uploading and is also available (https://api.crossref.org/snapshots/monthly/2025/09). That configuration error has also caused the JSON snapshots run to fail. We're working on fixing that and will rerun the process once we do. That will delay the JSON snapshots this month, but we expect them to be available by Monday, 6 October. -IF

2. resolved Oct 05, 2025, 03:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 20, 2025, 08:08 PM UTC· resolved Sep 21, 2025, 02:07 AM UTC

1. investigating Sep 20, 2025, 08:08 PM UTC

   We are currently investigating this issue. -IF

2. identified Sep 20, 2025, 08:39 PM UTC

   The issue has been identified and a fix is being implemented. -IF

3. monitoring Sep 20, 2025, 08:59 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Sep 21, 2025, 02:07 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 15, 2025, 09:13 AM UTC· resolved Oct 02, 2025, 03:31 PM UTC

1. investigating Sep 15, 2025, 09:13 AM UTC

   We have found that some records failed to be indexed by the REST API on Friday 12th September, and continuing. Our technical team is investigating.

2. investigating Sep 15, 2025, 04:33 PM UTC

   We are continuing to investigate this issue.

3. investigating Sep 16, 2025, 02:14 PM UTC

   Our technical team is re-pushing all of the records that have failed to be indexed since Friday, 12 September. Those records should be indexed in the REST API in the next 24 hours. -IF

4. monitoring Sep 17, 2025, 12:48 PM UTC

   A fix has been implemented and we are monitoring the results. Do to the heavy workload of indexing a large volume of records yesterday, we have observed longer response times in the Public and Polite pools of the REST API. We believe those response times should improve throughout the day. -IF

5. monitoring Sep 19, 2025, 10:15 AM UTC

   The public and polite pools are still showing as unstable with long response times and timeouts occurring. We are still looking into this as a priority and will post with more information as we know it.

6. monitoring Sep 22, 2025, 07:08 PM UTC

   We are continuing to monitor for any further issues.

7. identified Sep 23, 2025, 01:26 PM UTC

   The public and polite pools are still experiencing some instability, which is affecting downstream tools such as Participation Reports, Search, and Crossmark. We're working on a fix incl. infrastructure upgrades that should help long-term. -GH

8. identified Sep 26, 2025, 01:59 PM UTC

   We've identified and fixed one issue which was affecting citation counts. We're still working on two additional tasks: upgrading Elasticsearch in the REST API and updating the service that synchronises new and updated metadata records with the REST API. -GH

9. resolved Oct 02, 2025, 03:31 PM UTC

   We have updated the service that synchronises new and updated metadata records with the REST API; all three pools of the REST API are performing well as a result (as are the services that run on it). Thus, we are resolving this incident. -IF

Read the full incident report →

Started Sep 11, 2025, 11:56 AM UTC· resolved Sep 12, 2025, 01:14 PM UTC

1. investigating Sep 11, 2025, 11:56 AM UTC

   We have found that some records failed to be indexed by the REST API on 3rd September, and continuing. Our technical team is investigating. -EA

2. identified Sep 11, 2025, 09:30 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Sep 12, 2025, 01:14 PM UTC

   This incident has been resolved. -IF

Read the full incident report →

Started Sep 09, 2025, 07:02 PM UTC· resolved Sep 10, 2025, 05:53 PM UTC

1. identified Sep 09, 2025, 07:02 PM UTC

   All deposits containing references to CNKI, one of our sibling registration agencies, DOIs are processing slower at this time because of technical issues at CNKI. As a result, that is causing delays in submission processing and email notification delivery for all submissions (but especially submissions containing references to CNKI DOIs). -IF

2. resolved Sep 10, 2025, 05:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 22, 2025, 02:47 PM UTC· resolved Aug 25, 2025, 01:24 PM UTC

1. investigating Aug 22, 2025, 02:47 PM UTC

   We've had a Metadata Plus user sending bursts of very large numbers of queries which is knocking out the REST API Plus pool for a number of minutes at a time throughout the day today. We are working to get in contact with the Plus user in question to correct the behavior, but those large bursts of queries are causing some intermittent instability to the Plus pool. -IF

2. resolved Aug 25, 2025, 01:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 19, 2025, 09:39 AM UTC· resolved Aug 27, 2025, 01:16 PM UTC

1. investigating Aug 19, 2025, 09:39 AM UTC

   We have noted performance-related issues with Participation Reports. We are investigating the underlying cause. >EA

2. identified Aug 19, 2025, 01:56 PM UTC

   The issue has been identified and a fix is being implemented. >EA

3. monitoring Aug 19, 2025, 07:45 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Aug 20, 2025, 12:55 PM UTC

   We are continuing to monitor for any further issues.

5. monitoring Aug 25, 2025, 01:24 PM UTC

   A fix has been implemented. We will be monitoring the results for a few days before we resolve this incident. -IF

6. resolved Aug 27, 2025, 01:16 PM UTC

   This incident has been resolved. -IF

Read the full incident report →

Started Aug 05, 2025, 09:07 AM UTC· resolved Aug 08, 2025, 03:05 PM UTC

1. investigating Aug 05, 2025, 09:07 AM UTC

   Metadata Plus subscribers may be experiencing slow responses or timeouts from the REST API. We're still completing the setup of rate limiting in the new cloud environment, so we are focusing on getting that done ASAP. -GH

2. monitoring Aug 06, 2025, 10:35 AM UTC

   Things have settled down as a result of our changes and the Plus pool is performing better now. We're monitoring. -GH

3. monitoring Aug 07, 2025, 03:15 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Aug 08, 2025, 03:05 PM UTC

   We have made changes on our end that has resulted in better response times. This incident has been resolved. -IF

Read the full incident report →

Started Aug 04, 2025, 01:24 PM UTC· resolved Aug 07, 2025, 07:23 PM UTC

1. identified Aug 04, 2025, 01:24 PM UTC

   There was a bug in the code that generates the new XML Metadata Plus snapshots and, as a result, this month's XML Metadata Plus snapshots will be delayed. We have updated that code and the XML Metadata Plus snapshots are now being generated, but they may not be available until 7 August. -IF

2. identified Aug 06, 2025, 10:45 AM UTC

   Unfortunately, the data in the XML snapshot doesn't match what we would expect, so we're going to re-run it again. It takes a few days - we'll keep this incident updated as we know more. -GH

3. identified Aug 07, 2025, 03:19 PM UTC

   We continue to generate the new XML Metadata Plus snapshots. We expect it to be available by Saturday, 9 August. -IF

4. resolved Aug 07, 2025, 07:23 PM UTC

   This incident has been resolved. The newest XML Metadata Plus snapshots is now available.

Read the full incident report →

Started Jul 23, 2025, 07:12 PM UTC· resolved Aug 12, 2025, 07:47 PM UTC

1. investigating Jul 23, 2025, 07:12 PM UTC

   We have had metadata users report that they are receiving intermittent 504 (Gateway time-out) status code errors on calls to OAI-PMH endpoints. We have been able to replicate and are currently investigating. -IF

2. investigating Jul 24, 2025, 03:28 PM UTC

   We are continuing to investigate this issue.

3. investigating Jul 25, 2025, 08:40 PM UTC

   We are continuing to investigate this issue.

4. identified Jul 28, 2025, 06:49 PM UTC

   This issue has been identified and we'll be releasing a fix during tomorrow's maintenance window. -IF

5. identified Jul 30, 2025, 04:03 PM UTC

   We are continuing to work on a fix for this issue.

6. monitoring Aug 06, 2025, 06:26 PM UTC

   A fix has been implemented and we are monitoring the results.

7. monitoring Aug 08, 2025, 03:09 PM UTC

   We believe our changes have solved this issue, but we're going to continue to monitor this over the weekend. -IF

8. resolved Aug 12, 2025, 07:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 22, 2025, 05:45 PM UTC· resolved Jul 25, 2025, 09:01 AM UTC

1. investigating Jul 22, 2025, 05:45 PM UTC

   We distributed about a third of this month's resolution report before the batch run failed. Our technical team is working on a fix. Once the fix is in place, we will distribute the remaining resolution reports for this month. -IF

2. investigating Jul 22, 2025, 07:40 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jul 22, 2025, 09:37 PM UTC

   Jon on our technical team has deployed a fix and this month's run of the resolution report has resumed. It may take a several days before all reports have been distributed to our members. -IF

4. monitoring Jul 23, 2025, 08:20 PM UTC

   We are continuing to generate resolution reports for anyone who has yet to receive them this month.

5. monitoring Jul 24, 2025, 12:35 PM UTC

   Several members have reported that the links within the resolution reports are returning 404 'page not found' status code errors. We are actively working to fix those links and hope to have those routed properly within the next 24 hours. -IF

6. monitoring Jul 25, 2025, 12:50 AM UTC

   All of this month's resolution reports have now been delivered. The links within the reports continue to resolve to 404 'page not found' status code errors. We expect to have those links repaired tomorrow. -IF

7. resolved Jul 25, 2025, 09:01 AM UTC

   This should all be resolved now and the reports should not be resolving to a 404 error anymore.

Read the full incident report →

Started Jul 21, 2025, 12:45 PM UTC· resolved Aug 27, 2025, 12:06 PM UTC

1. investigating Jul 21, 2025, 12:45 PM UTC

   We have found that some records failed to be indexed by the REST API on 8 July and then again from 16 to 20 July. We believe this is related to our recent data centre migration (https://status.crossref.org/incidents/s92nm4xn1w84). Our technical team is investigating. -IF

2. identified Jul 22, 2025, 01:23 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified Jul 22, 2025, 07:37 PM UTC

   We are continuing to work on a fix for this issue.

4. identified Jul 23, 2025, 08:20 PM UTC

   We are continuing to work on a fix for this issue.

5. identified Jul 25, 2025, 08:41 PM UTC

   We are continuing to work on a fix for this issue.

6. identified Jul 28, 2025, 06:46 PM UTC

   We have found that this bug is impacting REST API indexing of DOIs since 8 July. We have found examples of a minority of records missing from the REST API since that 8 July date. Our technical team continues to work on a fix. -IF

7. identified Jul 30, 2025, 04:03 PM UTC

   We are continuing to work on a fix for this issue.

8. monitoring Jul 30, 2025, 07:20 PM UTC

   We’ve now solved the issues that were blocking reindexing. We will continue to monitor those issues, and will be working on adding the missing records that were not indexed earlier in July over the next couple of days. -IF

9. monitoring Aug 04, 2025, 01:21 PM UTC

   We have now reindexed all records since 7 July. No records were indexed from 17 to 19 July, but those records have all been reindexed in the last few days. There should be no missing records in the REST API for the month of July. We will continue to monitor this issue for the first couple of weeks of August to be sure that there are no other indexing issues with the REST API. -IF

10. monitoring Aug 06, 2025, 06:21 PM UTC

    We are continuing to monitor for any further issues.

11. identified Aug 11, 2025, 06:14 PM UTC

    Unfortunately, we have found that this bug is impacting REST API indexing of DOIs registered in August, so the underlying issue that is causing a small percentage of DOIs from being indexed in the REST API persists. Our technical team continues to work on a fix. -IF

12. identified Aug 13, 2025, 07:26 PM UTC

    We continue to receive reports from members and metadata users of records missing from our REST API. For the records not being indexed, which we have confirmed has continued for records registered into August, this can cause downstream issues for a number of services (e.g., Crossref metadata search - search.crossref.org, Participation Reports, ORCID auto-update, and for external services that make use of the metadata in our REST API). Our technical team continues to work on a fix. -IF

13. identified Aug 14, 2025, 07:19 PM UTC

    Our technical team is reindexing all records registered between 3 and 14 August, because we found works missing in our REST API. That reindex should be completed by end of day tomorrow. We continue to investigate the underlying cause of these indexing errors. -IF

14. identified Aug 15, 2025, 09:38 PM UTC

    Our technical team completed the reindex of all records registered between 3 and 14 August earlier today. There is still an underlying issue that is causing some records to go unindexed in the REST API. We continue to investigate that cause. We will continue to push records that are not being indexed in the REST API until we find and fix the bug. -IF

15. identified Aug 18, 2025, 02:15 PM UTC

    Our support and technical teams are finding a very small percentage of DOIs from our reindexing on 4 and 14 August that are not yet appearing in the REST API. If you have examples of DOIs that are not appearing in our REST API from registrations in July or August 2025, please do contact our support team - [email protected] - in order for us to investigate further. Our technical team continues to actively work on a fix. -IF

16. identified Aug 20, 2025, 05:47 PM UTC

    We are continuing to work on a fix for this issue. Martyn Rittman, Crossref Program Lead, has provided additional details about the ongoing issues in our Community Forum: https://community.crossref.org/t/whats-going-on-with-the-rest-api-indexing-issues/14341 - IF

17. identified Aug 22, 2025, 05:35 PM UTC

    We are continuing to work on a fix for this issue. Yesterday Panos on our technical team successfully re-pushed over 700,000 records that were registered in the previous week. So, all records registered up to 2025-August-21 T11:00:00 UTC should now be present in the REST API. - IF

18. monitoring Aug 25, 2025, 01:23 PM UTC

    A fix has been implemented. We will be monitoring the results for a few days before we resolve this incident. -IF

19. resolved Aug 27, 2025, 12:06 PM UTC

    This incident has been resolved. If you are still finding DOIs that have not been indexed in the REST API from July or August 2025 do let our technical support team know at [email protected]. - IF

Read the full incident report →