Network · data from 2026-11-12
AS270051 AS270051 - PLANET TELECOM COLOMBIA S.A.S
Registry name: AS270051 - PLANET TELECOM COLOMBIA S.A.S, CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270051, 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.
| 179.43.0.0/24 | Valid | Nonecovered by 179.43.0.0/22 | 673 100% |
| 179.43.2.0/24 | Valid | Nonecovered by 179.43.0.0/22 | 670 100% |
| 179.43.3.0/24 | Valid | Nonecovered by 179.43.0.0/22 | 670 100% |
| 179.43.1.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 2803:4de0:4::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2803:4de0:1::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 2803:4de0:2::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 2803:4de0:3::/48 | Valid | Other IRR onlyRADB | 634 100% |
AS-SET
AS270051 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 13 are in fix.csv.
- Route object: none3
- Route object: RIR5
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 179.43.0.0/24 | No route object for it. A route object for 179.43.0.0/22 with origin AS270051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270051 in the RIR database for the space. |
| Route object: none | 179.43.2.0/24 | No route object for it. A route object for 179.43.0.0/22 with origin AS270051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270051 in the RIR database for the space. |
| Route object: none | 179.43.3.0/24 | No route object for it. A route object for 179.43.0.0/22 with origin AS270051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270051 in the RIR database for the space. |
| Route object: RIR | 179.43.1.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2803:4de0:4::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2803:4de0:1::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2803:4de0:2::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2803:4de0:3::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270051 whose prefix no peer sees AS270051 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.43.0.0/22 | LACNIC | Valid |
| 2803:4de0::/32 | LACNIC, RADB | Valid |
| 2803:4de0:40::/42 | RADB | Valid |
| 2803:4de0:80::/42 | RADB | Valid |
| 2803:4de0:c0::/42 | 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.