Crossref incident
REST API Indexing Stalled since April 29th. Impacts on downstream services.
Resolved after 2 days 20 hours, affecting Public REST API and Plus REST API and 1 more, on May 2, 2026.
This issue has been resolved. Missed records have been indexed, and indexing of newly created and updated records has resumed.
Affected components
Update timeline
- 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.
- investigating May 03, 2026, 11:24 PM UTC
We are continuing to investigate this issue.
- 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.
- 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.
- 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.
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.
Amazon Web Services