All Systems Operational

APIs Operational
Public REST API ? Operational
Polite REST API ? Operational
OAI-PMH ? Operational
XML API ? Operational
Event Data Query API ? Operational
OpenURL ? Operational
Crossmark dialog server ? Operational
Public content negotiation ? Operational
Polite content negotiation ? Operational
Metadata Plus Operational
Plus REST API ? Operational
Plus OAI-PMH ? Operational
XML Snapshots ? Operational
JSON Snapshots ? Operational
Plus content negotiation ? Operational
Key Manager ? Operational
Content Registration Operational
Admin tool ? Operational
Test admin tool ? Operational
Web deposit form ? Operational
Record registration form ? Operational
Metadata files Operational
Open Funder Registry ? Operational
Retraction Watch ? Operational
Annual public data files ? Operational
Sites Operational
Crossref website ? Operational
Crossref support ? Operational
Metadata search ? Operational
Participation reports ? Operational
Integrations and external dependencies Operational
90 days ago
100.0 % uptime
Today
Handle servers ? Operational
Monitoring of iThenticate can be seen at https://turnitin.statuspage.io. Operational
AWS cloudfront Operational
ORCID Auto-update ? Operational
90 days ago
100.0 % uptime
Today
Meta Operational
deliberately-unreliable server ? Operational
Demo Auth ? Operational
Beta Operational
Metadata Manager ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Public REST API Response Time
Fetching
Public REST API Uptime
Fetching
Polite REST API Response Time
Fetching
Polite REST API Uptime
Fetching
Plus REST API Response Time
Fetching
Plus REST API Uptime
Fetching
Plus OAI-PMH Response Time
Fetching
Plus OAI-PMH Uptime
Fetching
OpenURL Response Time
Fetching
OpenURL Uptime
Fetching
Public Content Negotiation Response Time
Fetching
Public Content Negotiation Uptime
Fetching
Polite Content Negotiation Response Time
Fetching
Polite Content Negotiation Uptime
Fetching
Plus Content Negotiation Response Time
Fetching
Plus Content Negotiation Uptime
Fetching
Crossmark Response Time
Fetching
Crossmark Uptime
Fetching
Event Data Query API Response Time
Fetching
Event Data Query API Uptime
Fetching
Crossref Metadata Search Response Time
Fetching
Sep 3, 2025

No incidents reported today.

Sep 2, 2025
Completed - The scheduled maintenance has been completed.
Sep 2, 14:20 UTC
Verifying - Verification is currently underway for the maintenance items.
Sep 2, 14:18 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 2, 14:00 UTC
Scheduled - We will be undergoing scheduled maintenance - release version 0.248.0 - on Tuesday, 2 September from 1400 to 1600 UTC. Our members may experience delays in deposit system admin tool (doi.crossref.org) processing. Deposits submitted during this time will be stored and processed after the maintenance has been completed.
Aug 29, 19:11 UTC
Sep 1, 2025

No incidents reported.

Aug 31, 2025

No incidents reported.

Aug 30, 2025

No incidents reported.

Aug 29, 2025

No incidents reported.

Aug 28, 2025

No incidents reported.

Aug 27, 2025
Resolved - This incident has been resolved. -IF
Aug 27, 13:16 UTC
Update - A fix has been implemented. We will be monitoring the results for a few days before we resolve this incident. -IF
Aug 25, 13:24 UTC
Update - We are continuing to monitor for any further issues.
Aug 20, 12:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 19, 19:45 UTC
Identified - The issue has been identified and a fix is being implemented. >EA
Aug 19, 13:56 UTC
Investigating - We have noted performance-related issues with Participation Reports. We are investigating the underlying cause. >EA
Aug 19, 09:39 UTC
Resolved - This incident has been resolved. -IF
Aug 27, 13:16 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 26, 15:00 UTC
Update - We have confirmed that all notifications for registrations are being delivered and have been since 22 July. A small fraction of query submission email notifications (for very large queries) and forward-link alerts are going undelivered. Our technical team continues to work on a fix. -IF
Aug 8, 17:23 UTC
Update - We are continuing to work on a fix for this issue.
Aug 6, 18:27 UTC
Update - We are continuing to work on a fix for this issue.
Jul 30, 16:07 UTC
Update - We are continuing to work on a fix for this issue.
Jul 25, 20:41 UTC
Update - We are continuing to work on a fix for this issue.
Jul 23, 20:20 UTC
Update - We have resolved the problems for the vast majority of members and those submissions, but we know that a fraction of notifications are failing for very large submissions. We are continuing to work on a fix for this issue. -IF
Jul 22, 19:39 UTC
Update - We are continuing to work on a fix for this issue.
Jul 21, 12:42 UTC
Update - Yesterday's release did fix delivery of notification emails for many submissions, but we still have a small minority of notification emails that are going undelivered. Our technical team continues to work on a fix. -IF
Jul 17, 16:29 UTC
Update - We'll have an emergency, unplanned release (https://status.crossref.org/incidents/c5nyp41k6vx5) in ~20 minutes to address the ongoing errors with delivery of notification emails after registrations.

During that release window - from 1500 to 1700 UTC today - our members may experience delays in deposit system admin tool (doi.crossref.org) processing. Deposits submitted during this time will be stored and processed after the emergency maintenance has been completed.

Jul 16, 14:40 UTC
Update - We are continuing to work on a fix for this issue.
Jul 15, 20:51 UTC
Update - Delivery of email notifications of submission logs following a registration (for Simple Text Query form, web deposit form, and XML submissions) has been restored for many members and their submissions. We are working to remedy the other outstanding errors that are causing some email notifications to go undelivered. -IF
Jul 14, 17:42 UTC
Identified - Delivery of email notifications of submission logs following a registration (for Simple Text Query form, web deposit form, and XML submissions) began failing again late yesterday. Our technical team continues to work on a fix. -IF
Jul 12, 15:20 UTC
Update - Submissions from Metadata Manager and the Simple Text Query form have been restored. Unfortunately, delivery of email notifications of submission logs following a registration (for Simple Text Query form, web deposit form, and XML submissions) do appear to be delayed. We believe this is due to the volume of notification emails in the system, and the result of quite a backlog there. We are monitoring. -IF
Jul 11, 21:16 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 11, 15:22 UTC
Update - We are continuing to work on a fix for this issue.
Jul 11, 14:08 UTC
Update - We'll have an emergency, unplanned release (https://status.crossref.org/incidents/1c42q5j29ds2) in ~30 minutes to address the ongoing issues with Metadata Manager and newly reported errors with delivery of notification emails after registrations.

During that release window - from 1430 to 1630 today - our members may experience delays in deposit system admin tool (doi.crossref.org) processing. Deposits submitted during this time will be stored and processed after the emergency maintenance has been completed.

Jul 11, 14:08 UTC
Update - Errors to Crossmark dialog boxes have been fixed, as you can see with this example: https://crossmark.crossref.org/dialog/?doi=10.36676/girt.v12.i1.109&domain=pdf

We're continuing to work on Metadata Manager and the Simple Text Query form. -IF

Jul 10, 20:36 UTC
Update - We are continuing to work on a fix for the errors present with Metadata Manager registrations. We have also identified errors with reference registrations via the Simple Text Query form (https://apps.crossref.org/SimpleTextQuery/) and errors in the display of Crossmark dialog boxes (e.g., https://crossmark.crossref.org/dialog/?doi=10.3233/JIFS-179309&domain=pdf). -IF
Jul 10, 19:21 UTC
Identified - The issue has been identified and we continue to work on a fix for Metadata Manager registrations that are failing with the 'TypeError' error messages. We have deployed a fix for the depositor reports. That issue is resolved (e.g., https://data.crossref.org/depositorreport?pubid=J458872). -IF
Jul 10, 14:08 UTC
Investigating - As a result of our recent AWS migration (https://status.crossref.org/incidents/s92nm4xn1w84), Metadata Manager submissions are currently returning 'TypeError' error messages and our depositor reports are returning a 404 'Not Found' status code error message. Our technical team is working on a fix. -IF
Jul 10, 03:19 UTC
Resolved - 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 support@crossref.org. - IF
Aug 27, 12:06 UTC
Monitoring - A fix has been implemented. We will be monitoring the results for a few days before we resolve this incident. -IF
Aug 25, 13:23 UTC
Update - 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
Aug 22, 17:35 UTC
Update - 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
Aug 20, 17:47 UTC
Update - 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 - support@crossref.org - in order for us to investigate further. Our technical team continues to actively work on a fix. -IF
Aug 18, 14:15 UTC
Update - 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
Aug 15, 21:38 UTC
Update - 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
Aug 14, 19:19 UTC
Update - 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
Aug 13, 19:26 UTC
Identified - 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
Aug 11, 18:14 UTC
Update - We are continuing to monitor for any further issues.
Aug 6, 18:21 UTC
Update - 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
Aug 4, 13:21 UTC
Monitoring - 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
Jul 30, 19:20 UTC
Update - We are continuing to work on a fix for this issue.
Jul 30, 16:03 UTC
Update - 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
Jul 28, 18:46 UTC
Update - We are continuing to work on a fix for this issue.
Jul 25, 20:41 UTC
Update - We are continuing to work on a fix for this issue.
Jul 23, 20:20 UTC
Update - We are continuing to work on a fix for this issue.
Jul 22, 19:37 UTC
Identified - The issue has been identified and a fix is being implemented.
Jul 22, 13:23 UTC
Investigating - 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
Jul 21, 12:45 UTC
Aug 26, 2025
Completed - The scheduled maintenance has been completed.
Aug 26, 14:38 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 26, 14:00 UTC
Scheduled - We will be undergoing scheduled maintenance - release version 0.247.0 - on Tuesday, 26 August from 1400 to 1600 UTC. Our members may experience delays in deposit system admin tool (doi.crossref.org) processing. Deposits submitted during this time will be stored and processed after the maintenance has been completed.
Aug 25, 23:50 UTC
Aug 25, 2025
Resolved - This incident has been resolved.
Aug 25, 13:24 UTC
Investigating - 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
Aug 22, 14:47 UTC
Aug 24, 2025

No incidents reported.

Aug 23, 2025

No incidents reported.

Aug 22, 2025
Aug 21, 2025

No incidents reported.

Aug 20, 2025