Network · data from 2026-11-12
AS61451 AS61451 - WAVENET S.A.
Registry name: AS61451 - WAVENET S.A., AR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61451, 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.
| 148.222.151.0/24 | Valid | Nonecovered by 148.222.144.0/21 | 1 0%low visibility |
| 45.173.0.0/22 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 148.222.144.0/21 | Valid | RIR databaseLACNIC | 671 100% |
| 148.222.156.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 148.222.159.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 2803:c060::/32 | Valid | RIR databaseLACNIC, RADB | 633 100% |
AS-SET
AS61451 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 4 are in fix.csv.
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 148.222.151.0/24 | No route object for it. A route object for 148.222.144.0/21 with origin AS61451 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61451 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61451 whose prefix no peer sees AS61451 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 181.119.19.0/24 | RADB | No ROA |
| 181.119.20.0/24 | RADB | No ROA |
| 181.119.21.0/24 | 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.