Network · data from 2026-11-12
AS64140 PIT - Colombia - Bogota Route Servers
Registry name: AS64140 - PIT COLOMBIA SAS, CO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS64140, 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.
| 134.135.176.0/20 | No ROA | None | 672 100% |
| 209.22.138.0/24 | No ROA | None | 672 100% |
| 214.3.145.0/24 | No ROA | None | 671 100% |
| 214.29.74.0/23 | No ROA | None | 671 100% |
| 214.37.140.0/22 | No ROA | None | 671 100% |
| 214.65.0.0/20 | No ROA | None | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS64140: AS-PITCOLOMBIA-BOG. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS64140 isn't in the set, or no route object for AS64140 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS64140 in it | Not covered |
|---|---|---|---|---|---|
| AS-PITCOLOMBIA-BOG | RADB | 20 | 1 | Yes | 6 |
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 12 are in fix.csv.
- ROA: none6
- Route object: none6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 134.135.176.0/20 | No ROA covers it. Add a ROA for AS64140, maxLength 20. |
| Route object: none | 134.135.176.0/20 | No route object for it. Add a route object with origin AS64140 in the RIR database for the space. |
| ROA: none | 209.22.138.0/24 | No ROA covers it. Add a ROA for AS64140, maxLength 24. |
| Route object: none | 209.22.138.0/24 | No route object for it. Add a route object with origin AS64140 in the RIR database for the space. |
| ROA: none | 214.3.145.0/24 | No ROA covers it. Add a ROA for AS64140, maxLength 24. |
| Route object: none | 214.3.145.0/24 | No route object for it. Add a route object with origin AS64140 in the RIR database for the space. |
| ROA: none | 214.29.74.0/23 | No ROA covers it. Add a ROA for AS64140, maxLength 23. |
| Route object: none | 214.29.74.0/23 | No route object for it. Add a route object with origin AS64140 in the RIR database for the space. |
| ROA: none | 214.37.140.0/22 | No ROA covers it. Add a ROA for AS64140, maxLength 22. |
| Route object: none | 214.37.140.0/22 | No route object for it. Add a route object with origin AS64140 in the RIR database for the space. |
| ROA: none | 214.65.0.0/20 | No ROA covers it. Add a ROA for AS64140, maxLength 20. |
| Route object: none | 214.65.0.0/20 | No route object for it. Add a route object with origin AS64140 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS64140 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.