- Detected by Pingoru
- Sep 11, 2025, 11:56 AM UTC
- Resolved
- Sep 12, 2025, 01:14 PM UTC
- Duration
- 1d 1h
Affected: Public REST APIPolite REST API
Timeline · 3 updates
-
investigating Sep 11, 2025, 11:56 AM UTC
We have found that some records failed to be indexed by the REST API on 3rd September, and continuing. Our technical team is investigating. -EA
-
identified Sep 11, 2025, 09:30 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Sep 12, 2025, 01:14 PM UTC
This incident has been resolved. -IF
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2025, 07:02 PM UTC
- Resolved
- Sep 10, 2025, 05:53 PM UTC
- Duration
- 22h 51m
Affected: Admin tool
Timeline · 2 updates
-
identified Sep 09, 2025, 07:02 PM UTC
All deposits containing references to CNKI, one of our sibling registration agencies, DOIs are processing slower at this time because of technical issues at CNKI. As a result, that is causing delays in submission processing and email notification delivery for all submissions (but especially submissions containing references to CNKI DOIs). -IF
-
resolved Sep 10, 2025, 05:53 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 22, 2025, 02:47 PM UTC
- Resolved
- Aug 25, 2025, 01:24 PM UTC
- Duration
- 2d 22h
Affected: Plus REST API
Timeline · 2 updates
-
investigating Aug 22, 2025, 02:47 PM UTC
We've had a Metadata Plus user sending bursts of very large numbers of queries which is knocking out the REST API Plus pool for a number of minutes at a time throughout the day today. We are working to get in contact with the Plus user in question to correct the behavior, but those large bursts of queries are causing some intermittent instability to the Plus pool. -IF
-
resolved Aug 25, 2025, 01:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 09:39 AM UTC
- Resolved
- Aug 27, 2025, 01:16 PM UTC
- Duration
- 8d 3h
Affected: Participation reports
Timeline · 6 updates
-
investigating Aug 19, 2025, 09:39 AM UTC
We have noted performance-related issues with Participation Reports. We are investigating the underlying cause. >EA
-
identified Aug 19, 2025, 01:56 PM UTC
The issue has been identified and a fix is being implemented. >EA
-
monitoring Aug 19, 2025, 07:45 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Aug 20, 2025, 12:55 PM UTC
We are continuing to monitor for any further issues.
-
monitoring Aug 25, 2025, 01:24 PM UTC
A fix has been implemented. We will be monitoring the results for a few days before we resolve this incident. -IF
-
resolved Aug 27, 2025, 01:16 PM UTC
This incident has been resolved. -IF
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2025, 09:07 AM UTC
- Resolved
- Aug 08, 2025, 03:05 PM UTC
- Duration
- 3d 5h
Affected: Plus REST API
Timeline · 4 updates
-
investigating Aug 05, 2025, 09:07 AM UTC
Metadata Plus subscribers may be experiencing slow responses or timeouts from the REST API. We're still completing the setup of rate limiting in the new cloud environment, so we are focusing on getting that done ASAP. -GH
-
monitoring Aug 06, 2025, 10:35 AM UTC
Things have settled down as a result of our changes and the Plus pool is performing better now. We're monitoring. -GH
-
monitoring Aug 07, 2025, 03:15 PM UTC
We are continuing to monitor for any further issues.
-
resolved Aug 08, 2025, 03:05 PM UTC
We have made changes on our end that has resulted in better response times. This incident has been resolved. -IF
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2025, 01:24 PM UTC
- Resolved
- Aug 07, 2025, 07:23 PM UTC
- Duration
- 3d 5h
Affected: XML Snapshots
Timeline · 4 updates
-
identified Aug 04, 2025, 01:24 PM UTC
There was a bug in the code that generates the new XML Metadata Plus snapshots and, as a result, this month's XML Metadata Plus snapshots will be delayed. We have updated that code and the XML Metadata Plus snapshots are now being generated, but they may not be available until 7 August. -IF
-
identified Aug 06, 2025, 10:45 AM UTC
Unfortunately, the data in the XML snapshot doesn't match what we would expect, so we're going to re-run it again. It takes a few days - we'll keep this incident updated as we know more. -GH
-
identified Aug 07, 2025, 03:19 PM UTC
We continue to generate the new XML Metadata Plus snapshots. We expect it to be available by Saturday, 9 August. -IF
-
resolved Aug 07, 2025, 07:23 PM UTC
This incident has been resolved. The newest XML Metadata Plus snapshots is now available.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2025, 07:12 PM UTC
- Resolved
- Aug 12, 2025, 07:47 PM UTC
- Duration
- 20d
Affected: Plus OAI-PMHOAI-PMH
Timeline · 8 updates
-
investigating Jul 23, 2025, 07:12 PM UTC
We have had metadata users report that they are receiving intermittent 504 (Gateway time-out) status code errors on calls to OAI-PMH endpoints. We have been able to replicate and are currently investigating. -IF
-
investigating Jul 24, 2025, 03:28 PM UTC
We are continuing to investigate this issue.
-
investigating Jul 25, 2025, 08:40 PM UTC
We are continuing to investigate this issue.
-
identified Jul 28, 2025, 06:49 PM UTC
This issue has been identified and we'll be releasing a fix during tomorrow's maintenance window. -IF
-
identified Jul 30, 2025, 04:03 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Aug 06, 2025, 06:26 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Aug 08, 2025, 03:09 PM UTC
We believe our changes have solved this issue, but we're going to continue to monitor this over the weekend. -IF
-
resolved Aug 12, 2025, 07:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2025, 05:45 PM UTC
- Resolved
- Jul 25, 2025, 09:01 AM UTC
- Duration
- 2d 15h
Timeline · 7 updates
-
investigating Jul 22, 2025, 05:45 PM UTC
We distributed about a third of this month's resolution report before the batch run failed. Our technical team is working on a fix. Once the fix is in place, we will distribute the remaining resolution reports for this month. -IF
-
investigating Jul 22, 2025, 07:40 PM UTC
We are continuing to investigate this issue.
-
monitoring Jul 22, 2025, 09:37 PM UTC
Jon on our technical team has deployed a fix and this month's run of the resolution report has resumed. It may take a several days before all reports have been distributed to our members. -IF
-
monitoring Jul 23, 2025, 08:20 PM UTC
We are continuing to generate resolution reports for anyone who has yet to receive them this month.
-
monitoring Jul 24, 2025, 12:35 PM UTC
Several members have reported that the links within the resolution reports are returning 404 'page not found' status code errors. We are actively working to fix those links and hope to have those routed properly within the next 24 hours. -IF
-
monitoring Jul 25, 2025, 12:50 AM UTC
All of this month's resolution reports have now been delivered. The links within the reports continue to resolve to 404 'page not found' status code errors. We expect to have those links repaired tomorrow. -IF
-
resolved Jul 25, 2025, 09:01 AM UTC
This should all be resolved now and the reports should not be resolving to a 404 error anymore.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2025, 12:45 PM UTC
- Resolved
- Aug 27, 2025, 12:06 PM UTC
- Duration
- 36d 23h
Affected: Public REST APIPlus REST APIPolite REST API
Timeline · 19 updates
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2025, 09:16 PM UTC
- Resolved
- Aug 27, 2025, 01:16 PM UTC
- Duration
- 46d 15h
Affected: Crossmark dialog server
Timeline · 22 updates
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2025, 08:12 AM UTC
- Resolved
- Jul 02, 2025, 02:27 PM UTC
- Duration
- 6h 14m
Affected: Admin toolTest admin toolWeb deposit formNew Metadata Manager
Timeline · 6 updates
-
investigating Jul 02, 2025, 08:12 AM UTC
We are investigating an incident that is affecting metadata deposits of members using the record form and OJS instance. We'll provide updates as soon as we know more. If you have any questions, contact the support team at [email protected].
-
investigating Jul 02, 2025, 12:15 PM UTC
We are continuing to investigate this issue.
-
identified Jul 02, 2025, 12:49 PM UTC
This issue has been identified, and we will be deploying an emergency release starting at 1300 UTC (and continuing through 1500 UTC) to fix the problem. Our members may experience delays in deposit system admin tool (doi.crossref.org) processing. Deposits submitted during this time will be stored and processed after the emergency maintenance has been completed. -IF
-
identified Jul 02, 2025, 01:22 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Jul 02, 2025, 02:12 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 02, 2025, 02:27 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2025, 01:25 PM UTC
- Resolved
- Jun 19, 2025, 03:54 PM UTC
- Duration
- 1d 2h
Affected: Plus REST API
Timeline · 4 updates
-
identified Jun 18, 2025, 01:25 PM UTC
We’ve had several reports of performance lags of the Plus pool of our REST API from Metadata Plus users. We have identified the source of the degraded performance and are working on a fix. It could be 24 to 48 hours before we have that fix in place.
-
identified Jun 18, 2025, 04:28 PM UTC
We are continuing to work on a fix for this issue.
-
identified Jun 18, 2025, 08:11 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Jun 19, 2025, 03:54 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 10:12 AM UTC
- Resolved
- Jun 03, 2025, 12:15 PM UTC
- Duration
- 2h 2m
Affected: Metadata search
Timeline · 2 updates
-
investigating Jun 03, 2025, 10:12 AM UTC
For the last hour, Crossref Search has been showing a 504 timeout status response due to heavy use. We're investigating and looking at adding more capacity to balance the high traffic. -GH
-
resolved Jun 03, 2025, 12:15 PM UTC
We have increased capacity, and the service is now restored. Thanks for your patience! -GH
Read the full incident report →
- Detected by Pingoru
- May 29, 2025, 10:56 AM UTC
- Resolved
- May 29, 2025, 11:11 AM UTC
- Duration
- 14m
Affected: Admin tool
Timeline · 2 updates
-
investigating May 29, 2025, 10:56 AM UTC
The Crossref admin tool has been down for the last 10 minutes. Our team is aware and are investigating. More as we know it.
-
resolved May 29, 2025, 11:11 AM UTC
The admin tool is available once more. The team are investigating the reasons for the outage.
Read the full incident report →
- Detected by Pingoru
- May 07, 2025, 03:05 PM UTC
- Resolved
- May 07, 2025, 03:25 PM UTC
- Duration
- 19m
Affected: Crossref websiteAdmin toolPlus OAI-PMHOAI-PMHTest admin toolXML APIPlus content negotiationWeb deposit formOpenURLNew Metadata ManagerCrossmark dialog serverPublic content negotiationPolite content negotiation
Timeline · 3 updates
-
investigating May 07, 2025, 03:05 PM UTC
We are currently investigating this issue.
-
monitoring May 07, 2025, 03:11 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 07, 2025, 03:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 01, 2025, 02:09 PM UTC
- Resolved
- May 01, 2025, 05:39 PM UTC
- Duration
- 3h 29m
Affected: Admin toolTest admin toolNew Metadata Manager
Timeline · 5 updates
-
investigating May 01, 2025, 02:09 PM UTC
We are currently investigating this issue.
-
identified May 01, 2025, 03:13 PM UTC
The issue has been identified and a fix is being implemented.
-
identified May 01, 2025, 03:28 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring May 01, 2025, 04:26 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 01, 2025, 05:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2025, 12:35 PM UTC
- Resolved
- May 01, 2025, 02:54 AM UTC
- Duration
- 14h 18m
Affected: Public REST APICrossref websitedeliberately-unreliable serverPlus REST APIAdmin toolHandle serversPolite REST APICrossref supportPlus OAI-PMHDemo AuthOAI-PMHMetadata searchMonitoring of iThenticate can be seen at https://turnitin.statuspage.io.XML SnapshotsTest admin toolXML APIParticipation reportsJSON SnapshotsAWS cloudfrontPlus content negotiationWeb deposit formORCID Auto-updateOpenURLNew Metadata ManagerKey ManagerCrossmark dialog serverPublic content negotiationPolite content negotiation
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2025, 09:30 PM UTC
- Resolved
- Apr 29, 2025, 11:15 PM UTC
- Duration
- 1h 45m
Affected: Participation reports
Timeline · 2 updates
-
investigating Apr 29, 2025, 09:30 PM UTC
We are currently investigating this issue.
-
resolved Apr 29, 2025, 11:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2025, 07:02 PM UTC
- Resolved
- Apr 10, 2025, 01:54 PM UTC
- Duration
- 8d 18h
Affected: Admin toolTest admin toolWeb deposit formNew Metadata Manager
Timeline · 20 updates
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2025, 11:24 AM UTC
- Resolved
- Mar 04, 2025, 02:12 PM UTC
- Duration
- 2h 48m
Affected: Public REST API
Timeline · 2 updates
-
investigating Mar 04, 2025, 11:24 AM UTC
We noticed the 'Public' pool for the REST API is sometimes slow and timing out the last 20 minutes, we're looking into it and advise using 'Polite' if you need a faster response time at the moment, which means adding your mailto in your header requests. More soon. -GH
-
resolved Mar 04, 2025, 02:12 PM UTC
We have resolved the issue, which affected only some types of queries due to a small number of server failures, using the automated recovery mechanism for Elasticsearch. -GH
Read the full incident report →
- Detected by Pingoru
- Jan 20, 2025, 02:10 PM UTC
- Resolved
- Jan 21, 2025, 08:13 PM UTC
- Duration
- 1d 6h
Affected: ORCID Auto-update
Timeline · 4 updates
-
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.
-
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.
-
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.
-
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.
Read the full incident report →
- Detected by Pingoru
- Jan 07, 2025, 09:12 AM UTC
- Resolved
- Jan 07, 2025, 10:28 AM UTC
- Duration
- 1h 15m
Affected: Retraction Watch
Timeline · 2 updates
-
investigating Jan 07, 2025, 09:12 AM UTC
Files containing retractions and corrections from Retraction Watch haven't been updated on the GitLab repository since 31 December. This is due to an issue pushing to Crossref's GitLab. We are currently investigating the cause.
-
resolved Jan 07, 2025, 10:28 AM UTC
This is resolved. The GitLab token expired on Dec 31st, and a new one has now been created and applied.
Read the full incident report →
- Detected by Pingoru
- Dec 04, 2024, 12:40 AM UTC
- Resolved
- Dec 05, 2024, 03:41 PM UTC
- Duration
- 1d 15h
Affected: Crossmark dialog server
Timeline · 4 updates
-
investigating Dec 04, 2024, 12:40 AM UTC
Crossmark dialog boxes with corrections and other updates are not being reflected correctly (instead, the Crossmark status is returning the 'document is current' status). Our technical team will begin investigation into this error tomorrow morning. -IF
-
identified Dec 04, 2024, 11:08 AM UTC
The cause of this incident was identified to be a recent update to our REST API code. We expect it to be fixed by a re-index of the affected records, which our technical team is working on now. We expect this to be completed later today.
-
monitoring Dec 05, 2024, 02:55 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 05, 2024, 03:41 PM UTC
This incident has been resolved.
Read the full incident report →
Notice September 23, 2024 - Detected by Pingoru
- Sep 23, 2024, 06:27 PM UTC
- Resolved
- Jan 13, 2025, 06:18 PM UTC
- Duration
- 111d 23h
Timeline · 13 updates
Read the full incident report →
