Crossref Status

Identified: 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

Identified: 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

Identified: 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

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

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 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

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

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

Identified: 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

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

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

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

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

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

Identified: 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

Identified: 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

Identified: 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

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

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 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

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

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

Identified: 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

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

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

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

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

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

Resolved: This incident has been resolved.

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

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

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

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

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: 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

Identified: 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

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

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

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

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

Identified: 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

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

Identified: 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

Identified: 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.

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

Identified: 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

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

Monitoring: 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

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

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

Identified: 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.

Identified: 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

Identified: 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

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

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

Identified: 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

Identified: 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

Identified: 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

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

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 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

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

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

Identified: 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

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

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

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

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

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

Resolved: This incident has been resolved.

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

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

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

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

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: 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

Identified: 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

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

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

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

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

Identified: 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

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

Identified: 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

Identified: 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.

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

Identified: 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

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

Monitoring: 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

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

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

Identified: 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.

Identified: 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

Identified: 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

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

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