Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.misc
Subject: Pingable, But No Route To Host
Date: Mon, 24 Feb 2025 07:53:39 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 8
Message-ID: <vph8i2$vs13$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 24 Feb 2025 08:53:39 +0100 (CET)
Injection-Info: dont-email.me; posting-host="514b9375f3f626cad6324c9c7e91e06f";
	logging-data="1044515"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19xdj6Oz7mpkqwqdEjLwhsG"
User-Agent: Pan/0.162 (Pokrosvk)
Cancel-Lock: sha1:rhEAiBYWImkduXFCA6Z0hLpwQR0=
Bytes: 1322

Observed some interesting behaviour with a local online service: the 
domain name is pingable, but any attempt to actually connect returns “no 
route to host”.

Looks like the ping service is being provided by a separate mechanism to 
the actual host itself. What kind of server infrastructure would tell 
porkies like that? No doubt this is characteristic of some well-known 
cloud service ...