Crossref incident

Error when granting Crossref permission to update ORCID records

Minor Resolved View vendor source →

Crossref experienced a minor incident on January 20, 2025 affecting ORCID Auto-update, lasting 1d 6h. The incident has been resolved; the full update timeline is below.

Started
Jan 20, 2025, 02:10 PM UTC
Resolved
Jan 21, 2025, 08:13 PM UTC
Duration
1d 6h
Detected by Pingoru
Jan 20, 2025, 02:10 PM UTC

Affected components

ORCID Auto-update

Update timeline

  1. investigating Jan 20, 2025, 02:10 PM UTC

    Over the weekend we saw some Sentry errors regarding our ORCID Auto-update push and have had a couple of users report an error when trying to grant permission for Crossref to update their ORCID record. We are investigating (and working with the ORCID team) to determine the root cause and will update here when we have more information.

  2. monitoring Jan 20, 2025, 04:27 PM UTC

    We believe we have fixed the problem with the requests being sent and are now investigating how we can resend any requests which failed to send whilst this service was down.

  3. monitoring Jan 21, 2025, 09:40 AM UTC

    We are continuing to monitor and look into what requests may have been missed and whether they could be resent.

  4. resolved Jan 21, 2025, 08:13 PM UTC

    This incident has been resolved. Requests made to ORCID Auto-update during the period of degraded performance have been handled.