bgpreport

Network · data from 2026-11-12

AS30419 MediaMath

Registry name: PAEDAE-INC - PaeDae, Inc., US · PeeringDB

11IPv4 routes 27.3% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS30419, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS30419, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
74.121.136.0/24 No ROA Other IRR onlyRADB 672 100% 67
74.121.137.0/24 No ROA Other IRR onlyALTDB, BBOI, RADB 672 100% 67
74.121.138.0/24 No ROA Other IRR onlyRADB 672 100% 67
74.121.139.0/24 No ROA Other IRR onlyRADB 672 100% 67
74.121.141.0/24 No ROA Other IRR onlyRADB, REACH 672 100% 67
74.121.142.0/24 No ROA Other IRR onlyRADB 672 100% 67
74.121.143.0/24 No ROA Other IRR onlyRADB 672 100% 67
74.121.140.0/24 No ROA Other IRR onlyRADB 669 99% 67
64.125.96.0/24 Valid Other IRR onlyRADB 673 100% 67
216.200.232.0/24 Valid Other IRR onlyRADB 673 100% 67
216.200.233.0/24 Valid Other IRR onlyRADB 673 100% 67

AS-SET

AS30419's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 30 are in fix.csv.

  • ROA: none8
  • Route object: RIR11
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none74.121.136.0/24No ROA covers it. Add a ROA for AS30419, maxLength 24.672 of 673
Route object: RIR74.121.136.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.121.137.0/24No ROA covers it. Add a ROA for AS30419, maxLength 24.672 of 673
Route object: RIR74.121.137.0/24Route object only in ALTDB, BBOI, RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.121.138.0/24No ROA covers it. Add a ROA for AS30419, maxLength 24.672 of 673
Route object: RIR74.121.138.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.121.139.0/24No ROA covers it. Add a ROA for AS30419, maxLength 24.672 of 673
Route object: RIR74.121.139.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.121.141.0/24No ROA covers it. Add a ROA for AS30419, maxLength 24.672 of 673
Route object: RIR74.121.141.0/24Route object only in RADB, REACH. Add it in the RIR database for the space.672 of 673
ROA: none74.121.142.0/24No ROA covers it. Add a ROA for AS30419, maxLength 24.672 of 673
Route object: RIR74.121.142.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.121.143.0/24No ROA covers it. Add a ROA for AS30419, maxLength 24.672 of 673
Route object: RIR74.121.143.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.121.140.0/24No ROA covers it. Add a ROA for AS30419, maxLength 24.669 of 673
Route object: RIR74.121.140.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR64.125.96.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR216.200.232.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR216.200.233.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS30419 whose prefix no peer sees AS30419 announce. Many are kept on purpose (backup routes, space announced only in some places).

74.121.136.0/21ALTDB, REACHNo ROA
103.229.204.0/22NTTCOMNo ROA
103.229.204.0/23NTTCOMNo ROA
103.229.204.0/24NTTCOMNo ROA
103.229.205.0/24NTTCOMNo ROA
103.229.206.0/23NTTCOMNo ROA
103.229.206.0/24NTTCOMNo ROA
103.229.207.0/24NTTCOMNo ROA
185.29.134.0/23RADBNo ROA
185.29.134.0/24RADBNo ROA
192.100.214.0/24RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.