Network · data from 2026-11-12
AS270793 CONECTA TELECOM (c.i.t)
Registry name: AS270793 - CONECTA TELECOM LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270793, 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.
| 201.159.160.0/23 | Valid | Nonecovered by 201.159.160.0/22 | 672 100% |
| 2804:7180::/34 | Valid | Nonecovered by 2804:7180::/33 | 634 100% |
| 2804:7180:4000::/34 | Valid | Nonecovered by 2804:7180::/33 | 634 100% |
| 2804:7180:8000::/34 | Valid | Nonecovered by 2804:7180:8000::/33 | 634 100% |
| 2804:7180:c000::/34 | Valid | Nonecovered by 2804:7180:8000::/33 | 634 100% |
| 201.159.160.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 201.159.160.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 201.159.163.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 201.159.161.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 201.159.162.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 2804:7180::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:7180::/33 | Valid | Other IRR onlyRADB | 634 100% |
AS-SET
AS270793's PeeringDB record names no 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 16 are in fix.csv.
- Route object: none5
- Route object: RIR7
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 201.159.160.0/23 | No route object for it. A route object for 201.159.160.0/22 with origin AS270793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270793 in the RIR database for the space. |
| Route object: none | 2804:7180::/34 | No route object for it. A route object for 2804:7180::/33 with origin AS270793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270793 in the RIR database for the space. |
| Route object: none | 2804:7180:4000::/34 | No route object for it. A route object for 2804:7180::/33 with origin AS270793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270793 in the RIR database for the space. |
| Route object: none | 2804:7180:8000::/34 | No route object for it. A route object for 2804:7180:8000::/33 with origin AS270793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270793 in the RIR database for the space. |
| Route object: none | 2804:7180:c000::/34 | No route object for it. A route object for 2804:7180:8000::/33 with origin AS270793 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270793 in the RIR database for the space. |
| Route object: RIR | 201.159.160.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 201.159.160.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.159.163.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.159.161.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.159.162.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7180::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7180::/33 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270793 whose prefix no peer sees AS270793 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 201.159.164.0/24 | RADB | No ROA |
| 2804:7180::/40 | RADB | Valid |
| 2804:7180:100::/40 | RADB | Valid |
| 2804:7180:8000::/33 | RADB | Valid |
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.