Network · data from 2026-11-12

AS28104 Eutel N.V.

Registry name: AS28104 - Eutel N.V., BQ · PeeringDB

13IPv4 routes 100.0% RPKI valid · 46.2% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 7 with no route object for this origin

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

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

Announced routes

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


138.185.208.0/24	Valid	Nonecovered by 138.185.208.0/22	667 99%	68
138.185.209.0/24	Valid	Nonecovered by 138.185.208.0/22	667 99%	68
138.185.210.0/24	Valid	Nonecovered by 138.185.208.0/22	667 99%	68
190.107.248.0/24	Valid	Nonecovered by 190.107.248.0/21	667 99%	68
190.107.249.0/24	Valid	Nonecovered by 190.107.248.0/21	667 99%	68
190.107.254.0/24	Valid	Nonecovered by 190.107.248.0/21	667 99%	68
190.107.255.0/24	Valid	Nonecovered by 190.107.248.0/21	667 99%	68
190.107.250.0/24	Valid	Other IRR onlyRADB	667 99%	68
190.107.251.0/24	Valid	Other IRR onlyRADB	667 99%	68
190.107.252.0/24	Valid	Other IRR onlyRADB	667 99%	68
190.107.253.0/24	Valid	Other IRR onlyRADB	667 99%	68
138.185.208.0/22	Valid	RIR databaseLACNIC, RADB	667 99%	68
190.107.248.0/21	Valid	RIR databaseLACNIC, RADB	667 99%	68

AS-SET

AS28104'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 11 are in fix.csv.

Route object: none7
Route object: RIR4

Change	Prefix or set	Detail	Full-table peers
Route object: none	138.185.208.0/24	No route object for it. A route object for 138.185.208.0/22 with origin AS28104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28104 in the RIR database for the space.	667 of 673
Route object: none	138.185.209.0/24	No route object for it. A route object for 138.185.208.0/22 with origin AS28104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28104 in the RIR database for the space.	667 of 673
Route object: none	138.185.210.0/24	No route object for it. A route object for 138.185.208.0/22 with origin AS28104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28104 in the RIR database for the space.	667 of 673
Route object: none	190.107.248.0/24	No route object for it. A route object for 190.107.248.0/21 with origin AS28104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28104 in the RIR database for the space.	667 of 673
Route object: none	190.107.249.0/24	No route object for it. A route object for 190.107.248.0/21 with origin AS28104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28104 in the RIR database for the space.	667 of 673
Route object: none	190.107.254.0/24	No route object for it. A route object for 190.107.248.0/21 with origin AS28104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28104 in the RIR database for the space.	667 of 673
Route object: none	190.107.255.0/24	No route object for it. A route object for 190.107.248.0/21 with origin AS28104 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28104 in the RIR database for the space.	667 of 673
Route object: RIR	190.107.250.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	190.107.251.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	190.107.252.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	190.107.253.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

138.185.208.0/24

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

667 of 673

Route object: none

138.185.209.0/24

667 of 673

Route object: none

138.185.210.0/24

667 of 673

Route object: none

190.107.248.0/24

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

667 of 673

Route object: none

190.107.249.0/24

667 of 673

Route object: none

190.107.254.0/24

667 of 673

Route object: none

190.107.255.0/24

667 of 673

Route object: RIR

190.107.250.0/24

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

667 of 673

Route object: RIR

190.107.251.0/24

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

667 of 673

Route object: RIR

190.107.252.0/24

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

667 of 673

Route object: RIR

190.107.253.0/24

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

667 of 673

Route objects not announced

Every route object with origin AS28104 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.