KTM Telekom

BGP inherited

Cluster stats

Netblocks	8
Registered in	Poland (3) · Russia (2)
Cluster ID	208803811
Registry	PEERINGDB
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 4 shared RIR contact/maintainer handles
Registry names	2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON

10 0 netblocks since 2026-07-05

2026-07-05 peak 10 2026-07-19

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
89.46.145.181/32	KTM Telekom	PEERINGDB	ASSIGNED	● high
178.216.41.39/32	KTM Telekom	PEERINGDB	ASSIGNED	● high
195.182.218.14/32	KTM Telekom	PEERINGDB	ASSIGNED	● high
2001:678:3ac::557/128	KTM Telekom	PEERINGDB	ASSIGNED	● high
2001:7f8:42::6:2201:1/128	KTM Telekom	PEERINGDB	ASSIGNED	● high
2001:7f8:5b::294/128	KTM Telekom	PEERINGDB	ASSIGNED	● high
178.16.145.44/30	KTM-LAN	RIPE	ASSIGNED PA	● low
178.16.156.112/30	KTM-LAN	RIPE	ASSIGNED PA	● low

what's this?

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

TELEKOMSYSTEMNET-PL via Netia SA sub-allocation
Telekomibm sub-allocation
FTZ-TELEKOM via Verein zur Foerderung eines Deutschen Forschungsnetzes e.V. sub-allocation
ZAKLAD-TELEKOMUNIKACJI-PILA via Orange Polska Spolka Akcyjna sub-allocation
LATTELEKOM via SIA Tet sub-allocation
Telekom CG via Crnogorski Telekom a.d.Podgorica sub-allocation
ZEN20010918-DAR-TELEKOMASSIST via Zen Internet Ltd sub-allocation
APOLLO-TEKA_TELEKOM via SIA Tet sub-allocation

what's this?

RPKI hygiene: B how networks compare →

87.5% of checked blocks have valid RPKI ROA coverage (7 of 8)

No discrepancies found among checked blocks.

AS62201 DUMY-RIPE DUMY-RIPE OBIT-MNT