Network · data from 2026-11-12

AS56396 Amobee Europe

Registry name: Amobee NEXXEN GROUP LTD, GB · PeeringDB

6IPv4 routes 83.3% RPKI valid · 33.3% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 4 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS56396, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56396, 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.


192.208.200.0/22	No ROA	Other IRR onlyNTTCOM, RADB	673 100%	67
46.228.168.0/22	Valid	Nonecovered by 46.228.160.0/20	673 100%	67
46.228.162.0/24	Valid	Nonecovered by 46.228.160.0/20	672 100%	67
46.228.163.0/24	Valid	Nonecovered by 46.228.160.0/20	672 100%	67
46.228.164.0/24	Valid	Nonecovered by 46.228.160.0/20	672 100%	67
46.228.160.0/20	Valid	Other IRR onlyRADB	673 100%	67
2001:678:cb4::/48	Valid	Other IRR onlyNTTCOM, RADB	636 100%	67

AS-SET

AS56396'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 8 are in fix.csv.

ROA: none1
Route object: none4
Route object: RIR3

Change	Prefix or set	Detail	Full-table peers
ROA: none	192.208.200.0/22	No ROA covers it. Add a ROA for AS56396, maxLength 22.	673 of 673
Route object: RIR	192.208.200.0/22	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: none	46.228.168.0/22	No route object for it. A route object for 46.228.160.0/20 with origin AS56396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56396 in the RIR database for the space.	673 of 673
Route object: none	46.228.162.0/24	No route object for it. A route object for 46.228.160.0/20 with origin AS56396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56396 in the RIR database for the space.	672 of 673
Route object: none	46.228.163.0/24	No route object for it. A route object for 46.228.160.0/20 with origin AS56396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56396 in the RIR database for the space.	672 of 673
Route object: none	46.228.164.0/24	No route object for it. A route object for 46.228.160.0/20 with origin AS56396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56396 in the RIR database for the space.	672 of 673
Route object: RIR	46.228.160.0/20	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	2001:678:cb4::/48	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

192.208.200.0/22

No ROA covers it. Add a ROA for AS56396, maxLength 22.

673 of 673

Route object: RIR

192.208.200.0/22

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

673 of 673

Route object: none

46.228.168.0/22

No route object for it. A route object for 46.228.160.0/20 with origin AS56396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56396 in the RIR database for the space.

673 of 673

Route object: none

46.228.162.0/24

672 of 673

Route object: none

46.228.163.0/24

672 of 673

Route object: none

46.228.164.0/24

672 of 673

Route object: RIR

46.228.160.0/20

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

2001:678:cb4::/48

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

636 of 636

Route objects not announced

Every route object with origin AS56396 is announced.

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.