CodeBGP Monitor
BGP inherited
Cluster stats
Netblocks18
Cluster ID193384954
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

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

IP Ranges (18)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.49.238.134/32 CodeBGP Monitor PEERINGDB ASSIGNED ● high
80.81.194.207/32 CodeBGP Monitor PEERINGDB ASSIGNED ● high
80.249.213.32/32 CodeBGP Monitor PEERINGDB ASSIGNED ● high
149.112.50.110/32 CodeBGP Monitor PEERINGDB ASSIGNED ● high
185.1.144.13/32 CodeBGP Monitor PEERINGDB ASSIGNED ● high
185.1.147.132/32 CodeBGP Monitor PEERINGDB ASSIGNED ● high
193.178.185.182/32 CodeBGP Monitor PEERINGDB ASSIGNED ● high
193.239.119.110/32 CodeBGP Monitor PEERINGDB ASSIGNED ● high
196.60.9.186/32 CodeBGP Monitor PEERINGDB ASSIGNED ● high
2001:504:125:e1::110/128 CodeBGP Monitor PEERINGDB ASSIGNED ● high
2001:7f8::c4ee:0:1/128 CodeBGP Monitor PEERINGDB ASSIGNED ● high
2001:7f8:1::a505:414:1/128 CodeBGP Monitor PEERINGDB ASSIGNED ● high
2001:7f8:13::a505:414:1/128 CodeBGP Monitor PEERINGDB ASSIGNED ● high
2001:7f8:19:1::c4ee:1/128 CodeBGP Monitor PEERINGDB ASSIGNED ● high
2001:7f8:54::2:134/128 CodeBGP Monitor PEERINGDB ASSIGNED ● high
2001:7f8:54:8::13/128 CodeBGP Monitor PEERINGDB ASSIGNED ● high
2001:7f8:ca:1::132/128 CodeBGP Monitor PEERINGDB ASSIGNED ● high
2001:43f8:6d0::9:186/128 CodeBGP Monitor PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: B how networks compare →
88.9% of checked blocks have valid RPKI ROA coverage (16 of 18)
No discrepancies found among checked blocks.

NIC Handles

AS50414