Network · data from 2026-11-12
AS64113 ADMINISTRADORA DE SERVICIOS Y SISTEMAS AUTOMATIZADOS FALABELLA
Registry name: AS64113 - FALABELLA TECNOLOGIA CORPORATIVA LTDA, CL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS64113, 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.10.170.0/24 | Valid | Nonecovered by 200.10.168.0/22 | 673 100% |
| 200.10.168.0/23 | Valid | Nonecovered by 200.10.168.0/22 | 671 100% |
| 200.10.170.0/23 | Valid | Nonecovered by 200.10.168.0/22 | 671 100% |
| 200.10.168.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 200.10.169.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 200.10.171.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 200.10.167.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 200.10.172.0/24 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 2801:11:b800::/48 | Valid | RIR databaseLACNIC | 636 100% |
| 200.10.168.0/22 | Valid | RIR databaseLACNIC | 13 2%low visibility |
AS-SET
PeeringDB's irr_as_set for AS64113: AS64113:AS-FALABELLA. 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 (AS64113 isn't in the set, or no route object for AS64113 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 | AS64113 in it | Not covered |
|---|---|---|---|---|---|
| AS64113:AS-FALABELLA | LACNIC | 1 | 1 | Yes | 0 |
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 6 are in fix.csv.
- Route object: none3
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.10.170.0/24 | No route object for it. A route object for 200.10.168.0/22 with origin AS64113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64113 in the RIR database for the space. |
| Route object: none | 200.10.168.0/23 | No route object for it. A route object for 200.10.168.0/22 with origin AS64113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64113 in the RIR database for the space. |
| Route object: none | 200.10.170.0/23 | No route object for it. A route object for 200.10.168.0/22 with origin AS64113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64113 in the RIR database for the space. |
| Route object: RIR | 200.10.168.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.10.169.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.10.171.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS64113 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.