Network · data from 2026-11-12
AS270364 NOVALINK INTERNET AS270364
Registry name: AS270364 - NOVALINK INTERNET LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270364, 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.
| 190.89.92.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 190.89.94.0/23 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 190.89.92.0/22 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 190.89.92.0/23 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 190.89.93.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 190.89.94.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 190.89.95.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 2804:6ae4::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
| 2804:6ae4::/33 | Valid | Other IRR onlyRADB, TC | 634 100% |
| 2804:6ae4:8000::/33 | Valid | Other IRR onlyRADB, TC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS270364: AS270364:AS-CUSTOMERS. 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 (AS270364 isn't in the set, or no route object for AS270364 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 | AS270364 in it | Not covered |
|---|---|---|---|---|---|
| AS270364:AS-CUSTOMERS | TC | 3 | 1 | 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 10 are in fix.csv.
- Route object: RIR10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 190.89.92.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.89.94.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.89.92.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.89.92.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.89.93.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.89.94.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.89.95.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6ae4::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6ae4::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6ae4:8000::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS270364 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.