Network · data from 2026-11-12
AS269994 SCALI ALFREDO MARCOS
Registry name: AS269994 - SCALI ALFREDO MARCOS (ALL SOLUTIONS), AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269994, 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.
| 177.53.120.0/23 | Valid | Nonecovered by 177.53.120.0/22 | 672 100% |
| 177.53.122.0/23 | Valid | Nonecovered by 177.53.120.0/22 | 4 1%low visibility |
| 177.53.123.0/24 | Valid | Nonecovered by 177.53.120.0/22 | 4 1%low visibility |
| 177.53.120.0/24 | Valid | Other IRR onlyRADB | 4 1%low visibility |
| 177.53.121.0/24 | Valid | Other IRR onlyRADB | 4 1%low visibility |
| 177.53.122.0/24 | Valid | Other IRR onlyRADB | 4 1%low visibility |
| 177.53.120.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 2803:c1e0::/32 | Valid | RIR databaseLACNIC, RADB | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS269994: AS269994. 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 (AS269994 isn't in the set, or no route object for AS269994 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 | AS269994 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS269994 | A single AS number, not a set: AS269994 (this network), 5 route objects. | |||||
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 | 177.53.120.0/23 | No route object for it. A route object for 177.53.120.0/22 with origin AS269994 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269994 in the RIR database for the space. |
| Route object: none | 177.53.122.0/23 | No route object for it. A route object for 177.53.120.0/22 with origin AS269994 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269994 in the RIR database for the space. |
| Route object: none | 177.53.123.0/24 | No route object for it. A route object for 177.53.120.0/22 with origin AS269994 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269994 in the RIR database for the space. |
| Route object: RIR | 177.53.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.53.121.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.53.122.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 AS269994 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.