Network · data from 2026-11-12
AS52402 INTERCITY COMUNICACIONES
Registry name: AS52402 - INTERCITY COMUNICACIONES S.A., AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52402, 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.123.240.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.241.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.242.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.243.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.244.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.245.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.246.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.247.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.248.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.249.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.250.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.251.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.252.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.253.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.254.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.255.0/24 | Valid | Nonecovered by 200.123.240.0/20 | 4 1%low visibility |
| 200.123.240.0/20 | Valid | RIR databaseLACNIC | 668 99% |
AS-SET
PeeringDB's irr_as_set for AS52402: AS52402:AS-ICY. 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 (AS52402 isn't in the set, or no route object for AS52402 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 | AS52402 in it | Not covered |
|---|---|---|---|---|---|
| AS52402:AS-ICY | 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 16 are in fix.csv.
- Route object: none16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.123.240.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.241.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.242.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.243.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.244.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.245.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.246.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.247.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.248.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.249.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.250.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.251.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.252.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.253.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.254.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
| Route object: none | 200.123.255.0/24 | No route object for it. A route object for 200.123.240.0/20 with origin AS52402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52402 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS52402 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.