asn.dev

Autonomous system

AS12886 LEWTELNET Oskar-von-Miller-Str. 1b

Residential RIPE Cable/DSL/ISP

IPv4 addresses 48.38K 24 prefixes
IPv6 prefixes 5 counted as prefixes, not addresses
Countries 1 mostly DE
Exchanges 2 recorded by PCH
Upstreams 17 2 downstream
Flagged prefixes 0 none

Summary

LEW TelNet

Germany · AI-generated

telecom isp infrastructure

A power utility's telecoms arm, named in the registry after the street it sits on.

What it's used for

  • The telecommunications subsidiary of a Bavarian electricity utility. 48,384 addresses across 24 IPv4 prefixes, five IPv6 prefixes, and 102 observed BGP neighbours.

Notable

  • The large blocks are 62.204.160.0/19, 153.100.160.0/19, 193.23.64.0/19 and 212.118.192.0/19.
  • 153.100.160.0/19 carries the netname INNOGY_001, registered to a different energy group.
  • The AS handle is LEWTELNET Oskar-von-Miller-Str. 1b.
  • The registry lookup for 212.118.192.0/19 failed, so nothing here describes that block's record.
  • Nine of eighteen sampled addresses returned names, split between ptr-62-204-168-0.static.lewtelnet-access.de and ptr-153-100-168-0.pool.lewtelnet-access.de.

Interesting

  • Electricity utilities became telecoms operators by accident: they already owned rights of way, towers and ducts for the power grid, and fibre costs little more to pull once the trench exists. The 102 neighbours are the regional interconnections that follow from owning infrastructure rather than from selling internet access.
  • The handle carries a street address, and the street is named after an electrical engineer famous for building power transmission. A utility's telecoms arm registered at that address is a small joke that nobody involved intended.
  • The reverse names distinguish static from pool, so the zone states which addresses are assigned to a fixed customer and which are handed out dynamically. Mail systems and abuse tooling read exactly that distinction, which is why operators bother to encode it.
  • INNOGY_001 names an energy company folded into another, on a block now announced here. Utility mergers move networks the same way telecom mergers do, and the underscore-and-number naming suggests a block created from a template, expecting an _002 that may never have come.

This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.

Interconnection

Peering at a glance

Full topology · Graph

Internet exchanges

Recorded at 2 exchanges in 1 country, largest first.

ExchangeLocationTheir address
DE-CIX FrankfurtFrankfurt, Germany80.81.194.108
DE-CIX MunichMunich, Germany185.1.208.64

Transit providers

17 upstream, 2 downstream and 30 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS8767M-net Telekommunikations GmbH581
AS13237euNetworks GmbH551
AS6939Hurricane Electric LLC209
AS34549meerfarbig GmbH & Co. KG108
AS24482SG.GS30
AS34019Hivane Association30
AS48362Stadtwerke Feldkirch30
AS212024Marc Schmitt30

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 24 prefixes · 48.38K addresses IPv6 5 prefixes

CountryNamePrefixes
DEGermany29

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS12886
Registry name
LEWTELNET
Registrant
LEWTELNET-MNT
Abuse contact
abuse@lewtelnet.de
Registered
2002-09-10
Last changed
2026-09-07
Allocation
allocated

Declared

PeeringDB profile

self-reported
Name
LEW TelNet
Network type
Cable/DSL/ISP
Scope
Europe
Traffic ratio
Mostly Inbound
Peering policy
Open
IRR as-set
RIPE::AS-LEWTELNET
Present at
2 exchanges
Website
http://www.lewtelnet.de

PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.

Routing security

RPKI and IRR

Full detail
RPKI
73% valid · 22 valid, 8 with no ROA
ROAs
22 authorising AS12886
ASPA
no ASPA record
IRR
100% registered · 30 of 30 announcements
Route objects
30 naming AS12886

Reputation

Classification and threat

Residential Fixed-line consumer ISP. Addresses here are homes.

Spamhaus DROP

Not on ASN-DROP The network as a whole is not listed.

No DROP prefixes None of its announced space is on the DROP prefix list.

Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,773 prefixes, as published 2026-10-13. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.

FBI IC3

No IC3 indicators Nothing from the FBI IC3 feed.

IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.

Elsewhere

Cross-check