MIXP Ops

Data as of 2026-11-01
BGP inherited
This organisation
Netblocks10
IPv6 5 prefixes (largest 2001:43f8:270:d0d0::115/128)
Record ID260812801
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
196.223.0.15/32 MIXP Ops PEERINGDB ASSIGNED ● high
196.223.0.115/32 MIXP Ops PEERINGDB ASSIGNED ● high
196.223.0.199/32 MIXP Ops PEERINGDB ASSIGNED ● high
196.223.0.201/32 MIXP Route Servers PEERINGDB ASSIGNED ● high
196.223.0.202/32 MIXP Route Servers PEERINGDB ASSIGNED ● high
2001:43f8:270:d0d0::15/128 MIXP Ops PEERINGDB ASSIGNED ● high
2001:43f8:270:d0d0::115/128 MIXP Ops PEERINGDB ASSIGNED ● high
2001:43f8:270:d0d0::199/128 MIXP Ops PEERINGDB ASSIGNED ● high
2001:43f8:270:d0d0::201/128 MIXP Route Servers PEERINGDB ASSIGNED ● high
2001:43f8:270:d0d0::202/128 MIXP Route Servers PEERINGDB ASSIGNED ● high

IPv6 ranges (5)

Footprint over time

19 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-11-01

Network trust

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

NIC Handles

AS327821 AS37324