Network · data from 2026-11-12
AS271323 AS271323 - CONNECT TELECOM LTDA
Registry name: AS271323 - CONNECT TELECOM LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271323, 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.
| 2804:79b8:2000::/36 | No ROA | Nonecovered by 2804:79b8::/32 | 629 99% |
| 164.163.165.0/24 | Valid | Nonecovered by 164.163.164.0/22 | 666 99% |
| 164.163.164.0/24 | Valid | Nonecovered by 164.163.164.0/22 | 665 99% |
| 164.163.166.0/24 | Valid | Nonecovered by 164.163.164.0/22 | 665 99% |
| 2804:79b8:3000::/36 | Valid | Nonecovered by 2804:79b8::/32 | 629 99% |
| 2804:79b8:4000::/36 | Valid | Nonecovered by 2804:79b8::/32 | 629 99% |
| 190.123.68.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 190.123.71.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 190.123.69.0/24 | Valid | Other IRR onlyRADB | 666 99% |
| 2804:79b8:1000::/36 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS271323 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 18 are in fix.csv.
- ROA: none1
- Route object: none6
- Route object: RIR4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:79b8:2000::/36 | No ROA covers it. Add a ROA for AS271323, maxLength 36. |
| Route object: none | 2804:79b8:2000::/36 | No route object for it. A route object for 2804:79b8::/32 with origin AS271323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271323 in the RIR database for the space. |
| Route object: none | 164.163.165.0/24 | No route object for it. A route object for 164.163.164.0/22 with origin AS271323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271323 in the RIR database for the space. |
| Route object: none | 164.163.164.0/24 | No route object for it. A route object for 164.163.164.0/22 with origin AS271323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271323 in the RIR database for the space. |
| Route object: none | 164.163.166.0/24 | No route object for it. A route object for 164.163.164.0/22 with origin AS271323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271323 in the RIR database for the space. |
| Route object: none | 2804:79b8:3000::/36 | No route object for it. A route object for 2804:79b8::/32 with origin AS271323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271323 in the RIR database for the space. |
| Route object: none | 2804:79b8:4000::/36 | No route object for it. A route object for 2804:79b8::/32 with origin AS271323 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271323 in the RIR database for the space. |
| Route object: RIR | 190.123.68.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.123.71.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.123.69.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:79b8:1000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271323 whose prefix no peer sees AS271323 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 164.163.164.0/22 | RADB, TC | No ROA |
| 190.123.68.0/22 | RADB, TC | No ROA |
| 190.123.70.0/23 | RADB | No ROA |
| 190.123.70.0/24 | RADB | No ROA |
| 2804:79b8::/32 | RADB, TC | No ROA |
| 2804:79b8:9e00::/40 | RADB | No ROA |
| 2804:79b8:9f00::/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.