Crossref incident
Crossref DOIs not resolving/ DOI registration failing
Resolved after 12 hours 6 minutes, on March 17, 2026.
This incident has been resolved. All affected metadata submissions have now been reprocessed.
Update timeline
- investigating Mar 17, 2026, 07:56 AM UTC
Crossref DOIs have not been resolving as expected since around 06:56 UTC. Any attempt to resolve them returns the error message: “DOI Cannot Connect to Server.” We are currently investigating the issue.
- investigating Mar 17, 2026, 09:45 AM UTC
UPDATE: Crossref DOIs have not been resolving as expected since around 06:56 UTC. Any attempt to resolve them returns the error message: “DOI Cannot Connect to Server.” Some DOI registrations are impacted too. We are closely working with the DOI Foundation on a fix.
- identified Mar 17, 2026, 10:35 AM UTC
The DOI Foundation identified the issue as a surge in traffic affecting the backend infrastructure of doi.org. This has been resolved. Crossref registration servers have been restarted, and metadata registrations are now processing successfully.
- monitoring Mar 17, 2026, 10:38 AM UTC
We continue to monitor the system to ensure stability and consistent processing of registrations.
- resolved Mar 17, 2026, 08:03 PM UTC
This incident has been resolved. All affected metadata submissions have now been reprocessed.
Your product runs on more than Crossref
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.