Network · data from 2026-11-12
AS266312 NaveNet Telecom
Registry name: AS266312 - NaveNet servicos de internet ltda, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266312, 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.238.56.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.238.56.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.238.57.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.238.58.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.238.59.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 179.51.130.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 179.51.131.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 181.224.52.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 181.224.53.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 181.224.54.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 181.224.55.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 189.90.232.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 189.90.232.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 189.90.234.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 189.90.235.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 189.90.233.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 2804:35e0::/36 | Valid | Other IRR onlyRADB, TC | 632 99% |
| 2804:35e0:1000::/36 | Valid | Other IRR onlyRADB, TC | 632 99% |
| 2804:35e0:2000::/36 | Valid | Other IRR onlyRADB, TC | 628 99% |
AS-SET
PeeringDB's irr_as_set for AS266312: AS266312:AS-ANNOUNCEMENTS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS266312 isn't in the set, or no route object for AS266312 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS266312 in it | Not covered |
|---|---|---|---|---|---|
| AS266312:AS-ANNOUNCEMENTS | TC | 1 | 3 | Yes | 0 |
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 24 are in fix.csv.
- Route object: RIR19
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 170.238.56.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.238.56.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.238.57.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.238.58.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.238.59.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.51.130.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.51.131.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 181.224.52.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 181.224.53.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 181.224.54.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 181.224.55.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 189.90.232.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 189.90.232.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 189.90.234.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 189.90.235.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 189.90.233.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:35e0::/36 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:35e0:1000::/36 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:35e0:2000::/36 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266312 whose prefix no peer sees AS266312 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.51.130.0/23 | TC | No ROA |
| 181.224.52.0/22 | RADB, TC | Valid |
| 2804:35e0::/32 | RADB, TC | No ROA |
| 2804:35e0::/44 | RADB | Valid |
| 2804:35e0:ff00::/40 | 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.