BIG TELECOM
BGP inherited
Cluster stats
Netblocks11
All fragments 51 blocks across 3 clusters
Cluster ID192063853
RegistryPEERINGDB
Customersfind 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

2 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-07-06

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
109.239.137.40/32 BIG TELECOM PEERINGDB ASSIGNED ● high
178.18.225.123/32 BIG TELECOM PEERINGDB ASSIGNED ● high
185.1.152.200/32 BIG TELECOM PEERINGDB ASSIGNED ● high
185.232.60.37/32 BIG TELECOM PEERINGDB ASSIGNED ● high
193.27.37.6/32 BIG TELECOM PEERINGDB ASSIGNED ● high
193.27.39.87/32 BIG TELECOM PEERINGDB ASSIGNED ● high
195.208.208.154/32 BIG TELECOM PEERINGDB ASSIGNED ● high
2001:7f8:20:101::208:154/128 BIG TELECOM PEERINGDB ASSIGNED ● high
2001:b28:3ff::8be2:0:1/128 BIG TELECOM PEERINGDB ASSIGNED ● high
2a03:5f80:4::225:123/128 BIG TELECOM PEERINGDB ASSIGNED ● high
80.244.233.128/30 BIG-TELECOM RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: D how networks compare →
45.5% of checked blocks have valid RPKI ROA coverage (5 of 11)
No discrepancies found among checked blocks.

NIC Handles

ARTCOMS-MNT-RIPE AS35810 DUMY-RIPE DUMY-RIPE