All Systems Operational
APIs Operational
90 days ago
99.85 % uptime
Today
Public REST API ? Operational
90 days ago
98.68 % uptime
Today
Polite REST API ? Operational
90 days ago
100.0 % uptime
Today
Plus REST API ? Operational
90 days ago
100.0 % uptime
Today
OAI-PMH ? Operational
90 days ago
100.0 % uptime
Today
Plus 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
Sites Operational
90 days ago
99.97 % uptime
Today
Crossref website ? Operational
90 days ago
100.0 % uptime
Today
Crossref support ? Operational
90 days ago
100.0 % uptime
Today
Metadata search ? Operational
90 days ago
99.92 % uptime
Today
Content Registration Operational
90 days ago
99.97 % uptime
Today
Deposit system ? Operational
90 days ago
99.95 % uptime
Today
Test deposit system ? Operational
90 days ago
100.0 % 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
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
99.98 % uptime
Today
Participation Reports ? Operational
90 days ago
100.0 % uptime
Today
Event Data Query API ? Operational
90 days ago
100.0 % uptime
Today
Metadata Manager ? Operational
90 days ago
99.95 % 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
Apr 22, 2019

No incidents reported today.

Apr 21, 2019

No incidents reported.

Apr 20, 2019

No incidents reported.

Apr 19, 2019

No incidents reported.

Apr 18, 2019

No incidents reported.

Apr 17, 2019
Resolved - This incident has been resolved. We'll continue to monitor. We're working on reprocessing the affected submissions.
Apr 17, 21:03 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 17, 19:35 UTC
Identified - We have identified a problem with the processing of deposits containing unstructured references. For now, most deposits with unstructured references are not processing the full citation list. We're working to resolve the problem and will reprocess affected submissions as soon as a fix is in place.
Apr 17, 17:42 UTC
Apr 16, 2019
Resolved - We replaced the affected hardware on 5 April and have been monitoring the replacement since. Luckily, there have been no issues with the new hardware since. Thus, this incident has been resolved. All affected services are fully operational.
Apr 16, 16:36 UTC
Update - We've been unable to get the affected machine back to full health, so we're working on a replacement. We'll keep you updated as to our progress. Metadata Search performance remains degraded.
Mar 29, 20:34 UTC
Update - We have more work to do to resolve these hardware issues, but we're done for today. Performance of our metadata search is still degraded. All other services are operational.
Mar 29, 01:51 UTC
Update - We're continuing our work on the hardware issues from yesterday. Our efforts to move affected systems to auxiliary hardware while we troubleshoot has resulted in a stable day for our services. That said, more work continues and users may experience degraded performance as a result. We're monitoring.
Mar 28, 20:45 UTC
Update - We're still working to get this fully resolved. Users may experience degraded performance from Crossref Metadata Search, as we continue or work.
Mar 27, 18:54 UTC
Monitoring - A temporary fix has been implemented - affected systems have been moved to auxiliary hardware - and are currently operational. We're monitoring and will be performing additional work later today, so users may experience additional disruptions as we work toward a permanent fix.
Mar 27, 17:09 UTC
Identified - The issue has been identified and we are working on a fix, as part of this fix we are having to redirect some of our services. Users may experience degraded performance with the deposit system, Metadata Manager, and our APIs.
Mar 27, 14:28 UTC
Update - We are continuing to investigate this issue.
Mar 27, 09:36 UTC
Investigating - The hardware problems we experienced yesterday are continuing. The deposit system may be unstable and/or working in a degraded state until we are able to fix or replace the hardware.
Mar 27, 09:17 UTC
Completed - The scheduled maintenance has been completed.
Apr 16, 14:32 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 16, 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.
Apr 15, 15:48 UTC
Apr 15, 2019
Resolved - Some deposits made by members using our web deposit form (https://www.crossref.org/webDeposit/) failed between 16:30 UTC yesterday and 11:30 UTC today. This was due to a problem with a release we made to improve the security on the form. We’ve backed out the release and will be testing it further. If you received an email saying that your web deposit form submission failed during this time, and the message you received was "cvc-complex-type.2.3: Element ‘journal’ cannot have character [children]" or similar, please do complete the form again with your submission. We're really sorry for the inconvenience.
Apr 15, 16:30 UTC
Apr 14, 2019

No incidents reported.

Apr 13, 2019

No incidents reported.

Apr 12, 2019

No incidents reported.

Apr 11, 2019
Resolved - We had a configuration problem with our deposit system, which we have fixed. The problem resulted in a few deposits processing more slowly than usual.
Apr 11, 13:54 UTC
Investigating - We are currently investigating a problem with the deposit system. Members may continue to submit deposits, but there will be a delay in processing while we determine the cause.
Apr 11, 13:18 UTC
Apr 10, 2019
Resolved - This incident has been resolved.
Apr 10, 13:53 UTC
Identified - As a result of Friday's (5 April) incident - http://status.crossref.org/incidents/vbr448x8vtm0 - we learned that content negotiation is broken for all those Elsevier DOIs that were being used to test the prototype service (distributed usage logging) endpoints. We have identified a fix and are working with CNRI on implementation.
Apr 9, 01:30 UTC
Apr 9, 2019
Completed - The scheduled maintenance has been completed.
Apr 9, 14:51 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 9, 14:25 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.
Apr 8, 17:12 UTC
Apr 8, 2019
Resolved - We originally reported that thousands of DOIs under prefix 10.1016 that were being used to test a prototype service (distributed usage logging) were not resolving at all. These DOIs are now resolving. There is a related issue with content negotiation for these DOIs that we are still working to fix, but we have corrected the original incident of the 10.1016 DOIs not resolving.
Apr 8, 13:59 UTC
Update - We have an update on this incident: The DOI resolution should be fixed where it was broken. And, future deposits will not result in the same breakage, as we saw with this incident. Content negotiation is broken for all those Elsevier DOIs that were being used to test the prototype service (distributed usage logging) endpoints. We will look into fixing the content negotiation next week with the help of CNRI. Enjoy the weekend. We'll have more on this soon.
Apr 5, 21:30 UTC
Identified - We think we have isolated the issue to records that were being used for testing a prototype service (distributed usage logging). We have a plan in place to fix these and will update soon.
Apr 5, 17:46 UTC
Investigating - There is an issue where possibly tens of thousands of DOIs under prefix 10.1016 (an Elsevier prefix) are not resolving at all. Anyone clicking on these links are getting errors. We are investigating and will follow up with updates as we find out more.
Apr 5, 09:42 UTC