A4 TELECOM

BGP inherited
Cluster stats
Netblocks8
Cluster ID213186130
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name 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
45.68.73.191/32 A4 TELECOM PEERINGDB ASSIGNED ● high
45.68.75.46/32 A4 TELECOM PEERINGDB ASSIGNED ● high
45.68.83.140/32 A4 TELECOM PEERINGDB ASSIGNED ● high
187.16.214.180/32 A4 TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::214:180/128 A4 TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:2::55:140/128 A4 TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::145:191/128 A4 TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::147:46/128 A4 TELECOM PEERINGDB ASSIGNED ● high

Possibly related to this organisation

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.

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

AS271069