Network · data from 2026-11-12
AS268146 PKNET SERVICOS DE TELECOMUNICACOES LTDA
Registry name: AS268146 - PKNET SERVICOS DE TELECOMUNICACOES LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268146, 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.169.254.0/24 | No ROA | Nonecovered by 45.169.254.0/23 | 672 100% |
| 45.169.255.0/24 | No ROA | Nonecovered by 45.169.254.0/23 | 672 100% |
| 2804:58bc::/33 | No ROA | Nonecovered by 2804:58bc::/32 | 635 100% |
| 2804:58bc:8000::/33 | No ROA | Nonecovered by 2804:58bc::/32 | 635 100% |
| 45.169.254.0/23 | No ROA | Other IRR onlyRADB, TC | 672 100% |
| 38.210.109.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2804:58bc::/32 | No ROA | Other IRR onlyRADB, TC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS268146: AS268146: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 (AS268146 isn't in the set, or no route object for AS268146 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 | AS268146 in it | Not covered |
|---|---|---|---|---|---|
| AS268146:AS-ANNOUNCEMENTS | TC | 1 | 2 | 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 14 are in fix.csv.
- ROA: none7
- Route object: none4
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.169.254.0/24 | No ROA covers it. Add a ROA for AS268146, maxLength 24. |
| Route object: none | 45.169.254.0/24 | No route object for it. A route object for 45.169.254.0/23 with origin AS268146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268146 in the RIR database for the space. |
| ROA: none | 45.169.255.0/24 | No ROA covers it. Add a ROA for AS268146, maxLength 24. |
| Route object: none | 45.169.255.0/24 | No route object for it. A route object for 45.169.254.0/23 with origin AS268146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268146 in the RIR database for the space. |
| ROA: none | 2804:58bc::/33 | No ROA covers it. Add a ROA for AS268146, maxLength 33. |
| Route object: none | 2804:58bc::/33 | No route object for it. A route object for 2804:58bc::/32 with origin AS268146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268146 in the RIR database for the space. |
| ROA: none | 2804:58bc:8000::/33 | No ROA covers it. Add a ROA for AS268146, maxLength 33. |
| Route object: none | 2804:58bc:8000::/33 | No route object for it. A route object for 2804:58bc::/32 with origin AS268146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268146 in the RIR database for the space. |
| ROA: none | 45.169.254.0/23 | No ROA covers it. Add a ROA for AS268146, maxLength 23. |
| Route object: RIR | 45.169.254.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 38.210.109.0/24 | No ROA covers it. Add a ROA for AS268146, maxLength 24. |
| Route object: RIR | 38.210.109.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:58bc::/32 | No ROA covers it. Add a ROA for AS268146, maxLength 32. |
| Route object: RIR | 2804:58bc::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS268146 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.