We observed a 65% drop in global telnet traffic in a single hour on Jan 14, settling into a sustained 59% reduction.
-
We observed a 65% drop in global telnet traffic in a single hour on Jan 14, settling into a sustained 59% reduction. 18 ASNs went silent, 5 countries disappeared, but cloud providers were unaffected.
Our analysis of 51.2M sessions points to backbone-level port 23 filtering by a North American Tier 1 transit provider.
https://www.labs.greynoise.io/grimoire/2026-02-10-telnet-falls-silent/ -
We observed a 65% drop in global telnet traffic in a single hour on Jan 14, settling into a sustained 59% reduction. 18 ASNs went silent, 5 countries disappeared, but cloud providers were unaffected.
Our analysis of 51.2M sessions points to backbone-level port 23 filtering by a North American Tier 1 transit provider.
https://www.labs.greynoise.io/grimoire/2026-02-10-telnet-falls-silent/@greynoise Why was anyone in this century running telnet across the internet? Was it *all* attacks?
-
We observed a 65% drop in global telnet traffic in a single hour on Jan 14, settling into a sustained 59% reduction. 18 ASNs went silent, 5 countries disappeared, but cloud providers were unaffected.
Our analysis of 51.2M sessions points to backbone-level port 23 filtering by a North American Tier 1 transit provider.
https://www.labs.greynoise.io/grimoire/2026-02-10-telnet-falls-silent/@greynoise not a carrier’s job to police the Internet in this way and I would suggest potentially undermines any later attempt to claim “mere conduit” protection
-
We observed a 65% drop in global telnet traffic in a single hour on Jan 14, settling into a sustained 59% reduction. 18 ASNs went silent, 5 countries disappeared, but cloud providers were unaffected.
Our analysis of 51.2M sessions points to backbone-level port 23 filtering by a North American Tier 1 transit provider.
https://www.labs.greynoise.io/grimoire/2026-02-10-telnet-falls-silent/@greynoise there is still such a thing as telnet traffic?
-
R relay@relay.mycrowd.ca shared this topicR relay@relay.an.exchange shared this topic