Investigating - We’re still experiencing problems with load on the Event Data service. Users may see their queries time out when using the API. We’re investigating and will confirm when the issue is resolved.
Jul 4, 13:15 UTC
We've been monitoring for 16 hours, and it looks as though the work we've done to block the query.title feature on the REST API has made the REST API and dependent services stable.
Oct 17, 11:23 UTC
We've now put the block in place on the query.title feature of our REST API.
If you’re currently using query.title, please change to query.bibliographic instead.
Oct 16, 18:47 UTC
Important: query.title feature to be blocked on REST API
As users will have noticed, we’ve been having recurring performance issues on the REST API and related services such as Crossref Metadata Search and Content Negotiation. This has been particularly problematic over the last couple of days.
We’ve identified that this is due to the query.title feature on the REST API. Because of the way it's implemented, it seems to be degrading the performance of the REST API on all pools in which it’s used (public, polite and plus). The impact is not only on queries that use query.title but on all other users of the system too.
Because this is causing serious issues for dependent services, we’re planning on taking the step of blocking all use of the query.title feature later today. We’ve tried other fixes as an alternative, but this is the approach that will benefit the greatest number of users who are being affected by the performance issues. We’re aware that this is very short notice, but it’s the one way for us to stabilise the service for all users - the small group using query.title, and all other users too.
If you’re currently using query.title, please change to query.bibliographic instead. This is designed for title matching, so should in fact be a better fit for you.
We will update you when we introduce this change. At this point, anyone using the deprecated query parameter will see an HTTP 400 status code and an explanation.
Oct 16, 17:29 UTC
This issue was caused by use of the query.title feature on the REST API by a few users. Because of the way it's implemented, it seems to be degrading the performance of the REST API on all pools in which it’s used (public, polite and plus) and all related services, including Content Negotiation. We've now put a block on the query.title function and Content Negotiation is now stable - see https://status.crossref.org/incidents/4y45gj63jsp4 for more information.
Oct 16, 19:11 UTC
Our content negotiation service has been sluggish for the past few hours. This seems to be due to heavy usage from a single user. We're working with the relevant user and hope to return the service to normal performance very soon.
Oct 14, 14:09 UTC
This incident has been resolved.
Oct 11, 20:17 UTC
Content negotiation and the Polite and Public REST API have experienced degraded performance for the last two to three hours due to heavy usage. We're working with users of these services to correct the problem.
Oct 11, 17:27 UTC
The scheduled maintenance has been completed.
Oct 8, 14:33 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 8, 14:00 UTC
We will be undergoing scheduled maintenance during this time. Our members may experience delays in deposit system admin (doi.crossref.org) and Metadata Manager (crossref.org/metadatamanager) processing. Deposits submitted during this time will be stored and processed after the maintenance has been completed. You can learn more about all our scheduled releases here: https://gitlab.com/crossref/content_system.
Oct 7, 15:57 UTC