Is Crossref Down?

SaaSLive status, outages, and incident history

No. Crossref is up right now.

Every monitored Crossref system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s

Know the moment Crossref breaks

Crossref is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Crossref status page

How we know: the official Crossref status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report 9 Nov 2026 · 20:40 UTC

Crossref Status Summary

As of 20:40 UTC on 9 November 2026, Crossref is operational. PulsAPI checked Crossref's official status page and found 31 of 31 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.91% uptime for Crossref, counting degraded performance as up. The latest incident, "New funder matches not available via the Metadata Plus REST API pool", was on Oct 21, 2026 and lasted 181h 8m.

Cite as: PulsAPI, “Crossref status”, checked 9 November 2026, 20:40 UTC. https://www.pulsapi.com/services/crossref

Crossref Component Status

The main Crossref systems on this page. All 31 are operational right now.

31operational

APIs » Crossmark dialog server

Operational

APIs » OAI-PMH

Operational

APIs » OpenURL

Operational

28 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking APIs » Polite content negotiation, APIs » Polite REST API, APIs » Public content negotiation, APIs » Public REST API, APIs » XML API, Content Registration » Admin tool, Content Registration » New Metadata Manager, Content Registration » Test admin tool, Content Registration » Web deposit form, Integrations and external dependencies » AWS cloudfront, Integrations and external dependencies » Handle servers, Integrations and external dependencies » Monitoring of iThenticate can be seen at https://turnitin.statuspage.io., and 16 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Crossref Outages & Incidents

Incident history from the official Crossref status page, including resolution updates.

New funder matches not available via the Metadata Plus REST API poolResolved Oct 21, 2026 · 181h 8mResolved

This incident has been resolved. --- [2026-10-28T18:02:45.932Z] (monitoring) 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 --- [2026-10-27T15:56:32.736Z] (monitoring) We are continuing to monitor for any further issues. --- [2026-10-26T15:20:11.459Z] (monitoring) We are continuing to monitor for any further issues. --- [2026-10-24T06:42:19.687Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-24T06:42:01.046Z] (identified) All affected records have been reindexed and we are monitoring the solution. --- [2026-10-23T18:55:12.909Z] (identified) 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. --- [2026-10-23T12:55:46.941Z] (identified) We are testing a solution for this issue and will post another update once the fix has been deployed. --- [2026-10-21T12:01:51.799Z] (identified) 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.

Content Registration Outage and InstabilityResolved Oct 16, 2026 · 70h 45mResolved

This incident has been resolved. --- [2026-10-16T21:35:46.250Z] (monitoring) 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.

Metadata Plus REST API not validating API keysResolved Oct 5, 2026 · 4h 3mResolved

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. --- [2026-10-05T13:01:30.452Z] (monitoring) A fix has been implemented and we are continuing to monitor the performance of the Metadata Plus pool. --- [2026-10-05T12:49:37.535Z] (investigating) We are continuing the investigate the outage. The Plus pool was down between 12:00 and 12:36 on 5 Oct, 2026. --- [2026-10-05T12:41:47.422Z] (investigating) The API is back up but we are still investigating and monitoring. --- [2026-10-05T12:21:44.180Z] (investigating) Request to the Metadata Plus pool of the REST API are receiving 401 responses (access denied). We are investigating the cause.

Upcoming maintenance

Announced by Crossref. Planned work, not an outage.

10 November - weekly maintenance, release v0.298.0Scheduled for Nov 10, 2026 · 2h 0mScheduled

We will be undergoing scheduled maintenance - release version 0.298.0 - on 10 November from 1500 to 1700 UTC. 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 maintenance has been completed.

Crossref Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Crossref incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed

Aug 11100.00% average · 48 days with incidentsNov 9

Going further back: Crossref uptime by month and every recorded Crossref outage.

Live Crossref Outage Reports

Problems reported by engineers using Crossref. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No Crossref problems reported yet.

Something wrong with Crossref on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Crossref

Is Crossref down? Crossref reports live availability for 38 components at status.crossref.org, among them Public REST API, Crossref website and deliberately-unreliable server. Track Crossref outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Crossref uptime at 99.91%. Response times, incident history, and SLA tracking for Crossref are available on the PulsAPI dashboard.

Crossref Status FAQ

Is Crossref down right now?

The verdict at the top of this page comes from the latest poll of the official Crossref status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Crossref is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Crossref recovers.

How do I check Crossref uptime history?

PulsAPI tracks Crossref uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.91%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Crossref changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Crossref outages?

PulsAPI reads the official Crossref status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Crossref components?

Yes. PulsAPI monitors 31 individual Crossref components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Crossref goes down?

Yes. Create a free account and subscribe to Crossref: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Crossref to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Crossref problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Crossref?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Crossref plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Crossref with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services