GLOBAL-TELEPORT-KBK

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks4 · 1,536 IPv4 addresses
All fragments 8 blocks across 4 clusters
Cluster ID214999994
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
83.229.236.0/24 GLOBAL-TELEPORT-KBK RIPE ASSIGNED PA ● low
83.229.237.0/24 GLOBAL-TELEPORT-KBK RIPE ASSIGNED PA ● low
213.24.249.0 – 213.24.250.255 GLOBAL-TELEPORT-KBK RIPE ASSIGNED PA ● low
217.106.250.0/23 GLOBAL-TELEPORT-KBK RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (3 of 4)
Possible discrepancies (3)

These blocks are registered to GLOBAL-TELEPORT-KBK but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

213.24.249.0 – 213.24.250.255 /23 authorized for AS12389 — PJSC Rostelecom
83.229.236.0/24 /24 authorized for AS6854 — PJSC MegaFon
83.229.237.0/24 /24 authorized for AS6854 — PJSC MegaFon

NIC Handles

AS8342-MNT DUMY-RIPE DUMY-RIPE TCNET-NOC