Crossref incident

REST API Indexing Stalled since April 29th. Impacts on downstream services.

Minor Resolved View vendor source →

Crossref experienced a minor incident on May 2, 2026 affecting Public REST API and Plus REST API and 1 more component, lasting 2d 20h. The incident has been resolved; the full update timeline is below.

Started
May 02, 2026, 04:37 PM UTC
Resolved
May 05, 2026, 12:39 PM UTC
Duration
2d 20h
Detected by Pingoru
May 02, 2026, 04:37 PM UTC

Affected components

Public REST APIPlus REST APIPolite REST APICrossmark dialog serverPublic content negotiationPolite content negotiation

Update timeline

  1. investigating May 02, 2026, 04:37 PM UTC

    No newly created records have been index in REST API since 4/29. Our technical team is investigating. Impacts on downstream services such as Crossmark, Participation Reports, Metadata Search, and Co-Access/Multiple Resolution interim pages.

  2. investigating May 03, 2026, 11:24 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 04, 2026, 08:03 AM UTC

    We've resolved the issue. Records are being indexed in the REST API as expected again. This includes the backlog of records that were affected by this incident.

  4. monitoring May 04, 2026, 09:41 AM UTC

    Records are being indexed in the REST API as expected again. This includes the backlog of records that were affected by this incident.

  5. resolved May 05, 2026, 12:39 PM UTC

    This issue has been resolved. Missed records have been indexed, and indexing of newly created and updated records has resumed.