Network · data from 2026-11-12
AS269111 Netlink Provedor
Registry name: AS269111 - Netlink Provedor, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269111, 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.
| 45.178.212.0/24 | No ROA | Other IRR onlyALTDB, RADB, TC | 668 99% |
| 45.178.214.0/24 | No ROA | Other IRR onlyALTDB, RADB, TC | 668 99% |
| 45.178.215.0/24 | No ROA | Other IRR onlyALTDB, RADB, TC | 668 99% |
| 2804:5f98::/32 | No ROA | Other IRR onlyALTDB, RADB, TC | 627 99% |
| 2804:5f98::/33 | No ROA | Other IRR onlyRADB, TC | 627 99% |
| 2804:5f98:8000::/33 | No ROA | Other IRR onlyRADB, TC | 627 99% |
| 45.178.212.0/23 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 45.178.214.0/23 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS269111: AS269111. 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 (AS269111 isn't in the set, or no route object for AS269111 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 | AS269111 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS269111 | A single AS number, not a set: AS269111 (this network), 10 route objects. | |||||
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 18 are in fix.csv.
- ROA: none8
- Route object: RIR8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.178.212.0/24 | No ROA covers it. Add a ROA for AS269111, maxLength 24. |
| Route object: RIR | 45.178.212.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 45.178.214.0/24 | No ROA covers it. Add a ROA for AS269111, maxLength 24. |
| Route object: RIR | 45.178.214.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 45.178.215.0/24 | No ROA covers it. Add a ROA for AS269111, maxLength 24. |
| Route object: RIR | 45.178.215.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:5f98::/32 | No ROA covers it. Add a ROA for AS269111, maxLength 32. |
| Route object: RIR | 2804:5f98::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:5f98::/33 | No ROA covers it. Add a ROA for AS269111, maxLength 33. |
| Route object: RIR | 2804:5f98::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:5f98:8000::/33 | No ROA covers it. Add a ROA for AS269111, maxLength 33. |
| Route object: RIR | 2804:5f98:8000::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 45.178.212.0/23 | No ROA covers it. Add a ROA for AS269111, maxLength 23. |
| Route object: RIR | 45.178.212.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.178.214.0/23 | No ROA covers it. Add a ROA for AS269111, maxLength 23. |
| Route object: RIR | 45.178.214.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269111 whose prefix no peer sees AS269111 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.178.212.0/22 | ALTDB, RADB, TC | No ROA |
| 45.178.213.0/24 | ALTDB, RADB, TC | 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.