Science took a major hit today, and most didn’t even notice.

The U.S. govt (or better elons cronies) shut down #PubMed, one of the most important, comprehensive, widely used, free database of biomedical and life sciences.

It provided access to millions of research articles clinical studies and reviews.

PubMed was a cornerstone of modern medical and life sciences research.

Edit: It seems to be an DNS issue that has not been resolved yet (for everybody)

It seems DNS servers have been shut down. Situation is unclear, but i guess we can not rely on this source fully anymore. Expect censoring at least.

Check out the european alternative:

https://europepmc.org/

@martinjuhasz it seems it is related to DNS according to

https://tldr.nettime.org/@ww/114089911520112987

ww (@[email protected])

The @[email protected] noticed [1] that something's wrong with PubMed so I did a little investigating with the help of my favourite command line tools, host(1), traceroute(1) and RIPE's BGPPlay tool. The hostname for pubmed is pubmed.ncbi.nlm.nih.gov. The DNS zone is ncbi.nlm.nih.gov. DNS zones have serial numbers. That's how secondary nameservers can figure out if something has changed and they should fetch a new copy of the zone to serve. They figure this out using a serial number which, by convention, is a date and a sequence number. % host -t soa ncbi.nlm.nih.gov ncbi.nlm.nih.gov has SOA record dns1-ncbi.ncbi.nlm.nih.gov. systems.ncbi.nlm.nih.gov. 2025022701 10800 5400 2419200 82800 This suggests that the zone was last changed a few days ago. So it's not a DNS change that led to this problem. That zone has seven nameservers. Rather a lot, but not unusual for an old government system, $ host -t ns ncbi.nlm.nih.gov ncbi.nlm.nih.gov name server ns.nih.gov. ncbi.nlm.nih.gov name server ns2.nih.gov. ncbi.nlm.nih.gov name server ns3.nih.gov. ncbi.nlm.nih.gov name server lhcns1.nlm.nih.gov. ncbi.nlm.nih.gov name server lhcns2.nlm.nih.gov. ncbi.nlm.nih.gov name server dns1-ncbi.ncbi.nlm.nih.gov. ncbi.nlm.nih.gov name server dns2-ncbi.ncbi.nlm.nih.gov. Asking these nameservers directly for the address of pubmed, we find that the ones ending with nlm.nih.gov work fine, $ host -4 -t a pubmed.ncbi.nlm.nih.gov lhcns1.nlm.nih.gov. pubmed.ncbi.nlm.nih.gov has address 34.107.134.59 28 min but asking any of the first three does not work: $ host -4 -t a pubmed.ncbi.nlm.nih.gov ns.nih.gov. ;; communications error to 128.231.128.251#53: timed out What is wrong with the NIH nameservers? To be continued... [1] https://scholar.social/@researchfairy/114089685773663683

tldr.nettime
@Toch @martinjuhasz Anyways. Wasn't there a group of people, who were rescuing #science data and sources from depublication by the Trump admin? I'm trying to remember names/accounts. Maybe they wanna look into this to see if anything can be saved?

@levampyre @martinjuhasz as Martin has said above there is Europe pmc

According to them

https://europepmc.org/Help#howjournals

They mirror a lot from pmc.

Safeguarding Research & Culture (SRC) — Distributing Cultural Memory

"As researchers we often say 'we need the data'. Today, the data needs us." — Kathy Reid

Safeguarding Research & Culture (SRC) — Distributing Cultural Memory

@martinjuhasz They're not shut down, they're pretty dorked, though.

If you do a "dig www.nih.gov +tcp -t MX", you'll get an answer, but it won't be the MX's for NIH. If you do a "dig nih.gov +tcp -t SOA" you'll get an answer that looks vaguely right. If you don't do TCP, you won't get an answer at all.

Their DNS is broken, but not shut down.