bgpreport

Network · data from 2026-11-12

AS6336 Amobee, Inc.

Registry name: TURN-US-ASN - Turn Inc., US · PeeringDB

3IPv4 routes 0.0% RPKI valid · 33.3% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS6336, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS6336, 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.220.0/23 No ROA Nonecovered by 192.208.220.0/22 672 100% 67
192.208.222.0/23 No ROA Nonecovered by 192.208.220.0/22 669 99% 67
2620:112:f006::/48 No ROA Nonecovered by 2620:112:f000::/44 633 100% 68
192.208.220.0/22 No ROA RIR databaseARIN 672 100% 67

AS-SET

AS6336'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 24 are in fix.csv.

  • ROA: none4
  • Route object: none3
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none192.208.220.0/23No ROA covers it. Add a ROA for AS6336, maxLength 23.672 of 673
Route object: none192.208.220.0/23No route object for it. A route object for 192.208.220.0/22 with origin AS6336 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6336 in the RIR database for the space.672 of 673
ROA: none192.208.222.0/23No ROA covers it. Add a ROA for AS6336, maxLength 23.669 of 673
Route object: none192.208.222.0/23No route object for it. A route object for 192.208.220.0/22 with origin AS6336 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6336 in the RIR database for the space.669 of 673
ROA: none2620:112:f006::/48No ROA covers it. Add a ROA for AS6336, maxLength 48.633 of 636
Route object: none2620:112:f006::/48No route object for it. A route object for 2620:112:f000::/44 with origin AS6336 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6336 in the RIR database for the space.633 of 636
ROA: none192.208.220.0/22No ROA covers it. Add a ROA for AS6336, maxLength 22.672 of 673

Route objects not announced

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

8.22.36.0/23ALTDB, RADBNo ROA
8.22.36.0/24RADBNo ROA
8.22.37.0/24RADBNo ROA
50.116.192.0/18ALTDB, RADBNo ROA
50.116.192.0/20RADBNo ROA
50.116.208.0/20RADBNo ROA
50.116.224.0/20RADBNo ROA
50.116.236.0/22NTTCOMNo ROA
69.194.240.0/20ALTDB, RADBNo ROA
70.42.138.0/24ALTDBNo ROA
74.118.186.0/24ARINNo ROA
74.120.140.0/22ALTDB, RADBNo ROA
74.201.181.0/24ALTDBNo ROA
74.217.167.0/24ALTDBNo ROA
192.208.192.0/19RADBNo ROA
2001:df2:a300::/48RADBNo ROA
2620:112:f000::/44RADBNo 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.