Crossref incident

Degraded performance on Public and Polite REST API

Minor Resolved View vendor source →

Crossref experienced a minor incident on June 22, 2026 affecting Public REST API and Polite REST API and 1 more component, lasting 1d 23h. The incident has been resolved; the full update timeline is below.

Started
Jun 22, 2026, 10:20 AM UTC
Resolved
Jun 24, 2026, 09:43 AM UTC
Duration
1d 23h
Detected by Pingoru
Jun 22, 2026, 10:20 AM UTC

Affected components

Public REST APIPolite REST APIMetadata searchCrossmark dialog serverPublic content negotiationPolite content negotiation

Update timeline

  1. identified Jun 22, 2026, 10:20 AM UTC

    We are receiving a very large number of requests from a user that is applying various strategies to get around our rate limits on our public REST API pool. This is impacting performance, including on the public and polite REST API pools, Crossmark, content negotiation, Crossref Metadata Search and reference matching. We are investigating solutions.

  2. identified Jun 22, 2026, 11:22 AM UTC

    We are continuing to work on a fix for the performance issue.

  3. monitoring Jun 22, 2026, 11:39 AM UTC

    We have deployed and are monitoring a fix for this issue that affected our APIs and Metadata Search.

  4. monitoring Jun 23, 2026, 09:01 AM UTC

    We experienced a couple of downtimes for the Public REST API at 3:09 and 4:15 UTC due to high rates of requests. We are continuing to implement fixes and are monitoring the degraded performance on the Public and REST APIs.

  5. monitoring Jun 23, 2026, 04:24 PM UTC

    We are continuing to monitor our fixes for any further issues affecting the Public and Private REST APIs, Crossmark, content negotiation, and metadata search.

  6. resolved Jun 24, 2026, 09:43 AM UTC

    This incident has been resolved.