BTE

BGP inherited
Cluster stats
Netblocks8
Registered in Netherlands (7) · China (1)
All fragments 13 blocks across 4 clusters
Cluster ID210981955
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
116.228.56.196/30 BTE APNIC ASSIGNED NON-PORTABLE ● high
93.117.220.240/29 BTE RIPE ASSIGNED PA ● low
93.117.221.168/29 BTE RIPE ASSIGNED PA ● low
93.117.248.16/29 BTE RIPE ASSIGNED PA ● low
93.117.251.240/29 BTE RIPE ASSIGNED PA ● low
159.100.65.184/29 BTE RIPE LEGACY ● low
159.100.72.184/29 BTE RIPE LEGACY ● low
213.34.157.88/29 BTE RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “BTE” — 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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MAINT-CHINANET-SH TNF-MNT YS1216-AP YS1216-AP