Crossref Status

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

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

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

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

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

Investigating: We are continuing to investigate this issue.

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

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

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

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

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

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

Investigating: We are continuing to investigate this issue.

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

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

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

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

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

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

Investigating: We are continuing to investigate this issue.

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

Resolved: This incident has been resolved.

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

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

Investigating: We are currently investigating this issue. -IF

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

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

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

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

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

Investigating: We are continuing to investigate this issue.

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

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

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

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

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

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

Investigating: We are continuing to investigate this issue.

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