Identified - Email confirmations from our test deposit system (test.crossref.org) are not currently being delivered. We're working on a fix.
May 24, 18:42 UTC
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
APIs Degraded Performance
90 days ago
100.0 % uptime
Today
Public REST API ? Operational
90 days ago
100.0 % uptime
Today
Polite REST API ? Operational
90 days ago
100.0 % uptime
Today
OAI-PMH ? Operational
90 days ago
100.0 % uptime
Today
OpenURL ? Operational
90 days ago
100.0 % uptime
Today
Crossmark dialog server ? Operational
90 days ago
100.0 % uptime
Today
Content negotiation ? Operational
90 days ago
100.0 % uptime
Today
XML API ? Operational
90 days ago
100.0 % uptime
Today
Event Data Query API ? Degraded Performance
90 days ago
100.0 % uptime
Today
Metadata Plus Operational
90 days ago
99.99 % uptime
Today
Plus REST API ? Operational
90 days ago
99.97 % uptime
Today
Plus OAI-PMH ? Operational
90 days ago
100.0 % uptime
Today
XML Snapshots ? Operational
90 days ago
100.0 % uptime
Today
JSON Snapshots ? Operational
90 days ago
100.0 % uptime
Today
Sites Major Outage
90 days ago
99.75 % uptime
Today
Crossref website ? Operational
90 days ago
100.0 % uptime
Today
Crossref support ? Operational
90 days ago
100.0 % uptime
Today
Metadata search ? Major Outage
90 days ago
99.27 % uptime
Today
Content Registration Operational
90 days ago
99.9 % uptime
Today
Deposit system ? Operational
90 days ago
99.9 % uptime
Today
Test deposit system ? Operational
90 days ago
99.9 % uptime
Today
External dependencies Operational
90 days ago
100.0 % uptime
Today
AWS cloudFront ? Operational
90 days ago
100.0 % uptime
Today
Handle servers ? Operational
90 days ago
100.0 % uptime
Today
Similarity Check via iThenticate (Turnitin) status found at turnitin.status.io ? Operational
Meta Operational
90 days ago
100.0 % uptime
Today
deliberately-unreliable server ? Operational
90 days ago
100.0 % uptime
Today
Beta Operational
90 days ago
100.0 % uptime
Today
Participation Reports ? Operational
90 days ago
100.0 % uptime
Today
Metadata Manager ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on 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
Content Negotiation Response Time
Fetching
Content Negotiation Uptime
Fetching
Crossmark Response Time
Fetching
Crossmark Uptime
Fetching
Event Data Query API Response Time
Fetching
Event Data Query API Uptime
Fetching
Past Incidents
Oct 20, 2019

No incidents reported today.

Oct 19, 2019

No incidents reported.

Oct 18, 2019

No incidents reported.

Oct 17, 2019
Resolved - 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
Monitoring - 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
Identified - 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
Oct 16, 2019
Resolved - 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
Identified - 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
Oct 15, 2019

No incidents reported.

Oct 13, 2019

No incidents reported.

Oct 12, 2019

No incidents reported.

Oct 11, 2019
Resolved - This incident has been resolved.
Oct 11, 20:17 UTC
Identified - 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
Oct 10, 2019

No incidents reported.

Oct 9, 2019

No incidents reported.

Oct 8, 2019
Completed - 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
Scheduled - 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
Oct 7, 2019

No incidents reported.

Oct 6, 2019

No incidents reported.