Network · data from 2026-11-12
AS268327 AS268327 - K@NET PROVEDOR DE INTERNET
Registry name: AS268327 - K@NET PROVEDOR DE INTERNET, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268327, 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.238.132.0/23 | Valid | Nonecovered by 45.238.132.0/22 | 671 100% |
| 45.238.134.0/23 | Valid | Nonecovered by 45.238.132.0/22 | 671 100% |
| 45.238.135.0/24 | Valid | Nonecovered by 45.238.132.0/22 | 661 98% |
| 2804:4f70:c000::/34 | Valid | Nonecovered by 2804:4f70::/32 | 628 99% |
| 45.238.132.0/24 | Valid | Nonecovered by 45.238.132.0/22 | 2 0%low visibility |
| 45.238.133.0/24 | Valid | Nonecovered by 45.238.132.0/22 | 2 0%low visibility |
| 45.238.134.0/24 | Valid | Nonecovered by 45.238.132.0/22 | 2 0%low visibility |
| 45.238.132.0/22 | Valid | Other IRR onlyTC | 671 100% |
| 2804:4f70::/32 | Valid | Other IRR onlyTC | 634 100% |
AS-SET
AS268327 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 9 are in fix.csv.
- Route object: none7
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.238.132.0/23 | No route object for it. A route object for 45.238.132.0/22 with origin AS268327 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268327 in the RIR database for the space. |
| Route object: none | 45.238.134.0/23 | No route object for it. A route object for 45.238.132.0/22 with origin AS268327 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268327 in the RIR database for the space. |
| Route object: none | 45.238.135.0/24 | No route object for it. A route object for 45.238.132.0/22 with origin AS268327 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268327 in the RIR database for the space. |
| Route object: none | 2804:4f70:c000::/34 | No route object for it. A route object for 2804:4f70::/32 with origin AS268327 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268327 in the RIR database for the space. |
| Route object: none | 45.238.132.0/24 | No route object for it. A route object for 45.238.132.0/22 with origin AS268327 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268327 in the RIR database for the space. |
| Route object: none | 45.238.133.0/24 | No route object for it. A route object for 45.238.132.0/22 with origin AS268327 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268327 in the RIR database for the space. |
| Route object: none | 45.238.134.0/24 | No route object for it. A route object for 45.238.132.0/22 with origin AS268327 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268327 in the RIR database for the space. |
| Route object: RIR | 45.238.132.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:4f70::/32 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS268327 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.