Network · data from 2026-11-12
AS263221 AS263221 - ALVIS S.A.
Registry name: AS263221 - ALVIS S.A., AR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263221, 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.
| 161.0.178.0/24 | Valid | Nonecovered by 161.0.176.0/21 | 671 100% |
| 161.0.181.0/24 | Valid | Nonecovered by 161.0.176.0/21 | 671 100% |
| 161.0.179.0/24 | Valid | Nonecovered by 161.0.176.0/21 | 670 100% |
| 161.0.180.0/24 | Valid | Nonecovered by 161.0.176.0/21 | 670 100% |
| 161.0.182.0/24 | Valid | Nonecovered by 161.0.176.0/21 | 670 100% |
| 161.0.183.0/24 | Valid | Nonecovered by 161.0.176.0/21 | 670 100% |
| 161.0.176.0/24 | Valid | Nonecovered by 161.0.176.0/21 | 2 0%low visibility |
| 161.0.177.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 201.251.40.0/24 | Valid | RIR databaseLACNIC | 2 0%low visibility |
AS-SET
AS263221 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: none7
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 161.0.178.0/24 | No route object for it. A route object for 161.0.176.0/21 with origin AS263221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263221 in the RIR database for the space. |
| Route object: none | 161.0.181.0/24 | No route object for it. A route object for 161.0.176.0/21 with origin AS263221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263221 in the RIR database for the space. |
| Route object: none | 161.0.179.0/24 | No route object for it. A route object for 161.0.176.0/21 with origin AS263221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263221 in the RIR database for the space. |
| Route object: none | 161.0.180.0/24 | No route object for it. A route object for 161.0.176.0/21 with origin AS263221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263221 in the RIR database for the space. |
| Route object: none | 161.0.182.0/24 | No route object for it. A route object for 161.0.176.0/21 with origin AS263221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263221 in the RIR database for the space. |
| Route object: none | 161.0.183.0/24 | No route object for it. A route object for 161.0.176.0/21 with origin AS263221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263221 in the RIR database for the space. |
| Route object: none | 161.0.176.0/24 | No route object for it. A route object for 161.0.176.0/21 with origin AS263221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263221 in the RIR database for the space. |
| Route object: RIR | 161.0.177.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263221 whose prefix no peer sees AS263221 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 161.0.176.0/21 | RADB | Valid |
| 2803:a680::/32 | 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.