All Systems Operational

Uptime over the past 90 days. View historical uptime.
APIs Operational
Public REST API ? Operational
Polite REST API ? Operational
OAI-PMH ? Operational
XML API ? Operational
Event Data Query API ? Operational
OpenURL ? Operational
Crossmark dialog server ? Operational
Public content negotiation ? Operational
Polite content negotiation ? Operational
Metadata Plus Operational
Plus REST API ? Operational
Plus OAI-PMH ? Operational
XML Snapshots ? Operational
JSON Snapshots ? Operational
Plus content negotiation ? Operational
Key Manager ? Operational
Content Registration Operational
Admin tool ? Operational
Test admin tool ? Operational
Web deposit form ? Operational
Record registration form ? Operational
Metadata files Operational
Open Funder Registry ? Operational
Retraction Watch ? Operational
Annual public data files ? Operational
Sites Operational
Crossref website ? Operational
Crossref support ? Operational
Metadata search ? Operational
Participation reports ? Operational
Integrations and external dependencies Operational
90 days ago
100.0 % uptime
Today
Handle servers ? Operational
Monitoring of iThenticate can be seen at https://turnitin.statuspage.io. Operational
AWS cloudfront Operational
ORCID Auto-update ? Operational
90 days ago
100.0 % uptime
Today
Meta Operational
deliberately-unreliable server ? Operational
Demo Auth ? Operational
Beta Operational
Metadata Manager ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

System Metrics Month Week Day
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
Public Content Negotiation Response Time
Fetching
Public Content Negotiation Uptime
Fetching
Polite Content Negotiation Response Time
Fetching
Polite Content Negotiation Uptime
Fetching
Plus Content Negotiation Response Time
Fetching
Plus Content Negotiation Uptime
Fetching
Crossmark Response Time
Fetching
Crossmark Uptime
Fetching
Event Data Query API Response Time
Fetching
Event Data Query API Uptime
Fetching
Crossref Metadata Search Response Time
Fetching
Apr 21, 2025

No incidents reported today.

Apr 20, 2025

No incidents reported.

Apr 19, 2025

No incidents reported.

Apr 18, 2025

No incidents reported.

Apr 17, 2025

No incidents reported.

Apr 16, 2025

No incidents reported.

Apr 15, 2025
15 April - weekly maintenance - release v0.233.0
Completed - The scheduled maintenance has been completed.
Apr 15, 15:24 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 15, 14:00 UTC
Scheduled - We will be undergoing scheduled maintenance - release version 0.233.0 - on 15 April from 1400 to 1600 UTC. Our members may experience delays in deposit system admin tool (doi.crossref.org) processing. Deposits submitted during this time will be stored and processed after the maintenance has been completed.
Apr 14, 13:24 UTC
Apr 14, 2025

No incidents reported.

Apr 13, 2025

No incidents reported.

Apr 12, 2025

No incidents reported.

Apr 11, 2025

No incidents reported.

Apr 10, 2025
Slower submission processing at doi.crossref.org
Postmortem - Read details
Apr 16, 17:04 UTC
Resolved - This incident has been resolved. We continue to work on a post-mortem, and will share it when it's available. -IF
Apr 10, 13:54 UTC
Update - We are no longer seeing lags with processing of submissions and queries in our queue (doi.crossref.org). That said, we continue to monitor the performance of the queue, while we work on that post-mortem. -IF
Apr 9, 19:55 UTC
Monitoring - We believe a fix has been found and implemented; everything is flowing far faster now. We will monitor the results for a bit longer and share a post-mortem soon.
-GH
Apr 9, 11:29 UTC
Identified - We believe we have identified the underlying issue that has been causing submission processing lags. We're working on a fix. -IF
Apr 8, 20:30 UTC
Update - We are continuing to investigate this issue.
Apr 7, 21:45 UTC
Update - We're still focused on speeding up slow deposit and query processing in the submission queue. Some progress was made over the weekend so things are looking better; more details soon.
-GH
Apr 6, 10:14 UTC
Update - We are continuing to investigate this issue.
Apr 4, 19:08 UTC
Update - Our technical team continues to investigate the cause of these performance lags. -IF
Apr 3, 21:31 UTC
Update - We are continuing to investigate this issue.
Apr 2, 20:43 UTC
Investigating - We reverted additional code earlier today during our weekly release in an attempt to pinpoint the origin of the performance lags in the submission and query queues at doi.crossref.org. Unfortunately, this did not result in a return to the processing speeds that we saw prior to 18 March. We have enabled additional processing threads for submissions and queries and continue to investigate the source of the lags. -IF
Apr 1, 19:02 UTC
Update - We are continuing to monitor for any further issues.
Mar 31, 17:07 UTC
Update - The emergency maintenance has now been completed. We have dedicated additional resources to drive down the backlog of pending submissions and queries in the queue at doi.crossref.org. -IF

Our changes have improved performance. We continue to monitor the results.
Mar 29, 14:37 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 29, 13:58 UTC
Identified - We will be conducting emergency, unplanned maintenance tomorrow, Saturday, 29 March, from 11:00 to 14:00 UTC in order to address the slow processing times and a growing submission and query queue size. More details here: https://status.crossref.org/incidents/nxp3kkx4xxs3
Mar 28, 17:51 UTC
Investigating - Unfortunately, today's special release has not resolved the issue. We're continuing to investigate the cause of the performance lags in the submission queue - doi.crossref.org. Resolving these lags is our technical team's highest priority. -IF
Mar 27, 17:42 UTC
Update - We will be performing special maintenance - release v0.231.0 - tomorrow, 27 March, to try to further improve submission processing performance. -IF
Mar 26, 19:56 UTC
Update - Our change yesterday improved performance in the submission queue - doi.crossref.org - for several hours, but we're seeing lags again today. We're investigating other potential causes of this issue. -IF
Mar 26, 13:20 UTC
Update - The deployment earlier today did not fix the performance lags in our submission queue - doi.crossref.org. Our technical team has reverted a change that they believe is responsible for the lags. We're monitoring the results. -IF
Mar 25, 17:38 UTC
Monitoring - We have observed slower processing times in our submission queue - doi.crossref.org - during the last few days. We've exceeded 50,000+ pending submissions at the moment. We're still processing your submissions. We're hopeful that today's deployment will fix the performance lags. We're monitoring the issue. -IF
Mar 25, 14:13 UTC
Apr 9, 2025
Apr 8, 2025
8 April - weekly maintenance - release v0.232.0
Completed - The scheduled maintenance has been completed.
Apr 8, 15:11 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 8, 14:00 UTC
Scheduled - We will be undergoing scheduled maintenance - release v0.232.0 - on 8 April from 1400 to 1600 UTC. Our members may experience delays in deposit system admin tool (doi.crossref.org) processing. Deposits submitted during this time will be stored and processed after the maintenance has been completed.
Apr 8, 12:30 UTC
Apr 7, 2025
← Incident History Powered by Atlassian Statuspage