Network · data from 2026-11-12

AS263713 Cyberfuel

Registry name: AS263713 - Server Lodge S.A., CR · PeeringDB

9IPv4 routes 88.9% RPKI valid · 33.3% with a route object

3IPv6 routes 100.0% RPKI valid · 33.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 8 with no route object for this origin

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

1Route objects not announced registered with origin AS263713, seen from no peer

Announced routes

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


199.184.169.0/24	No ROA	Other IRR onlyRADB	669 99%	68
190.0.230.0/24	Valid	Nonecovered by 190.0.224.0/21	668 99%	68
190.0.224.0/24	Valid	Nonecovered by 190.0.224.0/21	666 99%	68
190.0.226.0/24	Valid	Nonecovered by 190.0.224.0/21	666 99%	68
190.0.227.0/24	Valid	Nonecovered by 190.0.224.0/21	666 99%	68
190.0.229.0/24	Valid	Nonecovered by 190.0.224.0/21	666 99%	68
190.0.231.0/24	Valid	Nonecovered by 190.0.224.0/21	666 99%	68
2803:7a80::/48	Valid	Nonecovered by 2803:7a80::/32	635 100%	68
2803:7a80:9be::/48	Valid	Nonecovered by 2803:7a80::/32	634 100%	68
190.0.224.0/21	Valid	Other IRR onlyRADB	668 99%	68
190.0.225.0/24	Valid	Other IRR onlyRADB	668 99%	68
2803:7a80::/32	Valid	Other IRR onlyRADB	635 100%	68

AS-SET

AS263713'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 14 are in fix.csv.

ROA: none1
Route object: none8
Route object: RIR4
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	199.184.169.0/24	No ROA covers it. Add a ROA for AS263713, maxLength 24.	669 of 673
Route object: RIR	199.184.169.0/24	Route object only in RADB. Add it in the RIR database for the space.	669 of 673
Route object: none	190.0.230.0/24	No route object for it. A route object for 190.0.224.0/21 with origin AS263713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263713 in the RIR database for the space.	668 of 673
Route object: none	190.0.224.0/24	No route object for it. A route object for 190.0.224.0/21 with origin AS263713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263713 in the RIR database for the space.	666 of 673
Route object: none	190.0.226.0/24	No route object for it. A route object for 190.0.224.0/21 with origin AS263713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263713 in the RIR database for the space.	666 of 673
Route object: none	190.0.227.0/24	No route object for it. A route object for 190.0.224.0/21 with origin AS263713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263713 in the RIR database for the space.	666 of 673
Route object: none	190.0.229.0/24	No route object for it. A route object for 190.0.224.0/21 with origin AS263713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263713 in the RIR database for the space.	666 of 673
Route object: none	190.0.231.0/24	No route object for it. A route object for 190.0.224.0/21 with origin AS263713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263713 in the RIR database for the space.	666 of 673
Route object: none	2803:7a80::/48	No route object for it. A route object for 2803:7a80::/32 with origin AS263713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263713 in the RIR database for the space.	635 of 636
Route object: none	2803:7a80:9be::/48	No route object for it. A route object for 2803:7a80::/32 with origin AS263713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263713 in the RIR database for the space.	634 of 636
Route object: RIR	190.0.224.0/21	Route object only in RADB. Add it in the RIR database for the space.	668 of 673
Route object: RIR	190.0.225.0/24	Route object only in RADB. Add it in the RIR database for the space.	668 of 673
Route object: RIR	2803:7a80::/32	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

199.184.169.0/24

No ROA covers it. Add a ROA for AS263713, maxLength 24.

669 of 673

Route object: RIR

199.184.169.0/24

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

669 of 673

Route object: none

190.0.230.0/24

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

668 of 673

Route object: none

190.0.224.0/24

666 of 673

Route object: none

190.0.226.0/24

666 of 673

Route object: none

190.0.227.0/24

666 of 673

Route object: none

190.0.229.0/24

666 of 673

Route object: none

190.0.231.0/24

666 of 673

Route object: none

2803:7a80::/48

No route object for it. A route object for 2803:7a80::/32 with origin AS263713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263713 in the RIR database for the space.

635 of 636

Route object: none

2803:7a80:9be::/48

634 of 636

Route object: RIR

190.0.224.0/21

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

668 of 673

Route object: RIR

190.0.225.0/24

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

668 of 673

Route object: RIR

2803:7a80::/32

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

635 of 636

Route objects not announced

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


190.0.228.0/24	RADB	Valid

190.0.228.0/24

RADB

Valid

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.