Crossref incident

Crossref DOIs not resolving/ DOI registration failing

Notice Resolved View vendor source →

Crossref experienced a notice incident on March 17, 2026, lasting 12h 6m. The incident has been resolved; the full update timeline is below.

Started
Mar 17, 2026, 07:56 AM UTC
Resolved
Mar 17, 2026, 08:03 PM UTC
Duration
12h 6m
Detected by Pingoru
Mar 17, 2026, 07:56 AM UTC

Update timeline

  1. 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.

  2. 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.

  3. 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.

  4. monitoring Mar 17, 2026, 10:38 AM UTC

    We continue to monitor the system to ensure stability and consistent processing of registrations.

  5. resolved Mar 17, 2026, 08:03 PM UTC

    This incident has been resolved. All affected metadata submissions have now been reprocessed.