Followers here will remember the Giganews screw-ups of a few weeks ago (repeated twice, I guess for 'effect'), where they (for still reasons unknown) changed their peering tables to move this Russian outfit (neva.ru) as their primary feed. That lasted both times for a few days before someone got their head screwed back on straight, and it took several days to 'back-fill' all the messages they had missed in the interim.
Since the last 'off the tracks' operation (and changing their peering back to Astraweb and other US-based plants) things have been running pretty smooth there.
Well, I guess maybe someone somewhere would have to copy their screw-up, and in picking around today (okay, I was actually doing some re-testing of the latest Astra screw-up, and decided to...) check out readnews, which is marketed under the Blocknews and Usenet-news 'names'.
Well, right in the middle of it (is IS Monday, time for idiot operators to swap things around) they changed their peering to.... you guessed it, neva.ru. As a result (and yes, I've checked), they are transmitting all that is being posted to all of their servers out through these ruskies. Where, of course, it appears to be 'stuck' and not propagating out.
So, if you posted anything on a readnews server from around 6 or so hours ago, I'd be checking to see it it actually propagated to anywhere else.
Like I said, I usually don't check these folks for much, but geeze, you'd think they might have notied the Giganews screw-up and made a mental note NOT to have anything to do with the ruskies.
Guess not.
Like I said, I posted some test transmissions, and will continue to check to see if it ever gets out of being 'locked' and failing to propagate. For posters, you should all be checking your transmissions on a server NOT your posting one, and you'll pretty quickly note that things have gone 'off-track'. Maybe at some point it'll get 'flushed out', and I'll amend this notice then.
Bookmarks