Network · data from 2026-11-12
AS271929 INTERCOMMERCE
Registry name: AS271929 - INTERCOMMERCE S.A., EC · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271929, 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.
| 45.236.142.0/24 | Valid | Nonecovered by 45.236.140.0/22 | 670 100% |
| 45.236.143.0/24 | Valid | Nonecovered by 45.236.140.0/22 | 670 100% |
| 45.236.140.0/24 | Valid | Nonecovered by 45.236.140.0/22 | 669 99% |
| 45.236.141.0/24 | Valid | Nonecovered by 45.236.140.0/22 | 669 99% |
| 2803:9a10:8000::/33 | Valid | Nonecovered by 2803:9a10::/32 | 636 100% |
| 179.0.42.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 179.0.43.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 179.60.52.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 45.236.140.0/22 | Valid | RIR databaseLACNIC | 670 100% |
| 2803:9a10::/32 | Valid | RIR databaseLACNIC, RADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS271929: AS271929:AS-PEERS. 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 (AS271929 isn't in the set, or no route object for AS271929 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 | AS271929 in it | Not covered |
|---|---|---|---|---|---|
| AS271929:AS-PEERS | LACNIC | 5 | 2 | 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: none5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.236.142.0/24 | No route object for it. A route object for 45.236.140.0/22 with origin AS271929 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271929 in the RIR database for the space. |
| Route object: none | 45.236.143.0/24 | No route object for it. A route object for 45.236.140.0/22 with origin AS271929 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271929 in the RIR database for the space. |
| Route object: none | 45.236.140.0/24 | No route object for it. A route object for 45.236.140.0/22 with origin AS271929 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271929 in the RIR database for the space. |
| Route object: none | 45.236.141.0/24 | No route object for it. A route object for 45.236.140.0/22 with origin AS271929 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271929 in the RIR database for the space. |
| Route object: none | 2803:9a10:8000::/33 | No route object for it. A route object for 2803:9a10::/32 with origin AS271929 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271929 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271929 whose prefix no peer sees AS271929 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.0.42.0/23 | LACNIC | 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.