Crossref Outage History

Started Oct 21, 2026, 12:01 PM UTC· resolved Oct 29, 2026, 01:10 AM UTC

1. identified Oct 21, 2026, 12:01 PM UTC

   On 15 September, we updated the method to identify identifiers for funders in metadata. The new matches were not, however, added to the REST API Metadata Plus pool and we did not notice until today (21 October). We have identified the issue and are implementing a fix. The affected time means that these matches are also missing from the most recent JSON snapshot. All data will be back-filled in the REST API and will be included in the next issued snapshot.

2. identified Oct 23, 2026, 12:55 PM UTC

   We are testing a solution for this issue and will post another update once the fix has been deployed.

3. identified Oct 23, 2026, 06:55 PM UTC

   We have implemented a fix and newly updated works include matches of funder names to ROR IDs in the Metadata Plus pool. We are starting to reindex the backlog of records with missing data. We expect the update process to take up to 24 hours.

4. identified Oct 24, 2026, 06:42 AM UTC

   All affected records have been reindexed and we are monitoring the solution.

5. monitoring Oct 24, 2026, 06:42 AM UTC

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

6. monitoring Oct 26, 2026, 03:20 PM UTC

   We are continuing to monitor for any further issues.

7. monitoring Oct 27, 2026, 03:56 PM UTC

   We are continuing to monitor for any further issues.

8. monitoring Oct 28, 2026, 06:02 PM UTC

   We are running some additional tests on our end to be sure that this incident is resolved. For now, while we continue testing and monitoring, we're leaving the incident in the monitoring status. More as we have it. -IF

9. resolved Oct 29, 2026, 01:10 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 16, 2026, 09:35 PM UTC· resolved Oct 19, 2026, 08:20 PM UTC

1. monitoring Oct 16, 2026, 09:35 PM UTC

   The metadata deposit and query processing queue was down for roughly 30 minutes starting around 20:40 UTC. It was brought back online around 21:10 UTC. We are monitoring for any possible ongoing instability.

2. resolved Oct 19, 2026, 08:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 05, 2026, 12:21 PM UTC· resolved Oct 05, 2026, 04:25 PM UTC

1. investigating Oct 05, 2026, 12:21 PM UTC

   Request to the Metadata Plus pool of the REST API are receiving 401 responses (access denied). We are investigating the cause.

2. investigating Oct 05, 2026, 12:41 PM UTC

   The API is back up but we are still investigating and monitoring.

3. investigating Oct 05, 2026, 12:49 PM UTC

   We are continuing the investigate the outage. The Plus pool was down between 12:00 and 12:36 on 5 Oct, 2026.

4. monitoring Oct 05, 2026, 01:01 PM UTC

   A fix has been implemented and we are continuing to monitor the performance of the Metadata Plus pool.

5. resolved Oct 05, 2026, 04:25 PM UTC

   We have identified the problem due to a bug in a deployment. The deployment was reversed and the Plus pool of the API is working normally again.

Read the full incident report →

Started Oct 04, 2026, 11:30 AM UTC· resolved Oct 05, 2026, 12:49 PM UTC

1. investigating Oct 04, 2026, 11:30 AM UTC

   The test admin system has been down since about 09:30 UTC, so members will see a 503 Service Unavailable message when visiting test.crossref.org. We're investigating. -GH

2. monitoring Oct 04, 2026, 01:18 PM UTC

   The test server ran out of memory and stopped responding; we restarted it, and it's working again. If you had problems depositing or querying in the test system during this time, please try again. We'll monitor. -GH

3. monitoring Oct 04, 2026, 01:18 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Oct 05, 2026, 12:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 27, 2026, 01:22 AM UTC· resolved Sep 27, 2026, 01:45 AM UTC

1. investigating Sep 27, 2026, 01:22 AM UTC

   Our test admin tool is down at the moment. Members are receiving a 503 service unavailable message when trying to access test.crossref.org. -IF

2. monitoring Sep 27, 2026, 01:38 AM UTC

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

3. resolved Sep 27, 2026, 01:45 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 21, 2026, 02:57 AM UTC· resolved Sep 21, 2026, 09:18 AM UTC

1. investigating Sep 21, 2026, 02:57 AM UTC

   Members attempting to access the test admin tool - test.crossref.org - are experiencing the following error: 'Error connecting to the authentication service. Please try again later or contact support.' Our technical team is investigating the issue.

2. resolved Sep 21, 2026, 09:18 AM UTC

   This incident has been resolved. Members can now log in to our test admin tool - test.crossref.org - as normal. Between approximately 21:30 UTC on 20 September and 08:30 UTC on 21 September, members attempting to log in saw the error "Error connecting to the authentication service." Our technical team restored the service and confirmed that login is working again.

Read the full incident report →

Started Sep 14, 2026, 11:19 PM UTC· resolved Sep 24, 2026, 01:22 PM UTC

1. monitoring Sep 14, 2026, 11:19 PM UTC

   Yesterday, 13 September, we reported an incident with our website: www.crossref.org. It was down from 11:13 to 12:23 UTC. We resolved that incident prematurely. The outage was caused by a know intermittent issue that our technical team is working to resolve, but does not yet have fixed. We're monitoring the issue, and anticipate doing so for the foreseeable future. Thus, we have re-opened a new incident here. We'll provide updates as we have them. -IF

2. monitoring Sep 15, 2026, 05:01 PM UTC

   We have deployed a fix for this issue and are monitoring the results. -IF

3. monitoring Sep 21, 2026, 10:12 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Sep 24, 2026, 01:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 13, 2026, 02:39 PM UTC· resolved Sep 14, 2026, 12:46 PM UTC

1. investigating Sep 13, 2026, 02:39 PM UTC

   Our main website at www.crossref.org was down for 70 minutes earlier, from 11:13 to 12:23 UTC. It's been up since but we'll investigate what happened. Sorry for the inconvenience. -GH

2. resolved Sep 14, 2026, 12:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2026, 04:25 PM UTC· resolved Sep 09, 2026, 08:38 PM UTC

1. investigating Sep 09, 2026, 04:25 PM UTC

   We had an issue with submission notifications going down around 0:00 UTC today. We re-enabled those submission notifications around 1000 UTC, but that has caused a delay in submission processing and notification delivery. As a result, processing of direct XML submissions either manually uploaded or posted to doi.crossref.org and submissions via our web deposit form - https://apps.crossref.org/webDeposit/ - are delayed. Our system is working through the backlog at the moment. -IF

2. monitoring Sep 09, 2026, 06:47 PM UTC

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

3. resolved Sep 09, 2026, 08:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 07, 2026, 08:00 PM UTC· resolved Sep 07, 2026, 08:00 PM UTC

1. resolved Sep 07, 2026, 08:00 PM UTC

   Several members reported errors authenticating and logging in to doi.crossref.org, Metadata Manager, web deposit form, OJS, and third-party tools due to an error in our system. That error began around 2000 UTC today. Jon on our technical team has fixed the issue. Members should now be able to log in to all Crossref services. -IF

Read the full incident report →

Started Aug 20, 2026, 02:13 PM UTC· resolved Aug 21, 2026, 01:30 PM UTC

1. investigating Aug 20, 2026, 02:13 PM UTC

   Crossref Metadata Search has been down and returning a 504 error since approximately 13:00 UTC. We are investigating.

2. investigating Aug 20, 2026, 02:15 PM UTC

   We are continuing to investigate this issue.

3. monitoring Aug 20, 2026, 04:34 PM UTC

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

4. resolved Aug 21, 2026, 01:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 09, 2026, 09:46 PM UTC· resolved Aug 09, 2026, 10:34 PM UTC

1. investigating Aug 09, 2026, 09:46 PM UTC

   We are currently investigating this issue.

2. investigating Aug 09, 2026, 10:18 PM UTC

   This incident is also resulting in errors for our members using the web deposit form and Metadata Manager. -IF

3. resolved Aug 09, 2026, 10:34 PM UTC

   This incident has been resolved. Our admin tool was down for approximately 140 minutes. We are now accepting and processing all submissions. -IF

Read the full incident report →

Started Jul 14, 2026, 08:36 AM UTC· resolved Jul 14, 2026, 09:16 AM UTC

1. investigating Jul 14, 2026, 08:36 AM UTC

   Some users are currently experiencing login issues with the Admin Tool, New Metadata Manager, and Web Deposit Form. We are currently investigating the issue.

2. resolved Jul 14, 2026, 09:16 AM UTC

   We have identified and fixed the issue affecting user logins. This incident is now resolved.

Read the full incident report →

Started Jul 13, 2026, 07:40 AM UTC· resolved Jul 13, 2026, 08:13 AM UTC

1. resolved Jul 13, 2026, 10:32 AM UTC

   The main Crossref website (www.crossref.org) has been down since 07:40 - 08:13 UTC. The website is available again.

Read the full incident report →

Started Jul 07, 2026, 01:01 PM UTC· resolved Jul 08, 2026, 12:26 PM UTC

1. investigating Jul 07, 2026, 01:18 PM UTC

   The REST API public and polite pools are experiencing issues with requests that return lists of results, including filters and queries. Requests are intermittently not returning all matching metadata records. We are investigating the cause.

2. investigating Jul 07, 2026, 03:11 PM UTC

   We are continuing to investigate this issue.

3. investigating Jul 07, 2026, 08:01 PM UTC

   We are continuing to investigate this issue.

4. monitoring Jul 08, 2026, 08:59 AM UTC

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

5. resolved Jul 08, 2026, 12:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 02, 2026, 01:00 PM UTC· resolved Jul 06, 2026, 10:06 AM UTC

1. investigating Jul 02, 2026, 01:00 PM UTC

   We have received multiple reports that requests in the REST API that use cursors to paginate through multiple pages of results are finishing early and not returning all of the requested records. We are investigating the cause. -IF

2. investigating Jul 02, 2026, 03:57 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jul 02, 2026, 05:54 PM UTC

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

4. monitoring Jul 02, 2026, 07:14 PM UTC

   We are continuing to monitor for any further issues.

5. monitoring Jul 03, 2026, 01:27 PM UTC

   We are continuing to monitor for any further issues.

6. monitoring Jul 03, 2026, 02:00 PM UTC

   We are continuing to monitor for any further issues.

7. resolved Jul 06, 2026, 10:06 AM UTC

   This incident has been resolved and our REST API is operating normally.

Read the full incident report →

Started Jun 22, 2026, 10:20 AM UTC· resolved Jun 24, 2026, 09:43 AM UTC

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.

Read the full incident report →

Started Jun 16, 2026, 08:15 AM UTC· resolved Jun 16, 2026, 11:59 AM UTC

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 →

Started May 29, 2026, 12:12 PM UTC· resolved Jun 05, 2026, 05:50 PM UTC

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 →

Started May 14, 2026, 04:10 PM UTC· resolved May 14, 2026, 06:17 PM UTC

1. investigating May 14, 2026, 04:10 PM UTC

   We are currently investigating this issue.

2. resolved May 14, 2026, 06:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 11, 2026, 04:00 AM UTC· resolved May 11, 2026, 04:00 AM UTC

1. resolved May 11, 2026, 04:00 AM 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 →

Started May 08, 2026, 04:59 PM UTC· resolved May 08, 2026, 07:38 PM UTC

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 →

Started May 04, 2026, 01:45 PM UTC· resolved May 07, 2026, 12:34 PM UTC

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 →

Started May 03, 2026, 10:56 AM UTC· resolved May 03, 2026, 08:57 PM UTC

1. resolved May 03, 2026, 11:00 AM 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 →

Started May 02, 2026, 04:37 PM UTC· resolved May 05, 2026, 12:39 PM UTC

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 →