bgpreport

Network · data from 2026-11-12

AS263821 AS263821 - Soluciones Favorables

Registry name: AS263821 - Soluciones Favorables, HN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263821, 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.219.120.0/22 Valid Other IRR onlyALTDB, RADB, RIPE-NONAUTH 673 100% 67
170.244.144.0/22 Valid Other IRR onlyALTDB, RIPE-NONAUTH 673 100% 67
138.59.4.0/22 Valid Other IRR onlyALTDB, RIPE-NONAUTH 666 99% 67
161.0.68.0/22 Valid Other IRR onlyALTDB, RIPE-NONAUTH 666 99% 67
168.181.52.0/22 Valid Other IRR onlyALTDB, RIPE-NONAUTH 666 99% 67
177.234.136.0/21 Valid Other IRR onlyALTDB, RIPE-NONAUTH 666 99% 67
200.0.60.0/23 Valid Other IRR onlyALTDB, RIPE-NONAUTH 665 99% 67
200.71.124.0/22 Valid Other IRR onlyALTDB, RIPE-NONAUTH 665 99% 67
200.189.44.0/22 Valid Other IRR onlyALTDB, RIPE-NONAUTH 665 99% 67
2803:e680::/32 Valid Other IRR onlyALTDB 634 100% 67

AS-SET

AS263821 isn't in PeeringDB, where networks name their 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 10 are in fix.csv.

  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
Route object: RIR138.219.120.0/22Route object only in ALTDB, RADB, RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR170.244.144.0/22Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR138.59.4.0/22Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.666 of 673
Route object: RIR161.0.68.0/22Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.666 of 673
Route object: RIR168.181.52.0/22Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.666 of 673
Route object: RIR177.234.136.0/21Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.666 of 673
Route object: RIR200.0.60.0/23Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.665 of 673
Route object: RIR200.71.124.0/22Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.665 of 673
Route object: RIR200.189.44.0/22Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.665 of 673
Route object: RIR2803:e680::/32Route object only in ALTDB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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