MAGNITE, INC.
Magnite, Inc.
LEI
54930018FR2YX1HHSB02
Registered name
MAGNITE, INC.
Jurisdiction
US-DE
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks40
All fragments 44 blocks across 2 clusters
Cluster ID191608954
RegistryBGP
Owner jurisdictionUS-DE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Legal identityLEI 54930018FR2YX1HHSB02
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

Footprint over time

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

IP Ranges (40)

⬇ export CSV
CIDR Org name Registry Status Confidence
27.111.229.135/32 Magnite PEERINGDB ASSIGNED ● high
27.111.230.54/32 Magnite PEERINGDB ASSIGNED ● high
69.173.144.0/24 Magnite, Inc. BGP ANNOUNCED ● high
69.173.145.0/24 Magnite, Inc. BGP ANNOUNCED ● high
69.173.146.0/23 Magnite, Inc. BGP ANNOUNCED ● high
69.173.152.0/23 Magnite, Inc. BGP ANNOUNCED ● high
69.173.154.0/23 Magnite, Inc. BGP ANNOUNCED ● high
69.173.156.0/23 Magnite, Inc. BGP ANNOUNCED ● high
69.173.158.0/24 Magnite, Inc. BGP ANNOUNCED ● high
80.81.193.126/32 Magnite PEERINGDB ASSIGNED ● high
80.81.193.147/32 Magnite PEERINGDB ASSIGNED ● high
80.249.212.237/32 Magnite PEERINGDB ASSIGNED ● high
80.249.215.235/32 Magnite PEERINGDB ASSIGNED ● high
191.215.64.0/19 Magnite, Inc. BGP ANNOUNCED ● high
193.239.119.7/32 Magnite PEERINGDB ASSIGNED ● high
206.126.237.164/32 Magnite PEERINGDB ASSIGNED ● high
206.126.237.165/32 Magnite PEERINGDB ASSIGNED ● high
206.223.116.40/32 Magnite PEERINGDB ASSIGNED ● high
206.223.117.40/32 Magnite PEERINGDB ASSIGNED ● high
216.19.192.0/20 Magnite, Inc. BGP ANNOUNCED ● high
216.19.208.0/20 Magnite, Inc. BGP ANNOUNCED ● high
216.109.160.0/20 Magnite, Inc. BGP ANNOUNCED ● high
2001:504:0:1:0:2:6667:1/128 Magnite PEERINGDB ASSIGNED ● high
2001:504:0:1:0:2:6667:2/128 Magnite PEERINGDB ASSIGNED ● high
2001:504:0:2:0:2:6667:1/128 Magnite PEERINGDB ASSIGNED ● high
2001:504:0:2:0:2:6667:2/128 Magnite PEERINGDB ASSIGNED ● high
2001:7f8::682b:0:1/128 Magnite PEERINGDB ASSIGNED ● high
2001:7f8::682b:0:2/128 Magnite PEERINGDB ASSIGNED ● high
2001:7f8:1::a502:6667:1/128 Magnite PEERINGDB ASSIGNED ● high
2001:7f8:1::a502:6667:2/128 Magnite PEERINGDB ASSIGNED ● high
2001:7f8:13::a502:6667:1/128 Magnite PEERINGDB ASSIGNED ● high
2001:de8:4::2:6667:1/128 Magnite PEERINGDB ASSIGNED ● high
2001:de8:4::2:6667:2/128 Magnite PEERINGDB ASSIGNED ● high
2602:803:c002::/48 Magnite, Inc. BGP ANNOUNCED ● high
2602:803:c003::/48 Magnite, Inc. BGP ANNOUNCED ● high
2602:803:c004::/48 Magnite, Inc. BGP ANNOUNCED ● high
2602:803:c005::/48 Magnite, Inc. BGP ANNOUNCED ● high
2602:803:c006::/48 Magnite, Inc. BGP ANNOUNCED ● high
2602:803:c007::/48 Magnite, Inc. BGP ANNOUNCED ● high
2602:803:c008::/48 Magnite, Inc. BGP ANNOUNCED ● high

Corporate group (4 entities) ~

top 2 shown — full list (JSON)

Network trust

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

NIC Handles

AS26667 AS26667