Network · data from 2026-11-12
AS270467 AS270467 - Conecta Telecom
Registry name: AS270467 - Conecta Telecom, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270467, 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.
| 200.50.200.0/22 | Valid | Other IRR onlyRADB, TC | 664 99% |
| 2804:6c6c::/32 | Valid | Other IRR onlyRADB, TC | 636 100% |
| 200.50.200.0/24 | Valid | Other IRR onlyRADB, TC | 6 1%low visibility |
| 200.50.201.0/24 | Valid | Other IRR onlyRADB, TC | 6 1%low visibility |
| 200.50.202.0/24 | Valid | Other IRR onlyRADB, TC | 6 1%low visibility |
| 200.50.203.0/24 | Valid | Other IRR onlyRADB, TC | 6 1%low visibility |
| 2804:6c6c::/34 | Valid | Other IRR onlyRADB, TC | 5 1%low visibility |
| 2804:6c6c:4000::/34 | Valid | Other IRR onlyRADB, TC | 5 1%low visibility |
| 2804:6c6c:8000::/34 | Valid | Other IRR onlyRADB, TC | 5 1%low visibility |
| 2804:6c6c:c000::/34 | Valid | Other IRR onlyRADB, TC | 5 1%low visibility |
AS-SET
AS270467 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 38 are in fix.csv.
- Route object: RIR10
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 200.50.200.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6c6c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.50.200.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.50.201.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.50.202.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.50.203.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6c6c::/34 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6c6c:4000::/34 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6c6c:8000::/34 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6c6c:c000::/34 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270467 whose prefix no peer sees AS270467 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.50.200.0/23 | RADB, TC | Valid |
| 200.50.202.0/23 | RADB, TC | Valid |
| 2804:6c6c::/33 | RADB, TC | Valid |
| 2804:6c6c::/35 | RADB | Valid |
| 2804:6c6c::/36 | RADB | Valid |
| 2804:6c6c:1000::/36 | RADB | Valid |
| 2804:6c6c:2000::/35 | RADB | Valid |
| 2804:6c6c:2000::/36 | RADB | Valid |
| 2804:6c6c:3000::/36 | RADB | Valid |
| 2804:6c6c:4000::/35 | RADB | Valid |
| 2804:6c6c:4000::/36 | RADB | Valid |
| 2804:6c6c:5000::/36 | RADB | Valid |
| 2804:6c6c:6000::/35 | RADB | Valid |
| 2804:6c6c:6000::/36 | RADB | Valid |
| 2804:6c6c:7000::/36 | RADB | Valid |
| 2804:6c6c:8000::/33 | RADB, TC | Valid |
| 2804:6c6c:8000::/35 | RADB | Valid |
| 2804:6c6c:8000::/36 | RADB | Valid |
| 2804:6c6c:9000::/36 | RADB | Valid |
| 2804:6c6c:a000::/35 | RADB | Valid |
| 2804:6c6c:a000::/36 | RADB | Valid |
| 2804:6c6c:b000::/36 | RADB | Valid |
| 2804:6c6c:c000::/35 | RADB | Valid |
| 2804:6c6c:c000::/36 | RADB | Valid |
| 2804:6c6c:d000::/36 | RADB | Valid |
| 2804:6c6c:e000::/35 | RADB | Valid |
| 2804:6c6c:e000::/36 | RADB | Valid |
| 2804:6c6c:f000::/36 | 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.