Login

Recent searches

No recent searches

Search options

Only available when logged in.
lor.sh is one of the many independent Mastodon servers you can use to participate in the fediverse.
lor.sh is yet another mastodon instance.

Administered by:

Server stats:

369
active users

lor.sh: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

tyx

New shitty reality:
Every time is you wonder whether it's permanent or not.

Just now the whole nih.gov is not resolving from two different locations I have access to.
Also:
downdetector.com/status/nih/

And just in time when I decided to do some work 1AM on Sat^W Sunday.

Downdetector screenshot with rising plot starting from 6pm, peak value on Y axis is 157. Above: National Institutes of Health outages reported in the last 24 hours Below: This chart shows a view of problem reports submitted in the past 24 hours compared to the typical volume of reports
#nih
Mar 02, 2025, 12:12 AM·Public·Web
9boosts·1favorite
Public
Pascal Hingamp

@tyx tldr.nettime.org/@ww/114089972

tldr.nettimeww (@ww@tldr.nettime.org)Attached: 2 images So, three nameservers out of seven for the pubmed.ncbi.nlm.nih.gov are broken. If you try to look at the web site, you stand a 3/7 chance of encountering something that is broken. The nameservers have the following addresses: $ host ns.nih.gov host ns.nih.gov has address 128.231.128.251 $ host ns2.nih.gov host ns3.nins2.nih.gov has address 128.231.64.1 $ host ns3.nih.gov ns3.nih.gov has address 165.112.4.230 We can see that the addresses for the first two both start with 128.231 and might guess that they are relatively nearby to each other. This can be confirmed using traceroute. Go ahead and open a terminal and try it out! traceroute 128.231.128.251 traceroute 128.231.64.1 for me, the paths, the sequence of routers between me and those addresses look broadly the same. The other one is different, traceroute 165.112.4.230 it goes a totally different way. So whatever problem is happening is not limited to a single site or datacentre. Now we can turn to RIPE for some help. Let us inspect the last address, https://stat.ripe.net/widget/bgplay#resource=165.112.4.230 This is very peculiar. Notice how that network is announced from two different places. And there seems to be a partition, they are not (visibly) connected to each other! This is not normal. I attach a screenshot. There is also some volatility, shown as path changes, the yellow bars at the bottom. Looking at ns.nih.gov, https://stat.ripe.net/widget/bgplay#resource=128.231.128.251 this appears more coherent, but volatile. The network was withdrawn about 45 minutes before I took the second screenshot, about an hour ago. And then re-announced. RIPE's BGPPlay is very nice, you can time travel and replay this incident as observed from the Internet. It takes a bit of background knowledge to decode what is going on though. Someone is doing networking... Badly... @researchfairy@scholar.social
Public *
tyx

@pascal_hingamp
Hope someone just screwed BGP up during a weekend maintenance window.

Search
About