Crossref Outage History

Crossref is up right now

Crossref had 49 outages in the last 2 years totaling 2304h 24m of downtime — averaging 2 incidents per month.

There were 49 Crossref outages since September 23, 2024 totaling 2304h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.crossref.org

Major June 16, 2026

Investigating an outage

Detected by Pingoru
Jun 16, 2026, 08:15 AM UTC
Resolved
Jun 16, 2026, 11:59 AM UTC
Duration
3h 44m
Affected: Participation reportsWeb deposit form
Timeline · 3 updates
  1. investigating Jun 16, 2026, 08:15 AM UTC

    We are investigating an incident with multiple tools and services including: - Web deposit form (https://apps.crossref.org/webDeposit) - Participation Reports (https://crossref.org/members/prep/) - Browsable title list (https://www.crossref.org/titleList/) - Other reports and forms under crossref.org Starting from around 04.16am UTC on 16 June, users attempting to access these tools have been receiving 503 errors. Our technical team are investigating. We'll provide updates as soon as we know more.

  2. monitoring Jun 16, 2026, 08:41 AM UTC

    A fix has been implemented. The services are available again and working as expected. We are now monitoring their performance and continuing to investigate the cause of the incident.

  3. resolved Jun 16, 2026, 11:59 AM UTC

    Participation Reports, the web deposit form, and other small apps and reports have been fully operational again since about 08.30am UTC.

Read the full incident report →

Notice June 10, 2026

DOI Error Reports (Non-registered DOIs reported by end users for prefix…) were not sent between May 11th and June 10th 2026

Detected by Pingoru
Jun 10, 2026, 06:25 PM UTC
Resolved
May 11, 2026, 04:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 10, 2026, 06:25 PM UTC

    Due to a configuration change, we stored, but did not send out, DOI Error Reports starting on May 11th 2026. The problem was reported, identified, and a fix was implemented, on June 10th 2026. All DOI Error Reports from the outage period are intact and will be emailed shortly.

Read the full incident report →

Minor May 29, 2026

Degraded service on REST API

Detected by Pingoru
May 29, 2026, 12:12 PM UTC
Resolved
Jun 05, 2026, 05:50 PM UTC
Duration
7d 5h
Affected: Public REST APIPlus REST APIPolite REST API
Timeline · 4 updates
  1. investigating May 29, 2026, 12:12 PM UTC

    We are experiencing delays in updating some metadata fields on the REST API. This includes citation counts, Retraction Watch retractions, aliased DOIs, and metadata in the member, journal, and funder routes. We are currently investigating the cause.

  2. monitoring May 29, 2026, 02:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Jun 01, 2026, 04:11 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 05, 2026, 05:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

Bug identified, possibly resulting in failed submissions. Emergency maintenance scheduled.

Detected by Pingoru
May 08, 2026, 04:59 PM UTC
Resolved
May 08, 2026, 07:38 PM UTC
Duration
2h 38m
Affected: Admin toolTest admin toolWeb deposit formNew Metadata Manager
Timeline · 5 updates
  1. investigating May 08, 2026, 04:59 PM UTC

    We have identified a bug in our system which may result in failing submissions at this time. An emergency release is scheduled for approximately 1900 UTC with a fix. During the release, our members may experience delays in deposit system admin tool (doi.crossref.org) processing. Deposits submitted during that time will be stored and processed after the maintenance has been completed.

  2. investigating May 08, 2026, 06:39 PM UTC

    We are continuing to investigate this issue.

  3. identified May 08, 2026, 07:01 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring May 08, 2026, 07:04 PM UTC

    Emergency release version 0.274.2 has been released. We are monitoring the results.

  5. resolved May 08, 2026, 07:38 PM UTC

    This incident has been resolved and the emergency maintenance has been completed.

Read the full incident report →

Minor May 4, 2026

April 2026 JSON Snapshot is missing data for records created or updated on 4/29 and 4/30

Detected by Pingoru
May 04, 2026, 01:45 PM UTC
Resolved
May 07, 2026, 12:34 PM UTC
Duration
2d 22h
Affected: JSON Snapshots
Timeline · 3 updates
  1. identified May 04, 2026, 01:45 PM UTC

    Due to problems with API indexing that occurred between 4/29 and 5/3, the current JSON snapshot for April 2026 is missing 1-2 days of data. We've resolved the indexing issue and are currently re-pushing the missing records into the API. Once that's completed, over the next few days, we'll build and release a new snapshot for April.

  2. identified May 05, 2026, 12:38 PM UTC

    The corrected JSON snapshot is in process. It will be completed and available in the next 2-3 days.

  3. resolved May 07, 2026, 12:34 PM UTC

    The corrected April 2026 JSON snapshot has been released.

Read the full incident report →

Notice May 3, 2026

Submission processing delayed on Sunday, 3 May

Detected by Pingoru
May 03, 2026, 11:34 PM UTC
Resolved
May 03, 2026, 11:00 AM UTC
Duration
Timeline · 1 update
  1. resolved May 03, 2026, 11:34 PM UTC

    Submission processing within our admin tool - doi.crossref.org - stalled and was therefore delayed between 10:56 and 20:57 UTC Sunday, 3 May. This issue has been fixed and submissions are again being processed. No submissions were lost during the processing delay; we stored all of those submissions in our system and began processing them at 20:57 UTC. There are no delays currently. -IF

Read the full incident report →

Minor May 2, 2026

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

Detected by Pingoru
May 02, 2026, 04:37 PM UTC
Resolved
May 05, 2026, 12:39 PM UTC
Duration
2d 20h
Affected: Public REST APIPlus REST APIPolite REST APICrossmark dialog serverPublic content negotiationPolite content negotiation
Timeline · 5 updates
  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.

Read the full incident report →

Notice April 21, 2026

31 March - test system - test.crossref.org - migration resulted in some members temporarily losing access and test notification callbacks being misrouted

Detected by Pingoru
Apr 21, 2026, 09:19 PM UTC
Resolved
Mar 31, 2026, 09:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 21, 2026, 09:19 PM UTC

    On 31 March, we migrated our test system - test.crossref.org - and brought it into sync with our production admin tool - doi.crossref.org. As a result of that migration, access to some of the test accounts was temporarily lost. In addition, members with notification callbacks enabled in test may have noticed that test callbacks were being misrouted to the endpoints set up for your production callbacks. We have since fixed both issues. If you're a test system user who is experiencing any issues today, do contact us at [email protected] so we can investigate and assist. - IF

Read the full incident report →

Critical April 17, 2026

Main website down between 05:46 UTC and 06:47 UTC

Detected by Pingoru
Apr 17, 2026, 06:32 AM UTC
Resolved
Apr 17, 2026, 10:23 AM UTC
Duration
3h 51m
Affected: Crossref website
Timeline · 3 updates
  1. investigating Apr 17, 2026, 06:32 AM UTC

    The main Crossref website (www.crossref.org) has been down since 05:46 UTC. We are investigating the cause of the issue.

  2. monitoring Apr 17, 2026, 07:04 AM UTC

    The website is available again. We are monitoring the situation.

  3. resolved Apr 17, 2026, 10:23 AM UTC

    From 05:46 UTC on 17 April we experienced a sustained surge of traffic to our website, which was caused by bot activity distributed across multiple IP addresses. The service recovered automatically without intervention after about an hour, and we have since applied tighter rate-limiting to the source. We are also reviewing options to further improve the scalability and resilience of the service going forward.

Read the full incident report →

Notice April 3, 2026

Depositor reports returning gateway timeout errors

Detected by Pingoru
Apr 03, 2026, 06:31 PM UTC
Resolved
Apr 03, 2026, 06:37 PM UTC
Duration
6m
Timeline · 3 updates
  1. investigating Apr 03, 2026, 06:31 PM UTC

    Our depositor reports (e.g., https://data.crossref.org/depositorreport?pubid=J533343) are returning status code 504 gateway timeout errors. We're aware of the issue and our technical team is investigating. -IF

  2. monitoring Apr 03, 2026, 06:35 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 03, 2026, 06:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 30, 2026

Failures downloading the 2026 public data file via Academic Torrents

Detected by Pingoru
Mar 30, 2026, 03:13 PM UTC
Resolved
Mar 30, 2026, 03:13 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 30, 2026, 03:13 PM UTC

    The 2026 public data file was stalling during download via Academic Torrents (https://academictorrents.com/details/b5ee0e102689b3e67023dd024694c0f5f124646f) for the last few days due to an issue with the number of available sources. We have addressed the issue and downloads should now be completing with no stalling/delays.

Read the full incident report →

Notice March 24, 2026

Crossref Resolution Reports unavailable

Detected by Pingoru
Mar 24, 2026, 09:41 AM UTC
Resolved
Mar 24, 2026, 10:49 AM UTC
Duration
1h 8m
Timeline · 2 updates
  1. investigating Mar 24, 2026, 09:41 AM UTC

    Crossref Resolution Reports (https://www.crossref.org/06members/51depositor.html) are currently unavailable. We will provide an update as soon as we have further information.

  2. resolved Mar 24, 2026, 10:49 AM UTC

    Resolution reports were unavailable from around 02:28 UTC to 09:42 UTC, due to the server running out of memory. We have rebooted the server and the service is now available again.

Read the full incident report →

Notice March 17, 2026

Crossref DOIs not resolving/ DOI registration failing

Detected by Pingoru
Mar 17, 2026, 07:56 AM UTC
Resolved
Mar 17, 2026, 08:03 PM UTC
Duration
12h 6m
Timeline · 5 updates
  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.

Read the full incident report →

Notice February 26, 2026

Website down for ≈ 20 minutes, on 25-02-2026

Detected by Pingoru
Feb 26, 2026, 11:14 AM UTC
Resolved
Feb 25, 2026, 10:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Feb 26, 2026, 11:14 AM UTC

    Yesterday, we experienced a brief website (www.crossref.org) downtime from 10:05 UTC to 10:24 UTC. This issue was resolved, and a temporary fix was implemented to prevent such spontaneous disruptions while we work on a permanent solution. EA

Read the full incident report →

Minor December 16, 2025

Members reporting errors when attempting to update records using the new Metadata Manager

Detected by Pingoru
Dec 16, 2025, 07:17 PM UTC
Resolved
Jan 09, 2026, 03:44 PM UTC
Duration
23d 20h
Affected: New Metadata Manager
Timeline · 4 updates
  1. investigating Dec 16, 2025, 07:17 PM UTC

    We have had members reporting ‘Error Loading Metadata’ failure messages in the new Metadata Manager tool -https://manage.crossref.org/records - when updating existing records. Our technical team is investigating. -IF

  2. identified Dec 16, 2025, 08:55 PM UTC

    The issue has been identified. This bug is only affecting DOIs with more than one /. Those DOIs will continue to trigger the ‘Error Loading Metadata’ failure messages until we fix the issue. -IF

  3. identified Jan 05, 2026, 08:03 PM UTC

    We are continuing to work on a fix for this issue.

  4. resolved Jan 09, 2026, 03:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 16, 2025

Degraded performance in our test admin tool - test.crossref.org

Detected by Pingoru
Dec 16, 2025, 07:11 PM UTC
Resolved
Dec 16, 2025, 10:34 PM UTC
Duration
3h 23m
Affected: Test admin tool
Timeline · 3 updates
  1. investigating Dec 16, 2025, 07:11 PM UTC

    Our test admin tool - test.crossref.org - is experiencing degraded performance at the moment. Author-title and funder searches for deposits are failing and we have a backlog of test submissions that we're working through. Our technical and infrastructure teams are investigating. -IF

  2. monitoring Dec 16, 2025, 08:29 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 16, 2025, 10:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 16, 2025

Crossref Participation Reports unavailable for several hours due to server problem

Detected by Pingoru
Dec 16, 2025, 10:38 AM UTC
Resolved
Dec 16, 2025, 02:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Dec 16, 2025, 10:38 AM UTC

    Our Participation Reports were unavailable from 02:24 UTC until 10:10 UTC due to a problem with their server. Our team has now increased the size of this server and enabled the report to run across more servers. Apologies for the inconvenience if you were trying to check your participation during this time - AB

Read the full incident report →

Major December 11, 2025

Login Issues with iThenticate accounts/Similarity Check

Detected by Pingoru
Dec 11, 2025, 04:41 PM UTC
Resolved
Dec 11, 2025, 05:25 PM UTC
Duration
44m
Affected: Monitoring of iThenticate can be seen at https://turnitin.statuspage.io.
Timeline · 2 updates
  1. investigating Dec 11, 2025, 04:41 PM UTC

    Turnitin has reported that users in Europe may have issues logging into their iThenticate accounts. They are currently investigating the issue. Please see their status for updates: https://turnitin.statuspage.io/incidents/krzh571rxsc2

  2. resolved Dec 11, 2025, 05:25 PM UTC

    This incident has now been resolved by Turnitin. - KL

Read the full incident report →

Minor December 2, 2025

Dropped sessions when adding contributors to Metadata Manager registrations

Detected by Pingoru
Dec 02, 2025, 07:54 PM UTC
Resolved
Jan 02, 2026, 07:06 PM UTC
Duration
30d 23h
Timeline · 2 updates
  1. investigating Dec 02, 2025, 07:54 PM UTC

    Several members have reported that their sessions have been dropped (screen turning white) when attempting to add contributor metadata to their registrations within Metadata Manager - https://www.crossref.org/metadatamanager/. Members facing this issue should register their metadata without contributors and then use the new record registration form - https://manage.crossref.org/records - to import those records so their contributors can be added to the metadata. Please contact our support team - [email protected] - if you have questions. - IF

  2. resolved Jan 02, 2026, 07:06 PM UTC

    We have deprecated - https://www.crossref.org/deprecated/ - our previous Metadata Manager tool. Members who previously made use of Metadata Manager to register their metadata should move to our new form - https://manage.crossref.org/records. Please contact our support team - [email protected] - if you have questions. - IF

Read the full incident report →

Major November 18, 2025

Cloudflare network problems affecting DOI.org resolution

Detected by Pingoru
Nov 18, 2025, 12:51 PM UTC
Resolved
Nov 18, 2025, 08:01 PM UTC
Duration
7h 10m
Affected: Handle servers
Timeline · 4 updates
  1. investigating Nov 18, 2025, 12:51 PM UTC

    Cloudflare network problems are affecting multiple sites, including doi.org resolution, meaning many DOI links are very slow or result in errors. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  2. investigating Nov 18, 2025, 01:12 PM UTC

    The DOI Foundation is also aware: https://doi.statuspage.io/incidents/z0rwt8tqcfsm

  3. resolved Nov 18, 2025, 08:01 PM UTC

    Clouflare reports that the issues are fixed, and DOIF subsequently reports that doi.org resolutions have returned to normal.

  4. postmortem Nov 20, 2025, 08:22 PM UTC

    CNRI has written a postmorterm about how they handled the Cloudflare outage for doi.org: [https://doi.statuspage.io/incidents/z0rwt8tqcfsm](https://doi.statuspage.io/incidents/z0rwt8tqcfsm)

Read the full incident report →

Minor October 27, 2025

Submission log emails not being sent for all registrations

Detected by Pingoru
Oct 27, 2025, 06:10 PM UTC
Resolved
Nov 04, 2025, 03:27 AM UTC
Duration
7d 9h
Affected: Admin tool
Timeline · 4 updates
  1. investigating Oct 27, 2025, 06:10 PM UTC

    We have found that starting on 24th October around 1800 UTC that not all submissions logs are being emailed to our members. Our technical team is investigating. -IF

  2. investigating Oct 27, 2025, 09:04 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 28, 2025, 04:06 PM UTC

    The issue has been identified and a fix is being implemented.

  4. resolved Nov 04, 2025, 03:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 3, 2025

Errors with the Metadata Plus snapshots in the last day

Detected by Pingoru
Oct 03, 2025, 10:18 PM UTC
Resolved
Oct 05, 2025, 03:58 PM UTC
Duration
1d 17h
Affected: JSON Snapshots
Timeline · 2 updates
  1. identified Oct 03, 2025, 10:18 PM UTC

    We had a configuration error on our end with the Metadata Plus snapshots that was resulting in Plus subscribers being unable to retrieve snapshots for yesterday and today. We have fixed that setting and snapshots should again be available to Plus subscribers. The XML snapshots for September has finished uploading and is also available (https://api.crossref.org/snapshots/monthly/2025/09). That configuration error has also caused the JSON snapshots run to fail. We're working on fixing that and will rerun the process once we do. That will delay the JSON snapshots this month, but we expect them to be available by Monday, 6 October. -IF

  2. resolved Oct 05, 2025, 03:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 20, 2025

Admin tool - doi.crossref.org - returning 503 status code error - service unavailable

Detected by Pingoru
Sep 20, 2025, 08:08 PM UTC
Resolved
Sep 21, 2025, 02:07 AM UTC
Duration
5h 59m
Affected: Admin tool
Timeline · 4 updates
  1. investigating Sep 20, 2025, 08:08 PM UTC

    We are currently investigating this issue. -IF

  2. identified Sep 20, 2025, 08:39 PM UTC

    The issue has been identified and a fix is being implemented. -IF

  3. monitoring Sep 20, 2025, 08:59 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 21, 2025, 02:07 AM UTC

    This incident has been resolved.

Read the full incident report →