Teleport sp. z o.o.

TELEPORT-Network

BGP inherited

Cluster stats

Netblocks	9
All fragments	11 blocks across 2 clusters
Cluster ID	205524793
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

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

Footprint over time

4 weekly snapshots · JSON

9 0 netblocks since 2026-07-05

2026-07-05 peak 9 2026-07-13

IP Ranges (9)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
46.175.112.0/22	TELEPORT-Network	RIPE	ASSIGNED PA	● low
46.175.116.0/22	TELEPORT-Network	RIPE	ASSIGNED PA	● low
85.209.38.0/23	Teleport-Network	RIPE	ASSIGNED PA	● low
91.217.18.0/24	TELEPORT-Network	RIPE	ASSIGNED PA	● low
91.217.19.0/24	TELEPORT-Network	RIPE	ASSIGNED PA	● low
185.225.108.0/23	TELEPORT-Network	RIPE	ASSIGNED PA	● low
185.225.110.0/23	TELEPORT-Network	RIPE	ASSIGNED PA	● low
193.35.24.0/25	Teleport-Network	RIPE	ASSIGNED PA	● low
193.35.24.128/25	Teleport-Network	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “TELEPORT Network” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Teleport-Network-for-Netask 2 blocks

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.

Iabg Teleport Network via IABG Teleport GmbH sub-allocation

Network trust

what's this?

RPKI hygiene: C how networks compare →

77.8% of checked blocks have valid RPKI ROA coverage (7 of 9)

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-TELEPORT