Network · data from 2026-11-12

AS262237 Orbyta

Registry name: AS262237 - Orbyta S.A., CL · PeeringDB

38IPv4 routes 86.8% RPKI valid · 97.4% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

5No ROA 1 with no route object for this origin

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

11Route objects not announced registered with origin AS262237, seen from no peer

Announced routes

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


170.82.128.0/24	No ROA	Other IRR onlyRADB	672 100%	66
170.82.129.0/24	No ROA	Other IRR onlyRADB	672 100%	66
200.91.45.0/24	No ROA	Other IRR onlyRADB	671 100%	66
200.91.46.0/24	No ROA	Other IRR onlyRADB	671 100%	66
200.91.47.0/24	No ROA	Other IRR onlyRADB	671 100%	66
200.29.230.0/24	Valid	Other origin only	672 100%	66
161.0.160.0/24	Valid	RIR databaseLACNIC, NTTCOM, RADB	672 100%	66
161.0.162.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.163.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.164.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.166.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.167.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.168.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.169.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.170.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.171.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.172.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.173.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.174.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
161.0.175.0/24	Valid	RIR databaseLACNIC, NTTCOM	672 100%	66
190.196.208.0/24	Valid	RIR databaseLACNIC, RADB	671 100%	66
190.196.210.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.196.212.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.196.213.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.196.214.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.196.215.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.196.218.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.196.220.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.196.221.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.196.222.0/24	Valid	RIR databaseLACNIC	671 100%	66
190.196.223.0/24	Valid	RIR databaseLACNIC	671 100%	66
161.0.161.0/24	Valid	RIR databaseLACNIC, NTTCOM	666 99%	67
161.0.165.0/24	Valid	RIR databaseLACNIC, NTTCOM	666 99%	67
190.196.209.0/24	Valid	RIR databaseLACNIC	665 99%	67
190.196.211.0/24	Valid	RIR databaseLACNIC	665 99%	67
190.196.216.0/24	Valid	RIR databaseLACNIC	665 99%	67
190.196.217.0/24	Valid	RIR databaseLACNIC	665 99%	67
190.196.219.0/24	Valid	RIR databaseLACNIC	665 99%	67
2803:6200::/32	Valid	RIR databaseLACNIC, RADB	636 100%	67

AS-SET

AS262237'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 22 are in fix.csv.

ROA: none5
Route object: none1
Route object: RIR5
Route object: not announced11

Change	Prefix or set	Detail	Full-table peers
ROA: none	170.82.128.0/24	No ROA covers it. Add a ROA for AS262237, maxLength 24.	672 of 673
Route object: RIR	170.82.128.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	170.82.129.0/24	No ROA covers it. Add a ROA for AS262237, maxLength 24.	672 of 673
Route object: RIR	170.82.129.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	200.91.45.0/24	No ROA covers it. Add a ROA for AS262237, maxLength 24.	671 of 673
Route object: RIR	200.91.45.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	200.91.46.0/24	No ROA covers it. Add a ROA for AS262237, maxLength 24.	671 of 673
Route object: RIR	200.91.46.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	200.91.47.0/24	No ROA covers it. Add a ROA for AS262237, maxLength 24.	671 of 673
Route object: RIR	200.91.47.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: none	200.29.230.0/24	Route objects for it name AS14708. Add a route object with origin AS262237 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

170.82.128.0/24

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

672 of 673

Route object: RIR

170.82.128.0/24

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

672 of 673

ROA: none

170.82.129.0/24

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

672 of 673

Route object: RIR

170.82.129.0/24

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

672 of 673

ROA: none

200.91.45.0/24

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

671 of 673

Route object: RIR

200.91.45.0/24

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

671 of 673

ROA: none

200.91.46.0/24

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

671 of 673

Route object: RIR

200.91.46.0/24

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

671 of 673

ROA: none

200.91.47.0/24

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

671 of 673

Route object: RIR

200.91.47.0/24

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

671 of 673

Route object: none

200.29.230.0/24

Route objects for it name AS14708. Add a route object with origin AS262237 in the RIR database for the space.

672 of 673

Route objects not announced

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


45.234.156.0/22	NTTCOM, RADB	No ROA
161.0.160.0/20	NTTCOM, RADB	No ROA
168.197.180.0/22	NTTCOM, RADB	No ROA
170.82.128.0/22	RADB	No ROA
170.82.130.0/24	RADB	No ROA
170.82.131.0/24	RADB	No ROA
190.196.208.0/20	NTTCOM, RADB	No ROA
191.102.32.0/22	RADB	No ROA
2801:1d:7000::/48	RADB	No ROA
2803:6200::/64	LACNIC	Valid
2803:ca80::/32	RADB	No ROA

45.234.156.0/22

NTTCOM, RADB

No ROA

161.0.160.0/20

NTTCOM, RADB

No ROA

168.197.180.0/22

NTTCOM, RADB

No ROA

170.82.128.0/22

RADB

No ROA

170.82.130.0/24

RADB

No ROA

170.82.131.0/24

RADB

No ROA

190.196.208.0/20

NTTCOM, RADB

No ROA

191.102.32.0/22

RADB

No ROA

2801:1d:7000::/48

RADB

No ROA

2803:6200::/64

LACNIC

Valid

2803:ca80::/32

RADB

No 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.