Crossref Status

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor our fixes for any further issues affecting the Public and Private REST APIs, Crossmark, content negotiation, and metadata search.

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

Monitoring: We have deployed and are monitoring a fix for this issue that affected our APIs and Metadata Search.

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

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

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor our fixes for any further issues affecting the Public and Private REST APIs, Crossmark, content negotiation, and metadata search.

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

Monitoring: We have deployed and are monitoring a fix for this issue that affected our APIs and Metadata Search.

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

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

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor our fixes for any further issues affecting the Public and Private REST APIs, Crossmark, content negotiation, and metadata search.

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

Monitoring: We have deployed and are monitoring a fix for this issue that affected our APIs and Metadata Search.

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

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

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor our fixes for any further issues affecting the Public and Private REST APIs, Crossmark, content negotiation, and metadata search.

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

Monitoring: We have deployed and are monitoring a fix for this issue that affected our APIs and Metadata Search.

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

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

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor our fixes for any further issues affecting the Public and Private REST APIs, Crossmark, content negotiation, and metadata search.

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

Monitoring: We have deployed and are monitoring a fix for this issue that affected our APIs and Metadata Search.

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

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

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor our fixes for any further issues affecting the Public and Private REST APIs, Crossmark, content negotiation, and metadata search.

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

Monitoring: We have deployed and are monitoring a fix for this issue that affected our APIs and Metadata Search.

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

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