BIG-4

BGP inherited
Cluster stats
Netblocks7
Cluster ID208390717
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-13

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
83.1.165.0/24 BIG-4 RIPE ASSIGNED PA ● low
83.1.166.0/24 BIG-4 RIPE ASSIGNED PA ● low
83.1.167.0/24 BIG-4 RIPE ASSIGNED PA ● low
212.244.82.0/24 BIG-4 RIPE ASSIGNED PA ● low
212.244.86.0/24 BIG-4 RIPE ASSIGNED PA ● low
217.96.110.0/24 BIG-4 RIPE ASSIGNED PA ● low
217.96.121.0/24 BIG-4 RIPE ASSIGNED PA ● low

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 (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE TPNET